Cycling 74 » Topic: Send OSC to VST~Plugin (N.I. Reaktor)

Send OSC to VST~Plugin (N.I. Reaktor)

hgh — Mon, 23 Jul 2012 14:14:32 +0000

Hi,

i wants to send numbers higher than 127 to Reaktor (implementet with VST~in my Max-Patch). So Midi is not enough, because higher Values than 127 with an high resolution are not possible.

Is there a way to control Native Instruments Reaktor in a Max/MSP-Patch with scales OSC-Values? How to do that?

Best hgh

Re: Send OSC to VST~Plugin (N.I. Reaktor)

broc — Mon, 23 Jul 2012 14:45:01 +0000

Reaktor can handle OSC only in standalone mode, not when running as vst plugin.

Re: Send OSC to VST~Plugin (N.I. Reaktor)

hgh — Mon, 23 Jul 2012 14:57:17 +0000

Thx…

is there a way to send Midi with more than 127 Steps?

I´ve heard NRPN-Midi Setup allows more Steps… [xBendin] in Max for example receives higher resoluted Midi-Values from Pitchbendwheel…

Best,
hgh

Re: Send OSC to VST~Plugin (N.I. Reaktor)

ShelLuser — Mon, 23 Jul 2012 16:07:13 +0000

You could always design a protocol yourself. While 127 maybe the maximum value in MIDI you could consider sending a list instead. I could imagine a ‘minimum 2 part list’; first number determines the amount of numbers and the rest is simply a list of values. Or sent out multipliers and then the value to multiply.

I think there are plenty of workarounds which you can work out.

Re: Send OSC to VST~Plugin (N.I. Reaktor)

broc — Mon, 23 Jul 2012 18:07:10 +0000

Notice that Reaktor VST can also be controlled by parameters which are represented as ‘automation ID’ of the GUI elements. To change a parameter send the list to the plugin, where value is a float number with range 0-1.

Re: Send OSC to VST~Plugin (N.I. Reaktor)

hgh — Tue, 24 Jul 2012 06:39:56 +0000

Thanks. That sounds very interesting, broc!!!

Do you have a simple example patch in Max… ? Must i try a “automation ID” Learnfunktion or work it only by define the ID at first part of the list?

Thanks very much,
hgh

Re: Send OSC to VST~Plugin (N.I. Reaktor)

broc — Tue, 24 Jul 2012 09:18:09 +0000

There is no learn function needed.

For example, the GoBox ensemble has a ‘Transp’ slider with automation ID set to 48 by default.
So you can simply send the list <48 $1> to move the slider (with $1 as float between 0 and 1).

Re: Send OSC to VST~Plugin (N.I. Reaktor)

hgh — Tue, 24 Jul 2012 11:23:53 +0000

Perfect!!!

But how to define the IDs, is there a way to do that manually?

Best,
hgh

Re: Send OSC to VST~Plugin (N.I. Reaktor)

broc — Tue, 24 Jul 2012 17:53:59 +0000

The ID’s can be defined/changed manually but rather tricky.
For details see manual, section ‘Automation ID Management’.

Re: Send OSC to VST~Plugin (N.I. Reaktor)

lowenstern — Tue, 24 Jul 2012 21:28:09 +0000

This may not be applicable in your case, but I figured some on the board might find it useful:

Whenever I have a NI (or other) plugin that does not directly expose its parameters to Max, I often wrap it in NI’s Kore2 vst or NI’s Maschine vst. Those often have an ability to control parameters that are otherwise either inscrutable or just not available. Then I just control Kore/Maschine with Max and everything’s peachy. I’ve found success dealing with Mobius this way, for example. (Mobius is controllable with Max, but older versions would not sync to the Max transport, but they’d sync when wrapped with Kore)

YMMV of course.