Reply To: Working standalone, but not in Cubase as plugin

Possemo wrote:

fyi I made some other experiments in Cubase:

Input from Host does work, no problems there. Output to Host: make a second track selecting the Ctrlr ouput as input . Unfortunately Cubase will only pass program and control changes to this new track – NO sysex! Therefore this is no option either. The only way in Cubase is to set the port on Midi output of the Ctrlr plugin. Cubase can access the synth through the Ctrlr plugin by selecting thru option “host to output”. This works nicely on my setup. Of course you will have to dedicate a port for the synth (no daisy chaining). But daisy chanining using Midi Thru is no option anyway when using bidirectional panels.

Edit: I forgot – you have to select “input from host to comparator”. “Input from host” does not work resp. is useless.

Much appreciated.

Yep, that all works, as I’d already discovered (except I don’t need to use ‘host to comparator’ – ‘host to output’ works fine for me). Just like you, I can see that the output (presumably sysex) from Ctrlr is somehow intercepted by Cubase and blocked when using ‘output to plugin host’. This is the sticking point.

I can get it working by setting the port in Ctrlr directly – no problem with that, but it will not work if I have the port used anywhere else in Cubase, or if I simply name the port in MIDI Device Manager. This just isn’t tenable for me. Ctrlr is effectively wanting exclusive use of the port and that isn’t realistic. If I temporarily remove the port references in Cubase to get Ctrlr working, then Cubase can’t make use of the port that Ctrlr has snatched from it. Sigh…

It looks like I will have to abandon this and see if I can come up with some other method for controlling my V4 MKS-70. Maybe there’s an iPad app I can use.

• This reply was modified 6 years ago by The Elf.
• This reply was modified 6 years ago by The Elf.