So are you saying that I can't have any more than two VU Meter (DirectX 12) entries? (As shows below)

So are you saying that I can't have any more than two VU Meter (DirectX 12) entries? (As shows below)

I'm using 6 locations in my skin where VU Meters can be displayed (simultaneously). All can be different skins or the same.
So I guess this is relevant for me too.

You'll see all 6 but, as above, you'll see only 2 different configurations at any given time.

By configuration I mean a unique combination of layout, mode, levels and the selected skin.

One small clarification for my understanding ... if I have 2 VU meters using the "same skin", will they count as 1 config or 2 configs?
If they are counted as 1 config, then if I change the skin of either one of the VU meter, then it becomes 2 configs?

oops, what are the chances of making more than 2 configurations in the future?

On a different note, Darkone theme has this command for changing the colors of the old vu meter...
Is there a substitute for "Analog VU Meter skins", with the new vu meter?

oops, what are the chances of making more than 2 configurations in the future?

Chances are good. I already made the extension. You'll get as many unique configurations/instances as your computer memory will let you

On a different note, Darkone theme has this command for changing the colors of the old vu meter...
Is there a substitute for "Analog VU Meter skins", with the new vu meter?

If I look at the resources for the original, it is using "IVUMeterWindow" Automation interface to create the menu. This is not something I have implemented.

Now at the risk of being greedy, this would be nice too. Because this is the only thing that is keeping the Darkone theme from going 64 bit.
Unless I can write a script that will change the vu meter colors without the fb.RunMainMenuCommand method.

Quote from: Majestyk on 2024-12-01 04:31:23

Now at the risk of being greedy, this would be nice too. Because this is the only thing that is keeping the Darkone theme from going 64 bit.
Unless I can write a script that will change the vu meter colors without the fb.RunMainMenuCommand method.

I do not know how to do it. All of my attempts have stalled and there is no straightforward documentation for this use case or example. When I load the panel through ActiveX, the object is empty and none of the functions dispatch. It loads successfully and I've checked so many ways to ensure the TLB file is in the right section and ID in the resources. Of all the other component DLLs I've dumped no one seems to export DllGetClassObject() or similar functions. I don't know if they're working with the registry or there is some back channel that I'm not aware of. So, it is a mystery at this point how it is supposed to work, and I'd rather put my energy into something with clearer line-of-sight. Sorry for venting.

If you write a script and you're targeting the original component, using RunMainMenuCommand() seems odd. The component has a LoadSkin() and similar functions to list out what it has that you could just call directly to do what you want.

Modifying the main menu and executing menu commands does not involve ActiveX scripting. What the original component seems to be doing is grouping the "skins" by directory (no nesting appears to be supported). The default panel included in the resources and anything placed alongside the DLL are in the "<Default>" group. The rest are just placed in a different "group" based on the folder name. The context menu is similarly affected, adding a new group popup that selects the directory/group to appear in the list directly below. I need to investigate in the SDK where those functions are.

Try 0.7.5 where I think the multi-instance situation has improved. Also, I've implemented the main menu "skin loader". The menu entries are hidden by default. You can show them by holding the shift key down while opening the View menu and you should see them in the Keyboard Shortcuts preferences page as shown above. Enjoy!

1) The Layout settings reset upon bootup and default to Left + Right (H). It only does this if you have more than 1 VU Meter. (The first VU Meter saves fine)
2) There are two VU Meter (Direct X 12) entries in the Columns UI Layout. (As seen the 1st image...this is not a big deal)
3) I don't see any skin loader (pressing shift main menu/view) or anything in Keyboard shortcuts. (As shown in the 2nd and 3rd images)

Quote from: Majestyk on 2024-12-04 03:42:12

1) The Layout settings reset upon bootup and default to Left + Right (H). It only does this if you have more than 1 VU Meter. (The first VU Meter saves fine)
2) There are two VU Meter (Direct X 12) entries in the Columns UI Layout. (As seen the 1st image...this is not a big deal)
3) I don't see any skin loader (pressing shift main menu/view) or anything in Keyboard shortcuts. (As shown in the 2nd and 3rd images)

Other than number 2, I can't reproduce your reporting. I would not have claimed I fixed something or that I added the menu feature mirroring almost 1:1 the older component if I didn't test it out a bit. Please check that you have installed the correct component version. In Columns UI, I tested 4 windows plus a fifth default UI one undocked. They all save across restarts and fullscreen'ing. And the menu is dynamically-generated, so responds to rescans as well.

2) There are two VU Meter (Direct X 12) entries in the Columns UI Layout. (As seen the 1st image...this is not a big deal)

Quote from: Majestyk on 2024-12-04 03:42:12

2) There are two VU Meter (Direct X 12) entries in the Columns UI Layout. (As seen the 1st image...this is not a big deal)

Problem number 2 is root caused and fixed. Very good eye to notice! It's on a version with the updated foobar2000 SDK and the latest LZMA SDK. I'm bashing it thoroughly through the night to make sure there are no obvious escapes or problems.

Here is what the menu looks like and the multiple windows. Opening and closing the program keeps all changes for me. Make sure your theme is not modifying something. I can't help you if it does because, as you can see, I test (and just generally play/listen) on a vanilla barebones configuration to eliminate uncertainty:

I just created a new fb2k 64 bit portable (no theme). I put my bin file folders in the default vumeter folder and I still don't get that "Anlog VU Meter skins" dir.

That's weird that I don't get that. Can you do me a big favor? If you have the time can you zip up your test build and post it? You can PM me a link if you don't want it public.

I just created a new fb2k 64 bit portable (no theme). I put my bin file folders in the default vumeter folder and I still don't get that "Analog VU Meter skins" dir.

Yes, I pressed SHIFT. (I've always known about the hidden shift key options)

I notice the new VU meter needle movement don't really mimic the old analog component. (Yes, I know they are different)
I installed fb32bit and placed both components side-by-side, and played a track to demo the differences (below animated GIF).
Anyone know what "tuning" would bring the new VU meter closest to the behavior of the old analog component?

Any and all tips and suggestions welcomed!

1) The Layout settings reset upon bootup and default to Left + Right (H). It only does this if you have more than 1 VU Meter.
2) There are two VU Meter (Direct X 12) entries in the Columns UI Layout.
3) I don't see any skin loader (pressing shift main menu/view) or anything in Keyboard shortcuts.

You won't unless at least one panel instance is active/added. I would consider it unethical to scan or traverse the filesystem when the component is loaded (by foobar2000) but unused. The scan is triggered on the first component window creation; it only "appears" to happen at program start when a panel was already loaded into the theme.