AudioLevel

[dgrace]

Here try this one and let me know if you see any change. I added a QueryPerformanceCounter check to keep it from hitting the buffer more than 60Hz.

dave

[dgrace]

that would be awesome

Sounds good. I'll get you the audio levels - you do the AfterEffects running in real-time on your desktop part.

dave

[j.daddy]

As real life piles up around me , I raincode.......
heres: Living sound , includes RainRGB to select bar color (thats not spectrum linked)
and 3 presets small,med,large in custom skin actions. Enjoy........

can we get an update cuz it looks weird with the new plugin

[Brian]

In general, we never want to really have more than one of these AudioLevel parent instances around - a loopback client on the core audio service is a fairly expensive thing.

I totally agree, in fact personally I would probably never have more than 1 skin using 1 parent at any time. However, when testing new code in the Rainmeter environment, I often try to "stress" the code to find any weaknesses, especially skins that require low Update values. I can see someone out there having multiple audio skins running at the same time, and complaining to us about CPU usage.

Here try this one and let me know if you see any change. I added a QueryPerformanceCounter check to keep it from hitting the buffer more than 60Hz.

Yeah, there is some improvement, but only about 2-3%. I am still hovering around 9-10% CPU usage for Rainmeter with those 4 skins. I messed around with the Updates of all 4 skins and basically got the same results. All 4 skins' Update value ranged from 0 (your skin) to 50 (killall-q's skin).

-Brian

[dgrace]

I've just discovered the joys of perfmon, being able to track CPU by process. (run "perfmon" from start menu, click on Monitoring Tools -> Performance Monitor, then click the green + icon in the toolbar and select Process in the Counters window, and you can select the process(es) you want to watch in the "Instances of selected object:" window.

I'm not seeing much CPU at all when I activate my VUMeter skin in the Rainmeter process, but my dwm.exe (desktop window manager) jumps up by 2% or so. Interestingly, the biggest factor in my Rainmeter process looks like my simple Network skin (copied from the Illustro one). Just having the NetIn and NetOut measures on takes about 1.5% of the CPU for me - that seems pretty high! If I run that skin at 100ms intervals it eats about 30% CPU, which seems insane. Is it actually packet-sniffing all the network traffic instead of just querying some kind of system counter?

Anyway, pretty useful tool, thought I'd share the info.

dave

[Dank420]

Is there maybe Still some Gain hiding in there still Left/Right channels seemingly not same
Parent measure

Code: Select all

[measureAudioRaw_Out]
Measure=Plugin
Plugin=AudioLevel
Port=Output
RMSAttack=100
RMSDecay=300
RMSGain=2.0
PeakAttack=15
PeakDecay=2700
PeakGain=1.0
FFTSize=512
FFTOverlap=512
FFTAttack=30
FFTDecay=320
Bands=24
FreqMin=100
FreqMax=1400

child

Code: Select all

[measureAudioOutL_FFT_00]
Measure=Plugin
Plugin=AudioLevel
Parent=measureAudioRaw_Out
Channel=L
Type=Band
BandIdx=0
(and more up to 23)

[measureAudioOutR_FFT_00]
Measure=Plugin
Plugin=AudioLevel
Parent=measureAudioRaw_Out
Channel=R
Type=Band
BandIdx=0
(and more up to 23)

used parent for both plugins for pics
just changed plugin by reinstalling

[dgrace]

Is there maybe Still some Gain hiding in there still Left/Right channels seemingly not same

Will take a look...

dave

[VasTex]

I was actually coming to confirm the same thing (same version of the plugin as well). I personally used a video from YouTube to test the differences. It's not as accurate as the above test, but it's none the less noticeable. Otherwise, I am loving the plugin.

Capture.PNG

[dgrace]

Not seeing it on mine, here's what I get with a 220hz wave going to L/R equally:

Can anyone else confirm?

dave

[VasTex]

Using a 220Hz wave through both L and R equally I still get this:

Capture2.PNG

I'd like to point out that I'm using the 64bit version of your plugin taken from this post:

Here try this one and let me know if you see any change. I added a QueryPerformanceCounter check to keep it from hitting the buffer more than 60Hz.

dave

with 64bit Rainmeter on 64bit Windows 8.1

**EDIT**

I just tested the same plugin version as above, but on my work computer running 64bit Rainmeter and 64bit Windows 7. Still has the same issue. Actually, when using Audacity to produce the 220Hz signal I have no output at all on the right side until I adjust the gain by at least +2Db, the higher that goes the more output I get on the right side. That being said, even when the gain has been pushed to ~+20Db the right side, although visible, does not reflect the shape of the output on the left at all.

I'm sorry I can't be much more help here. I'm not very familiar with audio technicalities as I should be. Apologies if I misused a word here or there.