Macro button initial states and controlling other buttons from other buttons

[cattywampus]

Hi

So I use Voicemeeter Macros along with an APC mini midi controller and an Elgato Stream Deck. Everything works fine but I cannot understand how to manipulate macro buttons themselves from either a) other macro buttons, or b) setting the state of the macro button at load up.

I will try and explain an example of what problem I am running into:

1. I have a macro button that is set to toggle A2 on strip 0 on and off [ eg. Strip[0].A2 = 1 ]
2. I also, as part of the button ON/OFF triggers tell my APC mini midi controller to change light colour [ eg. System.SendMidi("out1", "note-on", 1, 48, 01); ]
3. I have set the initial state to be whatever I want that button the APC mini to be, however, I do not know how to make the macro button state itself reflect the state of whatever I set in the ON/OFF sections.

This is problem because when I first boot up my PC for the day, all the toggles are set correctly in Voicemeeter (i.e. Strip0 A2 is enabled, Strip1 A3 enabled - just as it should be)... and the lights on my midi controller are set to their initial states as set in the macro buttons...but the macro buttons themselves are not enabled to match (i.e. lit up in the macro buttons app). This means the macro button state does not match the state that the macro button is used for - and so using keyboard shortcuts to toggle the Macros causes things to be come out of sync - i.e. the lights on the midi controller show that A2 is enabled, but because the macro buttons initial state is off, everything becomes unmatched and I have to do some messing around to get everything in line.

I understand what I just typed above may not make sense. The long and short of it is this:

1. Is there a way to tell a macro button to be enabled when loading the Macros app?
2. Is there a way to toggle another macro button from another macro button?

Thanks

[cattywampus]

Bump

[Vincent Burel]

we could add an instruction like this in the initial script

button.state = 1; to set the state of the current button
(but it would execute script for ON state
while button.state = 0; would execute script for OFF state)

to change the state of another button we could have this syntax:
button[0].state = 1; would push the first button...

i'm going to think about...

[cattywampus]

This would be awesome to include and is pretty much what I personally would find incredibly useful.

Would it be possible to take it one step further though and be able to toggle buttons from other buttons? I guess each individual button would need a unique name to be able to be referenced. Would be insane if you could implement that Thanks!

[Vincent Burel]

we will use logical number (that i will display in edit box too)...

but i've last question: does it make sens to change the button state without executing the related script ?

Button[0].state = 1; will set the button in ON mode and execute "Script_ON"
Button[0].state = 0; will set the button in OFF mode and execute "Script_OFF"

Button[0].StateOnly = 1; would set the button in ON position without executing the script

ok, finally i replied to my question! I will do that in next update...

[cattywampus]

Sweet. Can't wait! Thanks for the quick response. Great software.

[cattywampus]

Hi there,

Just wanted to ask whether this was something that would be added in the near future or whether you'll not be doing it?

Many thanks!

[TomW1605]

Hi

I'm also wondering if this will be coming soon. ether this or remembering the buttons states at shutdown (just in a text file) and reloading these states at start up

ether of these would make keeping hardware MIDI controllers in sync with VoiceMeeter across shutdowns a lot easier.

[Vincent Burel]

yes, as soon as possible... our planning is complicated.