Hi! I have defined a controller to the 1st channel
Mute/unmute works like expected. But when I press the controller on the external controller Solo gets first selected but stays there and is not un-solo by the external controller like the mute toggle anymore. Dont get confused that it is the same controller number. the midi channel is different. I also checked it with the midi monitor. I get the correct controller messages from the external controller.
Some additional information:
That’s the messages, when I monitor the controller directly
first 2 lines is mute/unmute
second 2 lines is solo/un-solo
When I use the connection (global layer) to virtual midi I mointor that
first 2 lines is mute/unmute
the rest is after press only solo
And another strange behaviour using a virtual midi instead of direct midi port. When I assign a controller to “main volume” in Application, everything works fine and it moves the correct channel in the mixer. In case i use the detour with virtual midi it now moves a different channel in the mixer.
It moves the channel assigned in Actions and Shortcuts. If the “MAIN” channel that is controlled via the “Apllication” “Main Volume” is at the same position (i.e. “1st Channel”), then it does the same.
Thanks for your reply.
I found the reason for this behaviour. I had assigned the same controller in global stack for virtual midi in. So global stack wins and “Main” never get the information when I add the same controller by accident. As it is never a good idead to have the same controller assigned to 2 channels, I would expect, that both moves.
Hi! Any news to the first and second post in this thread?
