u-he

lengro · Post by **lengro** » Sun Jan 14, 2018 9:19 am

Hi

Trying out the Satin-demo - yeah, dangerous path for my economics

I can't map "mode: Flange -> Range ms" to my MIDI controller, everything else maps out fine. I have tried with Ableton and Bitwig.
Is that a bug?

EvilDragon · Post by **EvilDragon** » Sun Jan 14, 2018 9:41 am

Seems to work here in Reaper...

lengro · Post by **lengro** » Sun Jan 14, 2018 10:28 am

EvilDragon wrote:Seems to work here in Reaper...

So probably something in my setup.
In Bitwig I even can't map it to a control surface:

satin_flange_range_map.gif

Any ideas?

tasmaniandevil · Post by **tasmaniandevil** » Mon Jan 15, 2018 10:57 am

lengro wrote:In Bitwig I even can't map it to a control surface

The Flanger ms range parameter is not an host automateable parameter, this is why you cannot add it to the perform page in Bitwig.
We have to omit certain parameters from being host automation parameters, because they might be dangerous, e.g. producing audio glitches when being controlled by the host.
But you should be able to map the parameter to your MIDI CC controller.
Did you try it with Satin's MIDI learn feature (accessed by clicking the cogwheel in the upper right corner of Satin's GUI)?

lengro · Post by **lengro** » Mon Jan 15, 2018 10:52 pm

tasmaniandevil wrote:The Flanger ms range parameter is not an host automateable parameter, this is why you cannot add it to the perform page in Bitwig.

Ah - understood.

tasmaniandevil wrote:But you should be able to map the parameter to your MIDI CC controller.

Stupid me - I had placed Satin in an effects track which wasn't configured to receive MIDI input...

All is good now, thank you.

u-he

KVR Audio

Satin issue - map to MIDI controller?