VUMeter Plugin

[sveakul]

Roger that, yes indeed it's a helpful addition, I just wanted to get phred up first with the behavior he has been used to in case the new check/create function causes him any confusion.

[phred]

phred I thought you were all set after your BIOS update!

Correct. This issue is on a different PC which is my testing box. Although I do admit I haven't tried 2.6 (nor 2.6.1) on my main PC. Which will be done once I figure out this issue on the testing PC.

Start MB anyway you can, and be sure that in "Arrange Panels" any "vumeter" element still on the left side has been dragged back over to the "pool" on the right.  THEN, exit MB, and delete any instance of "mbVUMeter.dll", "mbVUMeter.Settings.xml," and the VUMeter skins folder (s) (after backing up the sins!) wherever they exist.
...

I'm pretty sure I've done all that last night, but will try again after trying BoringName's suggestions.

[phred]

I have now tried the suggestions from both sveakul and BoringName using 2.6 and 2.5.1. Same results with the same error message. I'm out of time for a while, but what I'll try next is a brand new, clean and naked Portable install on the test machine. Will report back with results.

[sveakul]

I have now tried the suggestions from both sveakul and BoringName using 2.6 and 2.5.1. Same results with the same error message. I'm out of time for a while, but what I'll try next is a brand new, clean and naked Portable install on the test machine. Will report back with results.

WAS there a VUMeter element still on the left side of Layout?

Try deleting this entry, if present, from the MB ini file:

 <State>
  <Id>\MusicBee\Plugins\mb_VUMeter.dll</Id>
  <Name>VUMeter</Name>
  <Description>Creates a UI element to display a VU Meter.</Description>
  <Enabled>true</Enabled>
  <PanelHeight>-180</PanelHeight>
 </State>

So this all started when you forgot to re-specify your vumeter skins location in the xml file after you moved the MB Portable?

[johnnyboy]

Still cant get this to work. Error Loading skin. I think i havent extracted files correctly to their correct folders. help

[sveakul]

1.  What version number and type (Portable, Installer, Store) of MusicBee do you have?  From the Help/About menu. Note that the minimum version of Musicbee required is 3.6.9040.
2.  What version of the VUMeter plugin did you install?
3.  Where have you added the "vumeter" panel in the MB "Arrange Panels" dialog?
4.  Does the plugin show in the Preferences/Plugins list?
5.  Did you add the plugin using the "Add Plugin" button at the top of the Preferences/Plugins panel, or manually extract the zip?  If the latter, where did you extract the files/folders to?

We can and will continue to help you when you supply this info.

[phred]

Continuing with my "test" saga...

On my test PC I have created a brand new, naked, virginal and unmolested Portable installation of MB. I created a small library of about twenty tracks. No new skins, no new plugins, no new nothing. I closed MB and dragged mb_VUMeter.dll (6.1) into the Plugins directory. Restarted MB, arranged the VUMeter panel to where I've been placing it during this test (and where it happily lives on my main PC) and exited MB. Relaunched it and VU panel was all black and a right-click showed nothing. And then MB threw the same error it's been throwing all during this experiment and once I clicked ok, MB closed.

Code

MusicBee v3.6.9101.34338P  (Win10.0), 7 Dec 2024 13:32:

System.OverflowException: Value was either too large or too small for an Int32.
   at System.Convert.ToInt32(Double value)
   at MusicBeePlugin.VUMeter.SetPivotOffset()
   at MusicBeePlugin.VUMeter.FillVertexArrays()
   at MusicBeePlugin.VUMeter.Window_SizeChanged(Object sender, SizeChangedEventArgs e)
   at System.Windows.SizeChangedEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
   at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
   at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
   at System.Windows.UIElement.RaiseEvent(RoutedEventArgs e)
   at System.Windows.FrameworkElement.OnRenderSizeChanged(SizeChangedInfo sizeInfo)
   at System.Windows.ContextLayoutManager.fireSizeChangedEvents()
   at System.Windows.ContextLayoutManager.UpdateLayout()
   at System.Windows.UIElement.UpdateLayout()
   at System.Windows.Interop.HwndSource.Process_WM_SIZE(UIElement rootUIElement, IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam)
   at System.Windows.Interop.HwndSource.LayoutFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at MS.Win32.HwndSubclass.DefWndProcWrapper(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)

With MB still closed, I removed the dll, and my skins, and the ini file. No traces left in this installation. Restarted MB, went to Preferences > Plugins > Add Plugin and pointed it to a ZIP of 2.5.1. I checked and saw the dll and the default skins where they're supposed to be along with a "new" directory under AppData\Plugins\VUMeter which was empty (no .ini file yet.) Launched MB and it didn't throw an error. Open panel arrangement and dragged the VUMeter panel to where I want it, saved, and closed MB. Opened MB, saw an all black panel where the VUMeter should be with no context menu upon right-click and then MB threw the same error as above.

