Bug in the 3.2.0.5 API?

[stoepie]

Thanks, I checked. Yes, I'm pointing to the correct dll. I think.

The location

VBVMR unintall.png (31.7 KiB) Viewed 27335 times

The DLL

VoicemeeterRemote64.dll.png (101.74 KiB) Viewed 27335 times

I did a complete reinstall to make sure I had just one such DLL. This one has the version I noted, and yields 0 as result regardless of the button state. Also, I can't control buttons anymore.


By the way, during install, the installer splash screen shows Windows 10, while I am on Windows 11... is it just a splash screen or some indication?

Edit: I added some code to use the registry entry, and this gives the same result (does not work).

Suggestions are welcome.

[Vincent Burel]

the vmr_client.exe from 2021 (in Voicemeeter Remote API package) works with latest version x.1.1.9, so you may try it and check the source code to see what you are doing wrong: https://github.com/vburel2018/Voicemeet ... n/example0

MacroButtonsStatus.png (155.34 KiB) Viewed 7003 times

[stoepie]

Ah yes... more insights.

Thanks for the great help, your tool was a great idea, it showed me I did read the proper value - then I found this:

It's just like the commands under "Request For Initial State" do not run anymore at Macro Button startup. Or, too early and get overwritten after.

If I put this in:

Request For Initial State.png (2.99 KiB) Viewed 27306 times

This does not get done. State and color are unchanged*. This did work in an earlier version. When this isn't done, my script which depends on this, can't do what I want and appears to fail. But the reason is not the script nor the API, it's that request initial state that seems to not work, or at least, has unexpected behaviour.

Again your ideas are highly appreciated.


* = This version of Macro Buttons does partially remember button states, which the earlier versions did not do. Colors are not remembered until the mark to "Store Last Button State" is checked. Major differences, in my opinion..... breaking functionality.

[stoepie]

The fix is easy.

Request For Initial State must start with some delay, otherwise setting button state and color is not done (or done but gets overwritten with the new function in Macro Buttons that partially remembers the states of buttons).

I found that 100ms works, I will use 1000ms.

Can I query if app startup is done? I hate using timeouts..

Or, can Macro Buttons first finish initializing and then launch the Request for initial state?

[Vincent Burel]

It's just like the commands under "Request For Initial State" do not run anymore at Macro Button startup. Or, too early and get overwritten after.

Ok ,this is more precise, i will take a look on this case to fixe it in the next update.

[stoepie]

Thanks for your great support and tips that pointed me in the right direction. I would not have found it by myself.

Also thanks for taking a fix in consideration.

Do you have a 'buy me a beer'-button?

-David