Page 1 of 1
R3 Controling Sonar VST
Posted: Wed Sep 16, 2009 8:10 pm
by LSainsbury
Hi,
I've got my R3 hooked up to my PC via the USB. Now - I'm assuming that the MIDI info is tx / rx via the USB <> PC.
How can I configure the R3 to control the Sonar VSTi's? I've got the R3 configured to output to USB and Sonar to recieve via the R3 MIDI In (assuming this is the USB driver), but it dosn't seem to work - no MIDI info.
Any ideas?
Posted: Thu Sep 17, 2009 12:52 am
by xmlguy
Nope, that's the wrong midi port. You need to use "R3 KBD/KNOB" for the midi input, as shown on page 69 of the Owner's Manual. The "R3 MIDI IN" port is used for receiving midi from any other device plugged into the R3's MIDI IN port, not from the R3 itself.
Posted: Fri Sep 18, 2009 9:53 am
by LSainsbury
Thanks xmlguy - but I'm talking about outputting the R3's MIDI to the PC running Sonar to control the VSTi's - but I'm assuming it's the same knob control I need to change.
Goes to RTFM!!

Posted: Fri Sep 18, 2009 10:05 am
by xmlguy
Yes, I think know what you're referring to. When you press the white and black keys on the R3 or turn its assignable knobs, the midi data is sent over the USB-midi connection to the Software Driver MIDI port named "R3 KBD/KNOB" not the midi port named "R3 MIDI IN".
If you hook another keyboard's MIDI out connector to the R3's MIDI in connector, then the notes and knob MIDI output is sent over USB-midi to the Software MIDI port named "R3 MIDI IN".
In other words, you are configuring SONAR to listen to MIDI events that don't exist because you've apparently picked the wrong MIDI port of the R3 driver.
Posted: Fri Sep 18, 2009 6:57 pm
by LSainsbury
Yay!!! It works - thanks!
Anyway to get rid of the slight delay? There's a few ms between hitting the key on the R3 and the Sonar / VST producing any sound....
Posted: Fri Sep 18, 2009 8:06 pm
by xmlguy
Glad you got it working!
This kind of delay is called latency and probably isn't on the R3 end. Your computer is probably too slow and/or your Sonar/VST configuration more than your computer can handle quickly. You should go to forums that specialize in Sonar and your VSTs to research latency problems. You can try a very small Sonar session with only one midi track and one VST softsynth with the simplest patch and no other VST effects or anything else to slow down your system.
On a side note, for music production I recommend that you use a system that has been completely wiped out and reformatted with a clean operating system configuration, and then only install the minimum software and drivers that you need to do music. Never load or test any other software on this configuration, ie no Wordprocessing/Office, or general browsing or add-ins, games, or anything else.
By clean operating system I mean truly clean - not some Manufacturer's customized/basterdized version with all their crappy add-ons. If you have only one desktop computer, then you may be able to buy removable drive bays and multiple harddrives to have different configurations to keep them completely separate. 'Once you load crap onto a computer there is no reliable way of undoing the damage short of a complete reformat and clean OS reinstall, despite all the lying bastards who claim otherwise to sell you some "cleaner" that won't work. Rogue software/malware is designed specifically to avoid cleanup, and it changes too quickly for any cleaners to achieve anywhere near 100% detection and removal. The only reliable solution is to install a clean OS and to keep it clean. All it takes is one instance of spyware/malware/virus to kill your system's performance, even when your system should be fast enough to handle the load of your DAW and VSTs. Same goes for unneeded add-ons that consume memory and CPU.
When I get called to help fix system performance problems, often I see a desktop and taskbar filled with icons of every kind of crap known to man. My immediate diagnosis is that it's unfixable without a full reformat. Afterwards they're amazed at how much faster their system becomes, upon which I remind them that the improved speed is just temporary until they install just one program that kills it again - and I can't tell them what software might do that. Practice Safe Computing.
Posted: Fri Sep 18, 2009 8:15 pm
by 2disbetter
Just had this issue in FL. It is all software related. First off, does your soundcard have it's own ASIO drivers? If so make sure you have your VST using them. Second, how high do you have your sound buffer set within said VST? The lower the setting the less latency, but you also have an increased chance of garble or feedback. This factor is determined by your computer hardware (processing power, available memory, sound processor specs, etc.)
All of these things have many ways to go about changing them. Your best bet to tracking it down is your VST's help manual (you are not hte first to ask this), and second any official or fan based forum on the software.
Best of luck, hope you get it solved. Was sure annoying for me, when I had the problem.
2d