Restarting MB from this condition causes the same error to appear within five seconds. Still can't copy the error using the button in the error window and clicking ok closes MB.

[sveakul]

Continuing with my "test" saga...

On my test PC I have created a brand new, naked, virginal and unmolested Portable installation of MB. I created a small library of about twenty tracks. No new skins, no new plugins, no new nothing. I closed MB and dragged mb_VUMeter.dll (6.1) into the Plugins directory. Restarted MB, arranged the VUMeter panel to where I've been placing it during this test (and where it happily lives on my main PC) and exited MB. Relaunched it and VU panel was all black and a right-click showed nothing. And then MB threw the same error it's been throwing all during this experiment and once I clicked ok, MB closed.

Phred, you're doing SOMETHING wrong, because the meter works just great here.  Let me just address this first part of your post.  Let's start over from nothing, another brand-new Portable..  BTW, is this with the "knackered" PC that needed a BIOS boost, chipset update, and all the rest?

Be sure all of MB is whitelisted in any antivirus.

First of all you shouldn't have tried to manually drag anything.  And forget all your skins for now.  You should have just opened the new MB, gone to the plugins panel and pressed the "Add Plugin" button, pointing to where you put the VUMeter 2.6.1 zip file.  Then it will put the files/folders in the right place itself.  Restart MB.  Next, you would go to "Arrange Panels", and pull the "vumeter" element over to where you want it.  Restart MB for the heckuvit.  Check to be sure the plugin appears in prefs/plugins and is enabled (remember if the button says "Disable" it means the plugin IS ALREADY ENABLED--don't push it!)  Now do you get a context menu when you can pick one of the 4 (?) default skins??

Don't try to find or make path changes to the xml fle until the above is a success.  We're starting to reach the "I won't be able to help anymore with this" stage (kidding   ).

[phred]

BTW, is this with the "knackered" PC that needed a BIOS boost, chipset update, and all the rest?

This is -not- my main PC where I previously had issues. I answered your question earlier today regarding which machine. This is a test machine that has only had portable versions of MB previously and those MB installations are removed when i'm done with whatever it is/was that I was testing.

First of all you shouldn't have tried to manually drag anything.  And forget all your skins for now.  You should have just opened the new MB, gone to the plugins panel and pressed the "Add Plugin" button, pointing to where you put the VUMeter 2.6.1 zip file.  Then it will put the files/folders in the right place itself.  Restart MB.  Next, you would go to "Arrange Panels", and pull the "vumeter" element over to where you want it.  Restart MB for the heckuvit.  Now do you get a context menu when you can pick one of the 4 (?) default skins??

Don't try to find or make path changes to the xml fle until the above is a success.

Again, I commented about this in my previous post...

On my test PC I have created a brand new, naked, virginal and unmolested Portable installation of MB. I created a small library of about twenty tracks. No new skins, no new plugins, no new nothing.
...
With MB still closed, I removed the dll, and my skins, and the ini file. No traces left in this installation. Restarted MB, went to Preferences > Plugins > Add Plugin and pointed it to a ZIP of 2.5.1. I checked and saw the dll and the default skins where they're supposed to be along with a "new" directory under AppData\Plugins\VUMeter which was empty (no .ini file yet.) Launched MB and it didn't throw an error. Open panel arrangement and dragged the VUMeter panel to where I want it, saved, and closed MB. Opened MB, saw an all black panel where the VUMeter should be with no context menu upon right-click and then MB threw the same error as above.

Restarting MB from this condition causes the same error to appear within five seconds. Still can't copy the error using the button in the error window and clicking ok closes MB.

For sake of completeness and perhaps redundancy , I will delete the MB installation and (once again) create a new portable with nothing but a small library and try again.

[phred]

First of all you shouldn't have tried to manually drag anything.  And forget all your skins for now.  You should have just opened the new MB, gone to the plugins panel and pressed the "Add Plugin" button, pointing to where you put the VUMeter 2.6.1 zip file.  Then it will put the files/folders in the right place itself.  Restart MB.  Next, you would go to "Arrange Panels", and pull the "vumeter" element over to where you want it.  Restart MB for the heckuvit.  Check to be sure the plugin appears in prefs/plugins and is enabled (remember if the button says "Disable" it means the plugin IS ALREADY ENABLED--don't push it!)  Now do you get a context menu when you can pick one of the 4 (?) default skins??

Don't try to find or make path changes to the xml fle until the above is a success.  We're starting to reach the "I won't be able to help anymore with this" stage (kidding   ).

