VUMeter Plugin

[BoringName]

I couldn't replicate the issue on my other PC. But I've made a couple of changes that might work.

New version - VUMeter2.6.2.zip

Changes -
- Modified the handling of an empty skin path string at startup. (path to the skin file, this isn't a reference to the skinFolder setting in the XML).

There is no point installing this version unless you are having similar issues to Phred.

[sveakul]

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

Phred, I and I'm sure BoringName are reading them I assure you.  For me, it's just that they get a bit difficult to interpret sometimes as far as exactly what was or wasn't checked from my suggestions.  E.g., I know it was an extreme newbie type question to ask, but DID you double-check your antivirus on the test machine?  You didn't answer.  I was not trying to insult you but these are just the kind of things that even experts can completely forget about because they are looking at deeper issues.  In my last post, I thought I would begin from your what you described as your first new attempt instead of intertwining with the other redundant information you wrote in the same post.  For the sake of a clear "bulleted list" type of approach that would apply universally.

I'm sorry for the difficulties and at this point I will just lay low about it.  I hope 2.6.2 will help solve it for you.

[sveakul]

Noticed that oops' foo_vis_vumeter version 0.8.0 is now capable of playing hiccup's new meters directly from the *.rar file, complete with the option to use/not use the *.bin settings.

[phred]

Phred, I and I'm sure BoringName are reading them I assure you.

First off, an apology to sveakul and BoringName for my harsh, defeatist attitude last night. I know you guys are trying to help but I was getting frustrated and it showed in my tone.

Trying 2.6.2 doesn't solve the issue, but is perhaps providing another clue or two since it's now a different error message.
- brand new, naked, default configuration of MB Portable 3.6.9101 P
- installed the plugin via the "add plugins' button on the plugin preferences window
- exited MB and before restarting I checked and confirmed that the dll, default skins, and ini were all where they're supposed to be
- noticed that the ini entry for <skin folder> was empty but left it that way for this test
- launched MB and got this error before doing anything, which appears to be a different error than what I posted yesterday with v5.2.1 (...
System.OverflowException: Value was either too large or too small for an Int32...."

Code

MusicBee v3.6.9101.34338P  (Win10.0), 8 Dec 2024 11:22:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.VUMeter.DrawTextCustom(Int32 x, Int32 y, Int32 r, Int32 g, Int32 b, String font, Single fontSize, String fontStyle, String text)
   at MusicBeePlugin.VUMeter.OpenGLControl_OpenGLDraw(Object sender, OpenGLRoutedEventArgs args)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at System.Windows.RoutedEventArgs.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 SharpGL.WPF.OpenGLControl.DoRender()
   at MusicBeePlugin.VUMeter.RenderEventProcessor(Object myObject, EventArgs myEventArgs)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

- clicked 'copy error' and got error window "unable to coy the error text to the clipboard"
- copied it manually via CTRL-A, CTRL-C, and then pasting it here
- clicked OK on the 'unable to copy...' error window and it closed
- clicked OK on the initial error window and the window doesn't close. Yesterday with 2.6 and 2.5.1 the window closed and also crashed MB
- used task manager to exit MB
- edited ini file and added the proper path to the <skinFolder> element
- restarted MB and got what appears to be the same error

Code

MusicBee v3.6.9101.34338P  (Win10.0), 8 Dec 2024 11:29:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.VUMeter.DrawTextCustom(Int32 x, Int32 y, Int32 r, Int32 g, Int32 b, String font, Single fontSize, String fontStyle, String text)
   at MusicBeePlugin.VUMeter.OpenGLControl_OpenGLDraw(Object sender, OpenGLRoutedEventArgs args)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at System.Windows.RoutedEventArgs.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 SharpGL.WPF.OpenGLControl.DoRender()
   at MusicBeePlugin.VUMeter.RenderEventProcessor(Object myObject, EventArgs myEventArgs)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

- clicking OK on the error window does not close it and MB will not close unless I kill it with task manager
- removed all files relating to VUMeter plugin and restarted MB and it's fine
- It's not even noon here on the east coast of the US, but it's got to be five o'clock somewhere and I'm going to an adult beverage or two

[johnnyboy]

over complicated things by trying to extract files myself. Now I just used add plug in and chose the zip file and let the plug in do its thing.
Now trying it out    

[sveakul]

@phred : no apology is needed at all, don't worry about it!  I know how frustrating it is when something is so damn elusive despite every attempt to make it work.  I'm as baffled as you are at this stage as to why you are still getting those maddening errors after doing everything "according to Hoyle."  It's nuts.  When I've had similar experiences it usually turned out to be I just missed something simple, but in your case I can't see what that what might be--all the steps are in place.

If you try going to back to the last version of the plugin you know worked fine, and how you installed it, does that produce the same errors if you attempt installing it now?  I have most of the previous versions back to 1.6 that I could upload for you.

[johnnyboy]

Oh Dear!
I got the VU meters working using the primary sound driver output, all was good. So I changed to Wasapi Shared and the meters stopped but the audio was still working. I was aware of the probs with Wasapi so I changed the sound device output to virtual cable and launched Tuneblade. Disaster! no sound from my streamer. I had to delete   plugin and restart MB and my Streamer. I really think all this Hassle for what is just a cosmetic display is not worth the time. Will it get sorted?

[sveakul]

I use Wasapi Exclusive sound output (event mode) in MusicBee.  In the VUMeter context menu, I make sure "Event Mode" is checked, and "Ignore Replay Gain."  I have no problem at all with VUMeter or MusicBee.  That's all I can tell you.  If you use a calibrated-by-hiccup meter, they are a lot more accurate than "eye candy."

[johnnyboy]

  ok ill give it a try

[voodoopunk]

That's all I can tell you.  If you use a calibrated-by-hiccup meter, they are a lot more accurate than "eye candy."

Doesn't matter how "accurate" they are, unless you're recording they're still eye candy.

[BoringName]

First off, an apology to sveakul and BoringName for my harsh, defeatist attitude last night. I know you guys are trying to help but I was getting frustrated and it showed in my tone.

All good. It sucks when things don't work like they are supposed to and it's an annoying process trying to debug remotely.

- launched MB and got this error before doing anything, which appears to be a different error than what I posted yesterday with v5.2.1

Progress!!

Can you try this version - VUMeter_Phred.zip

All it does is move the error/loading message from the VUMeter window to status bar. I don't think this will solve your issue but it should get it further a long in the loading process, I'm expecting it should get you to a point where you can right click the window and select a skin but it will probably error when it's selected.

Can you give me the specs of your test system. The motherboard name and graphics card (if it has one). I think your system might be a bit old and not support the version of OpenGL I'm using. I haven't put any checks in place for that scenario and might explain all the issues.


edit: whoops, clicked post too soon.

The easiest way to determine the supported OpenGL version is running GPU-Z
It's a standalone app and will list the OpenGL version in the bottom right corner.

If you don't want to run a third party app you can get some of the info from windows.

- Press the `Windows key` + `R` to open the Run dialog box.
- Type `dxdiag` and press `Enter`. This will open the DirectX Diagnostic Tool.
- In the DirectX Diagnostic Tool, click on the "Display" tab.
- Look for the "Drivers" section, and you should see the "Feature Levels" listed.

Can you list the feature levels here please.

[BoringName]

Oh Dear!
I got the VU meters working using the primary sound driver output, all was good. So I changed to Wasapi Shared and the meters stopped but the audio was still working. I was aware of the probs with Wasapi so I changed the sound device output to virtual cable and launched Tuneblade. Disaster! no sound from my streamer. I had to delete   plugin and restart MB and my Streamer. I really think all this Hassle for what is just a cosmetic display is not worth the time. Will it get sorted?

When you change the sound output, you need to wait for the track to change so the stream Info supplied by Musicbee is updated. Probably a good idea to restart Musicbee anyway.

Nothing in VUMeter will stop the sound so that is a different issue.

Getting it sorted will depend on how much troubleshooting you want to do.
If you could be more specific on what you are doing it will make it easier.
At this stage it seems like the following -
Working.
Output - Wasapi Exclusive
Output Device - Primary Sound Driver

Sound works, VU meter doesn't.
Output - Wasapi Shared
Output Device - Primary Sound Driver
I believe this will probably work if you restart musicbee or even just change to a different track playing.

No sound, no VU meter.
Output - Wasapi Shared
Output Device - Virtual Cable (I have no idea what this is...)
No sound is not a VU Meter issue. I think if you solve that problem the VU meter should start working.

[phred]

Can you list the feature levels here please.

It's getting late, but wanted you to know I've read your latest suggestions. I've downloaded my "special" version and will install it tomorrow. I will also get you the PC specs at that time.  

Getting the feature levels was quick and easy (via dxdiag) so here it is:
Feature Levels: 10_0, 9_1
And it looks like it's a damn old driver (2012.) I'll see what I can do about updating it tomorrow.
Here''s the system specs taken from dxdiag:

Code

   Time of this report: 12/8/2024, 22:01:02
             Machine name: MUSICSERVER
               Machine Id: {E2B79A58-693E-49B6-8A22-F9E3BEF416B4}
         Operating System: Windows 10 Pro 64-bit (10.0, Build 19045) (19041.vb_release.191206-1406)
                 Language: English (Regional Setting: English)
      System Manufacturer: LENOVO
             System Model: 5536A1U
                     BIOS: LENOVO BIOS Rev: 1.0 (type: BIOS)
                Processor: Intel(R) Core(TM) i5 CPU         650  @ 3.20GHz (4 CPUs), ~3.2GHz
                   Memory: 8192MB RAM
      Available OS Memory: 7862MB RAM
                Page File: 1923MB used, 7155MB available
              Windows Dir: C:\WINDOWS
          DirectX Version: DirectX 12
      DX Setup Parameters: Not found
         User DPI Setting: 96 DPI (100 percent)
       System DPI Setting: 96 DPI (100 percent)
          DWM DPI Scaling: Disabled
                 Miracast: Not Available
Microsoft Graphics Hybrid: Not Supported
 DirectX Database Version: 1.0.8
           DxDiag Version: 10.00.19041.5198 64bit Unicode

[BoringName]

Feature Levels: 10_0, 9_1

It's not an exact indicator but there is a pretty good chance your device only supports OpenGL 3.1 and it needs 3.3 for the plugin to work. 3.3 was released in 2010 so it wasn't an issue I expected or checked for. I'm not sure I can actually check for it effectively.....even if I could there is nothing I can do on my end to make it work but I will update the plugin pages to specify that requirement.

Updating the driver might get you there.

It's hard to find the specs but based on this - List_of_Intel_graphics_processing_units I think that computer can only handle OpenGL 2.1 if you are using the onboard graphics.

[phred]

Progress!!

Maybe for you...

Can you try this version - VUMeter_Phred.zip

This gets really weird using the Phred version.
- all remnants of previous VUMeter have been removed
- opened MB >  Preferences > Plugins > Add Plugin
- navigated to the Phred version > clicked ok > clicked restart
- on restart, error window pops up and closes, taking MB with it
- most recent entries in error log are from two days ago
- launched MB again and go an info window stating that MB wasn't able to load preferences and recovered a backup
- plugin preferences window shows VUMeter 2.6.3 as installed
- arrange panels doesn't have an entry for VUMeter
- there are no VUMeter files or directories
- launched MB in an attempt to remove VUMeter from the plugins window and it crashed with a quick view of the error window and then MB disappeared
- still no new entry in error log
- launched one more time and tried to get a screenshot of the error window, but MB closes too fast
- deleted MB Portable and created new one with no library, plugins, skins, nothing but defaults
- installed VUMeter Phred and it shows in Plugin Preferences
- restarted MB
- arrange panels has a vumeter entry and I moved it to thte right sidebar (which is where I've been putting it all along)
- saved the panel arrangement and got a window "No skin folder found, set to default" Now there's progress!!
- before clicking on 'ok' in the 'no skins found' window, I looked for VUMeter files/directories and there are none. So much for progress!
- clicked 'ok' and a black panel appeared where the meter should be and an error window popped but I was able to get this before MB closed

and this from a little earlier

And there's no error message in the status bar as you can see in the full window screenshot.

I haven't started looking into drivers and OpenGL yet as I wan'ted to test the special phred version of the plugin. Since that was a bust, I'm going to take a break and may not deal with the drivers until tomorrow. But I do suspect BoringName is correct that the issue is the drivers being old as MB works fine on the test PC until I introduce VUMeter.