AudioLevel

[killall-q]

220 Hz 0.8 amplitude (default) tone, on 1.1.2

Please populate the version information field in About > Plugins properly so that it's easier to verify version.



Tip: Alt+Print Screen crops screenshots to the focused window.

[dgrace]

I tried again using Audacity as a source for a 220hz sine wave, stereo track. I get exactly equal numbers in Rainmeter->About->Skins for the left and right measures, straight down the line. Could it be something with your skin? Can you quantify the discrepancy? (i.e. "I see 0.976 on band 3 of left channel, 0.714 on band 3 R", etc.) To be most helpful, do it with Audacity and generate a 220Hz sine wave stereo track so all our numbers are consistent.

One note though - I finally repro'ed the buzzing bug - closing down Audacity while the "do you want to save?" dialog is up made it happen for me. Unfortunately I still don't know what I can do to fix it - it appears to be a bug in Windows and not Rainmeter/plugin. (i.e. from my audio capture client, the data just looks as valid as any other data, I don't get any different flags or notification when it happens)

I've attached my test skin with stereo spectrum display - let me know if you see the same bug when using it.

dave

[VasTex]

You're right, it was an issue with my code.

I essentially started my R audio at the 30th band instead of restarting it at the 1st band. This is why I could only see my R audio when I turned its gain all the way up. The audio just never 'reached' to the 30th band unless it was turned up that high.

In your example I noticed that you had 24 bands with the L audio going from bands 0-23 and the R audio also going from 0-23. What I had done was double the bands to a total of 48 bands where my L audio went from bands 0-23 and my R audio bands went from 24-47. Needless to say this skewed my display and I wasn't able to see this until I split the audio to two separate L / R audio channels and playing with their volume.

Everything looks great now:

Screenshot 2014-08-08 19.09.26.png

Long story short this is a false bug report. Your plugin is functioning properly and it was simply and issue of me misunderstanding the use of bands.

Please carry on and ignore me

[Dank420]

I built to big to fast, and have been squashing bugs since i posted....and feeling bad now for all the work i put ya thru... i fix'd my ish! Thanks for the effort and at lest buzz on the mind...
been thinking of [buzzkill] as a refresh skin at right time one time refresh but endlessloops and working once and not second time..etc... i back burner'd it.
need sleep...Thanks again, as i stated way earlier post FUN... TOO MUCH FUN!!!

OFF topic.... can we grab Plugin INfo name creator ver as to put it in a string/meter?

[jsmorley]

No, none of the information in the About interface dialog is exposed to Rainmeter in a way that it can be returned and used. A plugin author could add it as an option for the plugin, which would be the only, and really in my view, correct way to do that.

[MeasurePlugin]
Measure=Plugin
Plugin=MyPlugin
ReturnVersion=1

Which would return a string like: "1.0.0.0 © 2014 - David Grace"

[Dank420]

OK thanks.. Can we grab from this?

[jsmorley]

OK thanks.. Can we grab from this?

Not with anything native to Rainmeter. You would need to write some external addon that can read the "properties" of a file.

[Dank420]

Rawr!!! UGHHHH!!!!!
Thanks thou....

[Dank420]

OK then, Think this settles Colors for me, now Looms LVLs,Bands ,FReq,and Transformation Matrix(yikes), Channels, better positioning, but......

Like the King said, "i'll have a Fried PeanutButter and bananna sandwich."
(thought i was gonna say, have it your way didnt you!? Nope, Elvis is king, and Prince the Heir)

sidenote: #@#VUFFTCOLORS has "ID= " Var currently blank so default assign id there if want to specify device
......Enjoy!

[dgrace]

Ok new version is up. Changes in this one:

There's now a Sensitivity option on the parent to specify the dB scale of the output. Default is 35dB which matches the previous version. Increase to be able to track lower levels of audio, decrease if you only want your bars to register on higher volumes. This affects both the FFTIdx and BandIdx return values.

Better logging on error cases, should now tell you if your params are invalid and what the valid options are.

Fixed up the version info in the file.

Enjoy!

dave