Forum Replies Created
-
Posts
-
You must be on a Mac. On Windows most MIDI drivers do not allow more than one connection to a MIDI port.
Your setup didn’t work for me. But then I don’t know how you had the MIDI track ports configured.
Thanks for that. But how did you set the MIDI in and out on the MIDI track in Reaper?
I have something that somewhat works, but uses the stand-alone Ctrlr application rather than the VSTi, along with my DAW. I am using Sonar as my DAW, but others will be similar I assume. This doesn’t use the Ctrlr VSTi (can’t get that to work in the DAW) but instead uses the stand-alone Ctrlr application. Here’s what I have right now …
1) Install LoopMIDI, and run the tool.
2) In the LoopMIDI Config, click the + to add a port. You can name it first if you like, or use the default name.Sonar Part:
1) In Sonar, go to Preferences, MIDI devices, and select the new port as an output (not input).
2) Add an audio track to get the signal from your external MIDI device into Sonar, as usual per your audio interface.
3) Add a MIDI track for the external MIDI device.
4) Set the track MIDI Input to your keyboard, or whatever is used to send notes info, etc.
5) Set the track MIDI Output to the LoopMIDI port.Ctrlr Part:
1) Open the stand-alone Ctrlr application.
2) Under the MIDI menu, set the Input Device and Controller Device to the LoopMIDI port.
3) Set the Output Device to your hardware port connected to your external MIDI device (I don’t know how this is working to allow both Sonar and Ctrlr to access this port, but here it is).
4) Set the Thru to “Input Device -> Output Device”.This setup gets me MIDI and audio for the external MIDI device via Sonar, and also the ability to control the device with the stand-alone Ctrlr application.
There may be ways to improve on this, but this is what I have found for now.
I have something that somewhat works. I am using Sonar as my DAW, but other will be similar I assume. This doesn’t use the Ctrlr VSTi (can’tget that to work in the DAW) but instead uses the stand-alone Ctrlr application. Here’s what I have right now …
1) Install LoopMIDI, and run the tool.
2) In the LoopMIDI Config, click the + to add a port. You can name it first if you like, or use the default name.Sonar Part:
1) In Sonar, go to Preferences, MIDI devices, and select the new port as an output (not input).
2) Add an audio track to get the signal from your external MIDI device into Sonar, as usual per your audio interface.
3) Add a MIDI track for the external MIDI device.
4) Set the track MIDI Input to your keyboard, or whatever is used to send notes info, etc.
5) Set the track MIDI Output to the LoopMIDI port.Ctrlr Part:
1) Open the stand-alone Ctrlr application.
2) Under the MIDI menu, set the Input Device and Controller Device to the LoopMIDI port.
3) Set the Output Device to your hardware port connected to your external MIDI device (I don’t know how this is working to allow both Sonar and Ctrlr to access this port, but here it is).
4) Set the Thru to “Input Device -> Output Device”.This setup gets me MIDI and audio for the external MIDI device via Sonar, and also the ability to control the device with the stand-alone Ctrlr application.
There may be ways to improve on this, but this is what I have found for now.
This is great, but can someone make a step by step on the MIDI setup, especially for use as a VSTi?
Thanks.
It’s really too bad there seems to be no documentation on setting up Ctrlr as a VSTi and being able to use it alongside a keyboard.
But is it not possible to use Ctrlr via Sonar’s MIDI connections? As in, pass MIDI data to Sonar and let Sonar route it to the devices…
Ok, I did an uninstall and re-install of an earlier version, then the latest (5.4.54). Not sure if the earlier version is relevant to it working.
But now I need to know how to use the VSTi in a host. I can’t get the Ctrlr VSTi to send any data to my synth. Sonar is using the MIDI ports, so I cannot select those. I thought the VSTi would just use what Sonar makes available?? Surely someone is making this work.
Please advise. Thanks!
Thanks. But the problem is there is NO menu. Just an empty plugin window. See the image in my first post.
I am indeed using the 64 bit version. I can get nothing in the Ctrlr plugin window in Sonar.
Hep!! Hep!! I tought I taw a putty tat. Hep!!
Yes. You are correct. I just tried the wrapper since it wasn’t working otherwise.
I’ll have to make sure it is indeed using the 64 bit version.
I saw on the Sonar forum that someone else has had an issue with the Ctrlr menu bar not showing in the plugin window, but somewhere to the side. I’ll have to look for that too.
