How comes that when you map the Coarse tunings in Operator with live.remote, it becomes continuous, while when mapped with MIDI, it's stepped, as when you use the mouse ?
I'd like to move with integer ratios.
Mapping of Operator's Coarse Tuning parameters
-
- Posts: 6050
- Joined: Mon May 15, 2006 12:15 pm
Mapping of Operator's Coarse Tuning parameters
MacBook Pro 13" Retina i7 2.8 GHz OS 10.13, L10.0.1, M4L.
MacStudio M1Max 32Go OS 12.3.1
MacStudio M1Max 32Go OS 12.3.1
Re: Mapping of Operator's Coarse Tuning parameters
What do you mean by continuous?
Whichever method I use, I only see integer values.
Whichever method I use, I only see integer values.
-
- Posts: 6050
- Joined: Mon May 15, 2006 12:15 pm
Re: Mapping of Operator's Coarse Tuning parameters
Yeah, you see integer values.
But the pitch you hear slides continuously. Try mapping a (M4L) LFO to a single oscillator Coarse knob.
But the pitch you hear slides continuously. Try mapping a (M4L) LFO to a single oscillator Coarse knob.
MacBook Pro 13" Retina i7 2.8 GHz OS 10.13, L10.0.1, M4L.
MacStudio M1Max 32Go OS 12.3.1
MacStudio M1Max 32Go OS 12.3.1
Re: Mapping of Operator's Coarse Tuning parameters
I can hear it too.
Operator uses continuous values internally, artificially stepped when you access the device from the outside by turning the dial, in automation (which uses a grid), and via midi mapping. Max reaches the inside of a device and thus uses the continuous value.
Operator uses continuous values internally, artificially stepped when you access the device from the outside by turning the dial, in automation (which uses a grid), and via midi mapping. Max reaches the inside of a device and thus uses the continuous value.
-
- Posts: 6050
- Joined: Mon May 15, 2006 12:15 pm
Re: Mapping of Operator's Coarse Tuning parameters
I get it, but still it could work the 'stepped' way anyway. I think this it what you assume when you map it, isn't it ?
I'll try to figure out how it's mapped and try to revert the 'absolute' steeped values so I can make a special mapper for this parameter (that seems to be the only one to work that way in all devices).
Because it's a lot of fun to modulate...
I'll try to figure out how it's mapped and try to revert the 'absolute' steeped values so I can make a special mapper for this parameter (that seems to be the only one to work that way in all devices).
Because it's a lot of fun to modulate...
MacBook Pro 13" Retina i7 2.8 GHz OS 10.13, L10.0.1, M4L.
MacStudio M1Max 32Go OS 12.3.1
MacStudio M1Max 32Go OS 12.3.1