You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is expected as a statement such as
"map 0 gain" does not contain the assigned midi channel , so saving and retrieving this history will not re-connect a midi channel to a control (ie. gain).
It would be extremely useful if I was able to set the midi channel I want to connect to a controller. F.e.:
map 0 gain 1 10
this could potentially connect "gain" of FXid "0" to midi control #10 , on midi channel #1).
The text was updated successfully, but these errors were encountered:
The way that we store the session today, saving the command line history, is going to be deprecated. But, you are right about the map command, your suggestion is quite usuful. TODO added. Thanks.
This is expected as a statement such as
"map 0 gain" does not contain the assigned midi channel , so saving and retrieving this history will not re-connect a midi channel to a control (ie. gain).
It would be extremely useful if I was able to set the midi channel I want to connect to a controller. F.e.:
map 0 gain 1 10
this could potentially connect "gain" of FXid "0" to midi control #10 , on midi channel #1).
The text was updated successfully, but these errors were encountered: