To reverse polarity, simply insert a map controller event then set the parameters as follows
input 0-127
output 127-0
What does "Allow a value to be assigned for toggling this rather than treating it like (+/-). " mean?
I think the mute event solution is simply to add a range to the mute event. That way the user can specify which range of input values to pass to the mute event and which to ignore. So if you are just looking for a controller event with value 127 you could set your input range from 127 to 127. All controller events with values other than 127 (mute button up for example) would be ignored by the remote control processor.
You are saying that the track number is equal to the MIDI channel with the mute event at least. Right?
GarySome1 wrote:But then how do I un-mute?
<MIDI Status = Bn><Data Byte 1 = 0m><Data Byte 2 = Value>
where n = MIDI channel and m=track number (0-7).
So, the channel is in the MIDI status byte and the track number is in the low nibble of "Data Byte 1" (the controller number).
It is important to note that Solo and Record are different than Mute Track on the US-428. They expect to affect the last selected track as opposed to including the track number in the message.
This is uncalled for. Believe me, I am very familiar with this information
Well if the upper nibble is 0 then the track is the controller number. Which is pretty weird in my opinion.
...
Very strange.
GarySome1 wrote:But then how do I un-mute?
<MIDI Status = Bn><Data Byte 1 = 0m><Data Byte 2 = Value>
where n = MIDI channel and m=track number (0-7).
It is important to note that Solo and Record are different than Mute Track on the US-428. They expect to affect the last selected track as opposed to including the track number in the message.
Return to Metro/LX/SE Feature Request
Users browsing this forum: No registered users and 5 guests