Posted: 09 Jan 2007, 14:30
Would it be possible to have an option on the interface elements where an incoming value controller value don't have any effect until it matches the existing value?
Many controllers (like my Ozonic) have a similar feature; M-Audio calls it "NULL" mode: If one for instance sends a CC-value of 64 from fader X in program 1, change to program 2 and push fader X up to send a CC-value of 127, change back to program 1 and move fader X down, no values are sent from fader X before it's halfway down and "crosses" CC-value 64.
In the case of Usine, this sort of behaviour would as far as I can tell only apply where the assign mode is "Absolute", and then it should act upon the real value of the interface element, not the CC value as such.
An example:
A fader has been set up to receive a CC message and output integers from 1 to 4. I haven't checked, but I suppose the resulting values would be like this:
CC input > Fader output
0-31 > 1
32-63 > 2
64-95 > 3
96-127 > 4
If the last CC value received was 40, but input from something else in the patch, from the computer keyboard or from the mouse has changed the fader value from 2 to 3, sending new CCs wouldn't change anything before the value was in the range 64-95. That would imply that if one wants to set the value from 3 back to 1 or 2, the controller must first be moved up before being turned down again.
I'd like to add that this is not a big issue for me, and I haven't got a clue as to whether it would take a lot of work to implement, but as it seems that Olivier is working quite a bit on improved MIDI handling, I thought I'd chime in with a suggestion as well...
Many controllers (like my Ozonic) have a similar feature; M-Audio calls it "NULL" mode: If one for instance sends a CC-value of 64 from fader X in program 1, change to program 2 and push fader X up to send a CC-value of 127, change back to program 1 and move fader X down, no values are sent from fader X before it's halfway down and "crosses" CC-value 64.
In the case of Usine, this sort of behaviour would as far as I can tell only apply where the assign mode is "Absolute", and then it should act upon the real value of the interface element, not the CC value as such.
An example:
A fader has been set up to receive a CC message and output integers from 1 to 4. I haven't checked, but I suppose the resulting values would be like this:
CC input > Fader output
0-31 > 1
32-63 > 2
64-95 > 3
96-127 > 4
If the last CC value received was 40, but input from something else in the patch, from the computer keyboard or from the mouse has changed the fader value from 2 to 3, sending new CCs wouldn't change anything before the value was in the range 64-95. That would imply that if one wants to set the value from 3 back to 1 or 2, the controller must first be moved up before being turned down again.
I'd like to add that this is not a big issue for me, and I haven't got a clue as to whether it would take a lot of work to implement, but as it seems that Olivier is working quite a bit on improved MIDI handling, I thought I'd chime in with a suggestion as well...