ArrayArrayArrayArrayArray BrainModular BrainModular Users Forum 2007-01-11T10:57:35+02:00 https://brainmodular.org/forums/app.php/feed/topic/218 2007-01-11T10:57:35+02:00 2007-01-11T10:57:35+02:00 https://brainmodular.org/forums/viewtopic.php?t=218&p=1005#p1005 <![CDATA[No action taken on midi message until value "crosses" existing value.]]> I'll think about it.

Statistics: Posted by senso — 11 Jan 2007, 09:57

]]> 2007-01-10T23:58:22+02:00 2007-01-10T23:58:22+02:00 https://brainmodular.org/forums/viewtopic.php?t=218&p=1000#p1000 <![CDATA[No action taken on midi message until value "crosses" existing value.]]>
Just for info, Live 6 has implemented quite a good way to deal with that, I don't know if it would be easy to implement in Usine, but here's a excerpt of the Live 6 manual:

"When MIDI controls that send absolute values (such as faders) are used in a bank-switching setup, where they address a different destination parameter with each controller bank, you
will need to decide how Live should handle the sudden jumps in values that will occur when moving a control for the first time.
Three takeover modes are available:
None As soon as the physical control is moved, its new value is sent immediately to its destination parameter, usually resulting in abrupt value changes.
Pick-Up Moving the physical control has no effect until it reaches the value of its destination parameter. As soon as they are equal, the destination value tracks the control's value 1:1.
This option can provide smooth value changes, but it can be difficult to estimate exactly where the pick-up will take place.
Value Scaling This option ensures smooth value transitions. It compares the physical control's value to the destination parameter's value and calculates a smooth convergence of the two as the control is moved. As soon as they are equal, the destination value tracks the control's value 1:1."

Rgds,

B.

Statistics: Posted by bmoussay — 10 Jan 2007, 22:58

]]> 2007-01-10T10:12:57+02:00 2007-01-10T10:12:57+02:00 https://brainmodular.org/forums/viewtopic.php?t=218&p=996#p996 <![CDATA[No action taken on midi message until value "crosses" existing value.]]>
Concerning the name: I think both "NULL mode" and "Soft take over" are bad names not telling what's really happening, but I'm afraid I can't come up with a better suggestion. Has anyone else? Maybe one of the native English speakers?

Statistics: Posted by bsork — 10 Jan 2007, 09:12

]]> 2007-01-09T19:28:35+02:00 2007-01-09T19:28:35+02:00 https://brainmodular.org/forums/viewtopic.php?t=218&p=982#p982 <![CDATA[No action taken on midi message until value "crosses" existing value.]]> I will check It.

In Reaktor, they call this option "Soft take over".
What is the good term?

Statistics: Posted by senso — 09 Jan 2007, 18:28

]]> 2007-01-09T15:30:54+02:00 2007-01-09T15:30:54+02:00 https://brainmodular.org/forums/viewtopic.php?t=218&p=980#p980 <![CDATA[No action taken on midi message until value "crosses" 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...

Statistics: Posted by bsork — 09 Jan 2007, 14:30

]]> BrainModular BrainModular Users Forum 2007-01-11T10:57:35+02:00 https://brainmodular.org/forums/app.php/feed/topic/218 2007-01-11T10:57:35+02:00 2007-01-11T10:57:35+02:00 https://brainmodular.org/forums/viewtopic.php?t=218&p=1005#p1005 <![CDATA[No action taken on midi message until value "crosses" existing value.]]> I'll think about it.

Statistics: Posted by senso — 11 Jan 2007, 09:57

]]> 2007-01-10T23:58:22+02:00 2007-01-10T23:58:22+02:00 https://brainmodular.org/forums/viewtopic.php?t=218&p=1000#p1000 <![CDATA[No action taken on midi message until value "crosses" existing value.]]>
Just for info, Live 6 has implemented quite a good way to deal with that, I don't know if it would be easy to implement in Usine, but here's a excerpt of the Live 6 manual:

"When MIDI controls that send absolute values (such as faders) are used in a bank-switching setup, where they address a different destination parameter with each controller bank, you
will need to decide how Live should handle the sudden jumps in values that will occur when moving a control for the first time.
Three takeover modes are available:
None As soon as the physical control is moved, its new value is sent immediately to its destination parameter, usually resulting in abrupt value changes.
Pick-Up Moving the physical control has no effect until it reaches the value of its destination parameter. As soon as they are equal, the destination value tracks the control's value 1:1.
This option can provide smooth value changes, but it can be difficult to estimate exactly where the pick-up will take place.
Value Scaling This option ensures smooth value transitions. It compares the physical control's value to the destination parameter's value and calculates a smooth convergence of the two as the control is moved. As soon as they are equal, the destination value tracks the control's value 1:1."

Rgds,

B.

Statistics: Posted by bmoussay — 10 Jan 2007, 22:58

]]> 2007-01-10T10:12:57+02:00 2007-01-10T10:12:57+02:00 https://brainmodular.org/forums/viewtopic.php?t=218&p=996#p996 <![CDATA[No action taken on midi message until value "crosses" existing value.]]>
Concerning the name: I think both "NULL mode" and "Soft take over" are bad names not telling what's really happening, but I'm afraid I can't come up with a better suggestion. Has anyone else? Maybe one of the native English speakers?

Statistics: Posted by bsork — 10 Jan 2007, 09:12

]]> 2007-01-09T19:28:35+02:00 2007-01-09T19:28:35+02:00 https://brainmodular.org/forums/viewtopic.php?t=218&p=982#p982 <![CDATA[No action taken on midi message until value "crosses" existing value.]]> I will check It.

In Reaktor, they call this option "Soft take over".
What is the good term?

Statistics: Posted by senso — 09 Jan 2007, 18:28

]]> 2007-01-09T15:30:54+02:00 2007-01-09T15:30:54+02:00 https://brainmodular.org/forums/viewtopic.php?t=218&p=980#p980 <![CDATA[No action taken on midi message until value "crosses" 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...

Statistics: Posted by bsork — 09 Jan 2007, 14:30

]]>