lahatte
Ok, so it seems like you have to turn off your MIDI devices in Sonar that you want to make use of with Ctrlr, which seems really odd, but I guess that's what you get for nothin. Then you select them in the Ctrlr MIDI settings.
Ctrlr can send MIDI to the host or directly to the device. In the later case, it works directly, bypassing the host. Most MIDI devices are not "sharable", 2 programs can not work with the same device in parallel (while CtrlLr running inside Sonar is technically the same program, it tries to initiate a separate connection).
You can also output MIDI to the host and then ask the host to send that to the device. Sonar is able to do this, while routing is not straightforward. You will need to enable CtrlLr VST MIDI output, make separate MIDI track, set its input to CtrlLr output and its output to the device, enable Echo on that track and watch all other MIDI tracks in the project do not have "Omni.." as the input. Taking the problem Sonar likes to "mess" MIDI devices in case you disconnect something from you computer, evaporating any MIDI routing in the project, that is practically not usable approach...
So in practice, if you want to send MIDI from Ctrlr and Sonar in parallel, you have 2 options:
* get some software MIDI "router", so you have 2 virtual MIDI inputs routed to the single device input
* try to make the routing inside CtrLr, so output whatever you need to send from Sonar to CtrLr VST.
scook
lahatte
Have you made this work in Sonar?
No, but if it works at all in SONAR, it will work like any other VSTi that generates MIDI. In my experience it is something like a sequencer - a plug-in that loads like a synth but generates only MIDI, no audio.
Ctrlr is not normal VST MIDI FX. It is similar to Cakewalk Studioware, with options to work with MIDI devices directly (so not using VST MIDI in/out).