Author Topic: VUMeter Plugin  (Read 50531 times)

Mayibongwe

  • Sr. Member
  • ****
  • Posts: 1733
  • Heal The World
Then neither of those is probably getting the background colour of the Track Information panel(s).
From my testing this is where the 3 colours other than black in the dropdown come from in the musicbee skin file.
Yes, this corresponds with what I had as well.
But why not just pull panel.BackColor from the handle passed by OnDockablePanelCreated?
That's what I did with my LibraryQuiz panel which I believe has the same background as the trackInfo panel.
Strength and Honour (2025)

sveakul

  • Hero Member
  • *****
  • Posts: 3262
Ahhh ... but there is if you use Firefox. I was having this same issue on Dropbox and another of other websites where I didn't have, nor did I need an account.
You should already have installed the uBlockOrigin addon to Firefox. Open Options and select the My Filters tab and enter this
Code
||accounts.google.com/gsi/*$xhr,script,3p
and click Apply Changes. You'll never see that popup again.
Well never say never.  I installed uBlock, kept all the default settings, and entered your code into My Filters.  Restarted Fireox.  Clicked on the link again, and I STILL get this damn screen:



The filter page as entered on Ublock:



Can you, or hiccup, or BoringName please post the file foo_vis_vumeter-0.0.3.65533.fb2k-component someplace where I can DOWNLOAD it??  NOT Dropbox!!  I don't want to pester the developer any more.

For uploads I use mega.nz (noticed Steven often did)--free 20 GB account after email address sign-up.  And, people can actually download the links I send (what a concept).

BoringName

  • Sr. Member
  • ****
  • Posts: 916
But why not just pull panel.BackColor from the handle passed by OnDockablePanelCreated?

Not something I had considered, I'll give it a shot.

hiccup

  • Hero Member
  • *****
  • Posts: 9107
Can you, or hiccup, or BoringName please post the file foo_vis_vumeter-0.0.3.65533.fb2k-component someplace where I can DOWNLOAD it??  NOT Dropbox!!  I don't want to pester the developer any more.
There is nothing wrong with Dropbox or the browser or plugins you are using.
It looks like BoringName didn't choose the (basic) right-click option 'Copy Dropbox link', but created a 'share', which requires specifying shared users allowed to download the file.
If he shares the basic Dropbox link all should be fine. (but that makes the file very public, so that may not be desirable)

I don't have that file either, but I'm not in a hurry.
It would be better to first put our efforts in getting the current implementation as good as possible.
How are you faring with your LVU skins?
Have you created or modified some already?
Are they working as expected in VUMeter?

hiccup

  • Hero Member
  • *****
  • Posts: 9107
I've updated the zip - VUMeter1.7.zip
Sorry, but that one also seems to have some regression compared to earlier versions.
The needle frequently seems to be missing 'beats', or seems to 'exaggerate' others. With the sync/timing also not looking very good.
Not sure how to describe it better, but it's to the extend that it sometimes looks a bit as if the VU meter is listening to another song than I am  ;-)
(sample sliders both set to 1)

But perhaps I am misjudging or exaggerating a bit, will do some better testing tonight.
Last Edit: October 03, 2024, 08:34:32 AM by hiccup

sveakul

  • Hero Member
  • *****
  • Posts: 3262
It wasn't BoringName that made the DropBox post, it was "oops."

And thanks to BoringName, who sent me a MediaFire link instead, I was able to download the file no problems.

I haven't had time to do anything custom with the VU skins.  I have one I did long ago that still works fine, a mod of the default "simple.zip" skin to use any 819X614 png as the whole-frame backdrop, with simple LR LED's in the lower left corner re-scaled to respond to the resize by doing proportional reductions of the dbs values and adjusting the position points.  If you don't like Avril Lavigne, you can change the bg.png file to any other of same dimensions.
https://mega.nz/file/uBgQnBqK#BOt_NmcWSnJpHrSjxNKZAoK4Ulef0_nQBHXdlcb38ig

I am using the LVU 1.2.1 64-bit plugin with AIMP 5.30.2563 64-bit.  Yes works fine in MB (Single meter, lock to Y) but the design was for a large viz window like AIMP and more for a visual than use as a VUMeter.
Last Edit: October 03, 2024, 08:08:48 AM by sveakul

sveakul

  • Hero Member
  • *****
  • Posts: 3262
I've updated the zip - VUMeter1.7.zip
Sorry, but that one also seems to have some regression compared to earlier versions.
The needle frequently seems to be missing 'beats', or seems to 'exaggerate' others. With the sync/timing also not looking very good.
Not sure how to describe it better, but it's to the extend that it sometimes looks a bit as if the VU meter is listening to another song than I am  ;-)
(sample sliders both set to 1)
Will test a bit better tonight.
I'm going to wait on this one (1.7x) until the behind-the scenes revisions using the same version number settle down, I get 'em mixed up.

hiccup

  • Hero Member
  • *****
  • Posts: 9107
I haven't had time to do anything custom with the VU skins.
That's a pity. Considering BoringName has put in quite some effort in trying to fulfill your LVU suggestions/requests, I think timing-wise this would have been the moment to share some specific feedback and concrete results.
Before jumping to possible foobar2000 compatibility. (let's allow BoringName some time to figure things out regarding that first)
To me it feels like this LVU stuff may not have been completed, nor has it been tested very well yet, and it's now just left hanging there.
Can you at least give some indication on some percentage of LVU skins that are now working well in VUMeter?
Last Edit: October 03, 2024, 08:19:55 AM by hiccup

BoringName

  • Sr. Member
  • ****
  • Posts: 916
The 1.7 link "should" be better now. I temporarily changed to the get_peak method because I didn't know how long it would take me to diagnose but it was a quick fix so I changed it back. 1.7 is now using the PCM data for everything. 1.6 was using the getPeak command.  In testing they produce the same levels.


Not something I had considered, I'll give it a shot.

This is just producing the same colour. I really need a skin where someone has set a colour for the track information panel so it isn't the same as the panel.ChildBody.Default.

I tried setting <element id="TrackInfoPanel" bg="3,56,88" fg="182,182,182"/> in my current skin but it doesn't appear to do anything.

Is there a different element id for the track information panel?

hiccup

  • Hero Member
  • *****
  • Posts: 9107
I really need a skin where someone has set a colour for the track information panel so it isn't the same as the panel.ChildBody.Default.
As I mentioned before, 'Elemental' has this and displays the issue.
And Sample Skin will allow you to see and check all existing panels, their names, and their bg values.
Chameleon DNA may also be helpful.

Quote from: BoringName
Is there a different element id for the track information panel?
So for me it would be next to the Track Information panels, which would require to get the bg of "ElementPanel.Default".
Last Edit: October 03, 2024, 08:57:07 AM by hiccup

BoringName

  • Sr. Member
  • ****
  • Posts: 916
As I mentioned before, 'Elemental' has this and displays the issue.
And Sample Skin will allow you to see and check all existing panels, their names, and their bg values.

Sorry I missed that before. Turns out I just needed to add .Default to it. I'll do some tests but at this stage I think it's going to be limited to what colours I can grab. It seems to be mainly just the colours of a few main elements and that's it. If an element has a custom colour set and isn't inheriting from one of the main elements I might not be able to do much.

BoringName

  • Sr. Member
  • ****
  • Posts: 916
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.....

So if I call
Plugin.MbApiInterface.Setting_GetSkinElementColour(Plugin.SkinElement.SkinButton, Plugin.ElementState.ElementStateDefault, Plugin.ElementComponent.ComponentBackground)));
This returns the colour from the following element.
<element id="Controls.Button.Default" bg="2,54,104" fg="210,210,210" bdr="1,20,55" />

I confirmed it by changing the colours on that element and they were reflected in the colour returned.
Now if add the following line to the skins XML file
<element id="Controls.Button.Modified" fg="255,0,0" bdr="1,20,55" />

I would expect the following command to return 255,0,0 but it doesn't, it returns 210,210,210
Plugin.MbApiInterface.Setting_GetSkinElementColour(Plugin.SkinElement.SkinButton, Plugin.ElementState.ElementStateModified, Plugin.ElementComponent.ComponentForeground)));

I guess the issue could be that SkinElement.SkinButton is from something else that inherits the default colour from Controls.Button but I think that would be unlikely.

Or maybe Controls.Button cannot have a modified state? From the tests I've done I can't get any of the elements to return a different colour for modified state.

So, bug or idiot?.....possibly both.

sveakul

  • Hero Member
  • *****
  • Posts: 3262
I haven't had time to do anything custom with the VU skins.
That's a pity. Considering BoringName has put in quite some effort in trying to fulfill your LVU suggestions/requests, I think timing-wise this would have been the moment to share some specific feedback and concrete results.
To me it feels like this LVU stuff may not have been completed, nor has it been tested very well yet, and it's now just left hanging there.
Can you at least give some indication on some percentage of LVU skins that are now working well in VUMeter?
I'm not trying to compete with you or BoringName, and due to health issues have a limited amount of time to spend on my primary hobby, which includes two other players besides MusicBee.  I never promised anything as far as timing or output, and am trying to just give some feedback when I can.  I don't expect anyone to spend any amount of effort on my requests they don't choose to give.  So far every LVU skin I personally liked I've tried with MusicBee and works well with the exception of the Pick Signal 2 skin which used some odd zip scheme.  That's all I can really say--I don't have the technical ability to do the type of performance tweaking that you two have, but being an enthusiastic supporter carries some weight too.  There sure doesn't seem to be a lot of those out there.

phred

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 10266
Well never say never.  I installed uBlock, kept all the default settings, and entered your code into My Filters.  Restarted Fireox.  Clicked on the link again, and I STILL get this damn screen:
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.

Without filter:


With filter:
Download the latest MusicBee v3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Custom Forum Search
Posting screenshots is here

hiccup

  • Hero Member
  • *****
  • Posts: 9107
I never promised anything as far as timing or output, and am trying to just give some feedback when I can.  I don't expect anyone to spend any amount of effort on my requests they don't choose to give.  So far every LVU skin I personally liked I've tried with MusicBee and works well with the exception of the Pick Signal 2 skin which used some odd zip scheme.
Fair enough. I probably misunderstood your original intention for you raising this LVU stuff then.
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.