I have once again done a clean install of Portable MB 3.5 and patched to 3.6.9101. Once again I have followed your instructions. I used the 'add plugins' button. The four default skins are in E:\MB Test\Plugins\VUMeter\VUSkins. And once again, I'm getting the same result. You're correct. I'm starting to feel that I don't -want- help anymore. I should just delete everything and stick with my main PC. No more testing.  <sigh>

[BoringName]

It's not clear from your posts so you may have already tried this.

But you can remove all skins from the skin folder and start Musicbee with no skins available and see how that goes.

I was thinking maybe one of the skins is corrupted/broken but if it's just the 4 default skins that's probably not it.

At this point I think it may be something to do with the computer setup, I understand this is a different computer to the one that normally has issues but is it setup the same? Same region etc... I think this might be a problem like Boroda had with my other plugin to do with commas and decimal points.

I think your computer might be setup in a way that the check the code makes to ensure  a valid skin is loaded and what type it is gets skipped somehow. The same reason your other computer couldn't handle multiple threads.

Edit: Can you go to Windows Settings->Time & Language->Region and list what is in the "Country or Region" and "Regional Format" fields. Might be worth listing it for both your computers, we might be able to solve your issues on that PC as well.

[BoringName]

Still cant get this to work. Error Loading skin. I think i havent extracted files correctly to their correct folders. help

Depending whether you have the installed version or portable, you need skins to be stored in the following folders
Installed - C:\users\<username>\AppData\Roaming\Musicbee\Plugins\VUMeter\VUSkins
Portable - C:\Musicbee\Plugins\VUMeter\VUSkins

Alternatively you can specify a custom directory path for the skins in the XML file. Close musicbee and open this file in a text editor.
Installed - C:\Users\<username>\AppData\Roaming\MusicBee\Plugins\VUMeter\mbVUMeter.Settings.xml
Portable - C:\Musicbee\AppData\Plugins\VUMeter\mbVUMeter.Settings.xml

Change <skinFolder />
To something like this -
<skinFolder>C:\Example\VU Meter Skins</skinFolder>

edit: just to state the obvious, you need to change the drive letter and folder names to match your system.

[phred]

But you can remove all skins from the skin folder and start Musicbee with no skins available and see how that goes.

I totally removed all VU skins and VU files.

I was thinking maybe one of the skins is corrupted/broken but if it's just the 4 default skins that's probably not it.

Only the default skins. Plugin installed via the "add plugins" button in plugin preferences.

At this point I think it may be something to do with the computer setup, I understand this is a different computer to the one that normally has issues but is it setup the same? Same region etc... I think this might be a problem like Boroda had with my other plugin to do with commas and decimal points.

Same region

Main PC:


Test PC:


I don't want anyone else to waste time on this. It's a test PC with a test config of MB. Everything else is working as expected (both the PC and MB.) The suggestions so far have been appreciated, but we're getting nowhere. And I'm getting frustrated. So I'll let it rest for a while and when I feel like it I'll come back to it and try again.

Thanks for the help and suggestions.

[phred]

Depending whether you have the installed version or portable, you need skins to be stored in the following folders
Installed - C:\users\<username>\AppData\Roaming\Musicbee\Plugins\VUMeter\VUSkins
Portable - C:\Musicbee\Plugins\VUMeter\VUSkins

Here's another reason why I'm giving up (temporarily.) Neither you nor sveakul seem to be reading my reports as you're asking questions for which I've already supplied answers.

- It's a clean portable installation of MB
- After the initial plugin try, and removal of all things VUMeter-related, I installed the plugin via the "Add Plugins" button. So the paths are the default paths specified within the plugin.
- No paths or drive lettersneed to be changed as the plugin is creating them.
- Previously I tried using a created path for the skins and edited the .ini to reflect the change.

[BoringName]

Here's another reason why I'm giving up (temporarily.) Neither you nor sveakul seem to be reading my reports as you're asking questions for which I've already supplied answers.

That quote you linked is for a different user, not you.

I totally removed all VU skins and VU files.

And got the same error with no skins installed? If that's the case it does confirm it's skipping or incorrectly applying the code that checks what skins are installed. Edit: Actually I can't see any possible way for that error to happen if the skins folder is empty, very strange.

I don't want anyone else to waste time on this. It's a test PC with a test config of MB.

I can understand that, but if you have this problem there is no doubt others who had the same problem and just uninstalled and never mentioned it here. So I would like to find the source of the issue.

But I can understand the frustration part. Outside of it being a problem with the region I'm at a dead end anyway so I won't bother you with further troubleshooting steps. I'm going to set my test system to the same region as yours and see if I can replicate it. If I can't I'm out of ideas.