Maybe doing something wrong, but for Action that is controlled by e.g.: PrgCh 6
The Outbound MIDI msg is toggling me between 0 / 127
What ui type is the action?
Eg start-stop, but I’m not sure this behavior is exclusive to this only action
If it’s a switch (button, toggle) it will toggle 0 and 127.
Hmmmm… here is a bit of confusion then if using it with PrgCh as it sends a specific value to toggle but ActionOut outputs then PrgCh 0 and 127 (that “means” something different) meanwhile the specific value is set for Out.
Unfortunately my MIDI foot switch sends PG’s only, but I can trick out “everything” 
Meanwhile maybe for PrgCh values, … out value should stay somehow as set (or 0, and $set). Or?
can you show me a picture? Now you talk about input (footswitch)…wasn’t this about output?
Yes, and input brings the need for output (status update)
While it seems toggle-types and PrgCh ctrl aren’t obvious friends in term of status-update-via-output.
(Will describe more if that would help, just didn ’t wanted to write a litany)
Still don’t get it…
Note that Program Change is a one byte value, as opposed to other stati (except Channel Pressure (“Aftertouch”)). So there is no data2. Maybe that is what confuses?
Sure! That’s exactly my point too!
So the new action-output shouldn’t send PrgCh 0/127 when it’s output-pre-set value is “PrgCh#6”
While got to my laptop, here is an example (just ignore beginning / ending) (don’t get confused by some details… all are by concept)
(p.s.: I personally solved my problem, but I still feel the question valid )
If I understood your issue is that for every prgchng 6 sent from streamdeck to VST, you need a prgchng 6 to be sent from VST to streamdeck, but as the action is set as a toggle, VST ignores the data1 out set to 6 and only send as a toggle 0 and 127 then 0 and then 127 (on- off - on - off) … right??
Hi @ciro1983811 , in short: YES
(Longer: I’m routing my BT-Ft-Sw and SteamDeck to the same loopMIDI, to trick out VL can only assign 1MIDI Input/Action 
then I can use the same setup/config when going alone or with buddy. Meanwhile could custom-reconf the footSW to NoteOnOff 
)
But what should it send?
If you propose that it should send pgm chg #6 each time, that is a bad idea from MIDI specs point of view. Almost every stage in a MIDI processing chain has a filter somewhere that says “if the exact same MIDI channel event is to be sent to the same output/instrument, ignore it”. Any synth or instrument, plugin or physical MIDI will ignore it anyway.
Now of course this is a different application, but the rules apply. And the trigger for the action will not even make it in the first place - because it had been executed already.
Reading again, sorry, misinterpreted your post. But sending pgm chg 0 or 127 seems weird for a toggle switch…no idea how to handle this yet.
1 Like
Good point, need to agree! Just somehow can’t find toggle prg.ch 0-127 is the best solution either. Hmmm. Maybe 0 and $reqested value, is it a bad idea?
Even more complex…
As mentioned, I was personally able to solve this already, I just kept discussing hoping some idea will came up, that could help to avoid other user’s confusion, the “what is going on here” feel, I had for a while (before realised here is a logical confusion).