VUMeter Plugin

[hiccup]

But perhaps I am misjudging or exaggerating a bit, will do some better testing tonight.

Tried it again, but it's really bad. As I said, it's often as if the meter is listening to another song than I am.
Missing the beat, unexpected rises and falls, it's just very off.

[Mayibongwe]

#1    Can someone else whose made a plugin confirm something for me before I post another bug report where it turns out there was no bug and I'm just an idiot.....
#2    Now if add the following line to the skins XML file:    <element id="Controls.Button.Modified" fg="255,0,0" bdr="1,20,55" />

#1   Your guess is better than mine. I didn't even know SkinElement.SkinButton existed (certainly not in the C# interface I have).
#2   No such element exists to the best of my knowledge. Wouldn't expect it to work.

If you're open to alternatives, why not save yourself the headache and provide a panel_skinning .xml that users can modify as they wish (independent of MB's skin).
I ended up doing the same with LibraryQuiz when I designed that panel. Retrieving colours via the MB API is very limited.

[sveakul]

To be clear, in your post regarding this issue you mentioned that your were getting a -Google- popup asking you to log in using your Google account. Your current screenshot shows that Dropbox is asking you to log in and there is no sign of the Google login request

phred I'm sorry, I guess I was just getting tired and frustrated last night.  Yes you are right, the message I can't get past must be being sent by Dropbox, not Google.  That "Continue with Google" button and logo on the message panel was what confused me--funny it was not there when I posted that screenshot, but it's back again now (see below).

While oops swears it works OK for him as a test as an unknown user, I think he must be missing that "Copy Link" option you mentioned before, unless my Firefox setup is stopping it somehow--as a hint I sent him a Reddit link with others having the same issue, and finding out they were just creating the link wrong.  I give up on it.  The copy of the file BoringName was kind enough to put on MediaFire for me should be enough the final is publicly released on the Foobar component site.

[phred]

phred I'm sorry, I guess I was just getting tired and frustrated last night.  Yes you are right, the message I can't get past must be being sent by Dropbox, not Google.  That "Continue with Google" button and logo on the message panel was what confused me.

Apology accepted, but not necessary. We all get tired and then frustrated at some point. But please answer a question for me... was there actually a Google prompt to log in using your Google account?

[sveakul]

Since you also frequently brought up the tool for creating them (both here and on the AIMP forum), I assumed you were using that tool and wanted to create and share your own VU meter skins with us.
I now understand that that was not the case. But then I also do not understand why it was an issue for you that that tool allegedly contained a virus, if you had no intention to use it. But I have probably not read or understood everything you have said and explained about it, so that's probably on me.

Ah well, so we can then put that LVU stuff to rest now, and move on to other things.

My intention is to eventually try the tool; the one admittedly amateur attempt I made with the "Avril Lavigne mod" was just done by trial and error examining the ini file for the simple.zip skin supplied with the meter.  I do think the LEDs, though tiny, respond quite well to the music even after my changes.

The virus issue was with the new LVU 1.2 plugin release itself, not the tool.  The tool is like 10 years old and was released with the 32-bit version LVU plugin which was the only one available even when AIMP went to 64-bit.  When the 64-bit LVU came out I said here we go, but was stopped in my tracks by the mass of virus alerts it threw from VirusTotal.  Now, the 1.2.1 release has fixed that, and I can give things another try when I have more time.  Just a misunderstanding.  Yes, upwards and onwards!

[sveakul]

Apology accepted, but not necessary. We all get tired and then frustrated at some point. But please answer a question for me... was there actually a Google prompt to log in using your Google account?

At the time I first encountered the problem, the message looked exactly like the crop screenshot I just posted above, complete with the "Continue with Google" button/prompt on it as you can clearly see.  When I posted that complete screenshot for you last night, it did NOT have it;  why, I do not know and at this point do not care.  I'm not trying to BS anybody.

[phred]

When I posted that complete screenshot for you last night, it did NOT have it;  why, I do not know and at this point do not care.  I'm not trying to BS anybody.

The filter that I sent you, once added to uBlockOrigin is responsible for removing the Google login prompt on non-Google websites. For me, that filter was a gift from the heavens.

