Trying to understand why certain issues are happening
Posted: Fri Sep 15, 2023 10:44 am
We've been integrating with VoiceMeeter for a number of years now and rarely had any issues, so never had to delve too deeply into anything API related.
However we recently had a user say they couldn't get the Command.Button(0).State=1 command to work. Commands like Strip(0).Mute=1 worked, but the Macro Buttons did nothing.
I tried myself and this was indeed correct.
So after much fiddling and testing I decided to uninstall Voicemeeter, restart my machine, re-install the latest version, restart my machine again and then copied the voicemeeterremote.dll into our application folder, as per usual, and now it all seems to be working.
What I'm trying to figure out though, before it was working, when sending a command that failed, the call to VBVMR_SetParameters would return -2, and I can't find anything anywhere that tells me what that return code means. In it's working state it returns 0, which I take as good.
Are there any logs generated by voicemeeterremote.dll or VoiceMeeter itself that can be viewed?
However we recently had a user say they couldn't get the Command.Button(0).State=1 command to work. Commands like Strip(0).Mute=1 worked, but the Macro Buttons did nothing.
I tried myself and this was indeed correct.
So after much fiddling and testing I decided to uninstall Voicemeeter, restart my machine, re-install the latest version, restart my machine again and then copied the voicemeeterremote.dll into our application folder, as per usual, and now it all seems to be working.
What I'm trying to figure out though, before it was working, when sending a command that failed, the call to VBVMR_SetParameters would return -2, and I can't find anything anywhere that tells me what that return code means. In it's working state it returns 0, which I take as good.
Are there any logs generated by voicemeeterremote.dll or VoiceMeeter itself that can be viewed?