Reaktor5 inside vst~: possible to control snapshot morphing via MIDI?
I'm trying to map my MIDI controller to the snapshot morphing function in Reaktor. This parameter is MIDI-controllable when running Reaktor as a standalone, but doesn't produce a parameter index or value at the relevant vst~ outlet when changed, so I'm not able to control it via the usual method of sending a list of [index value]. Has anyone had success with this? How about with the two buttons on either side of the snapshot-morphing slider that control the button & switch parameters?
Thanks in advance,
Robert
I think you can control snapshot morphing by sending CC messages to the Reaktor vst~ .
Just set and activate a CC number in the 'Morph Ctrl' field of the CONNECT section.
That's what I originally tried. That works when using Reaktor as a standalone, but vst~ interprets the cc messages as selecting presets, so instead of morphing between presets it just moves through the preset menu.
It seems like you are sending pc (program change) instead of cc (controller change).
Posting your patch may be helpful.
reaktor vst in max... why didn't i think of this before? mind blown!
Thanks, Broc. I don't think that's the issue, but here's the patch.
In your patch, the numbers coming from [ctlin 17 1] have exactly the same effect as the preset numbers.
For sending cc to vst~ you need to use the appropriate format like you did for notes in 'p midi'.
Of course, that makes perfect sense. I've now tried that a few different ways (using [midiformat], [prepend midievent], message object with "midievent 176 17 $1") but still no luck. I tried different channel numbers as well as scaling the message down to 0.-1. as is done with other parameters.
Again, it works as intended as standalone. Here is the patch, slightly modified. Thanks again for your assistance.
Which Max version?
Just did a quick test. It works for me in Max 7 but *not* in Max 5.
v7.0.2. Hmm, strange.
your patch works for me as well in Max 7.0.3. Did you set Morph Ctrl to 17 in Reaktor?
Brad
Thanks for the confirmation, Brad. I just reopened the patch and it's working now – not sure what was missing before. Anyway, glad that it's working as intended now!