I’m using the Muse as my Midi controller. Programs like Omnisphere already have beautiful maps already set up for it and dozens of other popular synths. But you have to roll your own for most others. I was programming Arturia’s Pigment synth (ver 7) and they’ve now added a visually simplified “play mode” which gives you a finite set of controls for digging into a preset and experimenting without, as a reviewer in this months SOS said feeling like you’re “running a railway signaling system”.
It all works brilliantly enough and I mapped the filter, resonance, attack, delay, sustain, and release straight away. But unlike when controlling the Muse itself, the Muse has no idea what the value of, say, attack is in my virtual synth. So of course, if I push the attack fader up, it immediately begins increasing the virtual instruments attack. If you were 90% on the VI but all the way down on the fader when you began, you would have the full throw of the fader but only be controlling the area between 90% and 100%. Once you’ve topped out, then the fader would control the full 100%-0% range.
Now I understand why this works the way it does, but I’m wondering if there is a protocol where the ‘setting’ of any mapped controlled is transmitted to a synth so the synth would know when to actually start sending an increase or decrease attack signal back to the DAW. Even Omnisphere, which has presets for the Muse doesn’t engage in this two-way feedback method.
Yes, I have too much time on my hands . . . .