[sveakul]

The filter that I sent you, once added to uBlockOrigin is responsible for removing the Google login prompt on non-Google websites. For me, that filter was a gift from the heavens.

if you ever find a filter that blocks the Dropbox "sign up for free so we can confirm your identity" block on Dropbox sites, I'm all in!   FWIW, your filter did "blank out" the "Continue with Google" button from the block panel, so I believe you, it works.

[BoringName]

Tried it again, but it's really bad. As I said, it's often as if the meter is listening to another song than I am.
Missing the beat, unexpected rises and falls, it's just very off.

- copied the latest bass.dll

Just making sure you installed the new MusicBeeBass.dll because that's different to the straight bass.dll file.

[BoringName]

If you're open to alternatives, why not save yourself the headache and provide a panel_skinning .xml that users can modify as they wish (independent of MB's skin).

I really don't want to be delving in to skin stuff for the sake of one colour. I was hoping I could just grab a modified foreground colour on one of the elements I can retrieve and then users could just set that colour in their skin.xml to whatever they wanted. But it seems the modified element state doesn't work.

[Bee-liever]

Using MB Version: 3.6.9042 P and new MusicBeeBass.dll and still can't get 'Ignore ReplayGain' to work.
Using DejaVu Compact LED Calibrated Elemental, works fine in normal mode.
Stop playback, select 'Ignore ReplayGain' and restart track.
Needles no longer react to input, just slowly climb until at peak +6 on meter.
Stop track and needles sit at peak approx. 30sec and then really slowly fall back

Will try to upload gif later when satellite internet is a bit more stable.

[BoringName]

Will try to upload gif later when satellite internet is a bit more stable.

Probably more helpful if you provide the info I requested previously.
What's your EQ preamp set to?
Is it the same for all tracks and do they have replaygain tags?

Also are you using WASAPI Shared or Exclusive?

edit: Ok I'm seeing it in my Portable install so it's an issue with the portable version. No idea why that should be different but I'll see if I can track it down.

[Bee-liever]

What's your EQ preamp set to?

Not used - 0

Is it the same for all tracks and do they have replaygain tags?

All tracks/albums have replaygain tags

Also are you using WASAPI Shared or Exclusive?

Normally WASAPI Exclusive but if using outdoor bluetooth WASAPI Shared.
Error occurs either way.

Just saw the edit about portable version as I posted reply

[BoringName]

Just saw the edit about portable version as I posted reply

Yeah, not really sure what's going on there as the portable version is literally the same EXE file. I expect it just checks for a registry entry and when that doesn't exist it goes into portable mode.

I've asked in the rawdata thread as I don't think it's my fault this time but we will see....

edit: So the problem is the preAmp figure is coming through as zero regardless of what the preAmp is set to on the portable version. It should be coming through as 1 if no preAmp is set. You might think it should come through as zero when the PreAmp is set to 0 but when you are converting things from peak to decibel and back. 1.0 peak is zero decibels so when I'm adjusting the current level by the preAmp value it adjusts it by zero as it should when no preAmp is set.

When the preAmp comes through as 0 it converts to 1.0 and when I adjust the current level by 1.0 it sends the needle to max like you are seeing. It's tricky to check for zero when dealing with decibels as you have to decide if it's zero because of a problem or it's supposed to be zero. In this case there is no reason for PreAmp to ever be zero but it highlighted a problem that might not have been noticed for a while if I had forced preAmp to be 1.0 if it came through as Zero.

I have noticed the upside down left needle  on that skin is going off the meter which means I haven't handled the maxAngle thing correctly. The upside down needles make everything backwards! It seems I really suck at testing, and now I'm going to have to start testing installed and portable versions...

[BoringName]

If you are having issues in the portable version. when Ignore Replaygain is checked.
hamburger Menu-Edit Preferences->Player->Equaliser & DSP (button down the bottom right)

Click "enable equaliser" at the top left. You can leave everything at defaults so it shouldn't alter the volume.

I hadn't even noticed that check box existed and just thought that page did nothing unless you adjusted the values.

That will get it working for now. I will add a check in the next version to ignore the PreAmp value if the EQ is not enabled.