Radias running as a vst in Cubase 5

49erkid · Post by **49erkid** » Wed Oct 26, 2011 1:02 am

Hello all is it possible to run the Radias as a vst instrument in Cubase? Thanks for the great website.

49erkid

CharlesFerraro · Post by **CharlesFerraro** » Wed Oct 26, 2011 5:54 am

You cannot run the editor as a VST instrument.

You can sequence and automate the RADIAS with a MIDI track.

You can also build a MIDI device. I'm in the process of doing that. I'll post it in this thread before the end of the year. Its on my to-do list.

49erkid · Post by **49erkid** » Wed Oct 26, 2011 2:12 pm

Hey Charles thanks for the reply. Ok yeah I am looking into adding the Radias as a midi device, are you referring to making a cubase script with all the parameters to call up Radias patches within cubase? If so, there is a midi device called ms2000 which actually works (but the patch names are incorrect) maybe you can edit the patch names and save the file as Radias? Just a thought.

CharlesFerraro · Post by **CharlesFerraro** » Thu Oct 27, 2011 5:26 am

Ya I saw the MS2000 in the device list which prompted me to look up the CC's and they are different unfortunately. It'll MIDI dump and all but I'm just going to do it from scratch. Using a pic of the editor as the device background so it looks pretty sweet. Going to be busy pretty much all Nov, I'll have to do it some time in December.

49erkid · Post by **49erkid** » Fri Oct 28, 2011 5:28 pm

Hey that's great that you're gonna take the time to make the correct file for the Radias, let me know when you finish the project, be interested to know how it turns out for you. Cheers.

49erkid

CharlesFerraro · Post by **CharlesFerraro** » Tue Dec 20, 2011 2:43 pm

Been working on it the past two nights and its turning out really well. Its like running the timbre window of the editor/librarian inside of Cubase. The Radias can send CC information to- and recieve CC info from it and they sync perfectly. Automation is visual for the device too which is very convenient. For instance if you sync the line tool to the grid you can draw in easy cutoff sweeps/dub wobbles and you'll see the cutoff knob move in the device window.

I need to work out a few bugs and I'm going to cover the V.Patch section with some mod switches and FX knobs since I'm not sure how to program anything besides CC's into the device. Hopefully it'll be done by Xmas, scripting and all.

Maybe I'll make an improved version next year with all the editor/librarian functions but let me get this version out first. Heres a screen cap:

X-Trade · Post by **X-Trade** » Tue Dec 20, 2011 6:20 pm

Wow! I'd love to try that out.

How does that work within Cubase though? Which version are you using?

I'm on Studio 4, and always thought MIDI Devices were just patch lists.

CharlesFerraro · Post by **CharlesFerraro** » Wed Dec 21, 2011 1:47 am

You'll be able to try it in a few days. To do so you'll need to download a device xml file that i'll post on some file-sharing site. Then you'll open a midi track and send the 'midi out' to the device (instead of to your outboard synth). The device then sends the midi out data to your synth.

Since the midi track is receiving midi data from your outboard synth, it then sends that data to the device, thus allowing communication between the device and your synth. If that doesn't seem to make much sense don't worry about it, point is it works.

I'm using Cubase 6 and this is my first time creating a midi device. I upgraded from 4 but never got into building devices when I had that version. Apparently the device manager/creation editor software hasn't been upgraded for a while so my bet is you can build the same thing in 4 np.

MIDI devices are very complex. I'm only using CC program numbers and standard patch recall programming via sysex. But you can go balls out crazy and use nrpn's to make the radias do whatever you want thanks to the extensive midi implementation pdf which you can download here http://korg.com/uploads/Support/RADIAS_ ... 050000.pdf

I'll use this version as a template for a much more complex program involving the Vocoder, and the rest of the parameters not accessible through midi cc like eg3 and a poly/mono switch etc. Maybe a way to access effects templates and stuff too, who knows.

CharlesFerraro · Post by **CharlesFerraro** » Wed Dec 21, 2011 7:13 am

beta version: http://www.file-upload.net/download-396 ... e.xml.html
upload an initialized patch into the radias since I haven't programmed any sysex presets yet. Also, turn local control off on the radias or you'll get instantaneous echo back when you hit a midi note which will cause awkward phasing.

demo vid: http://www.youtube.com/watch?v=gnCD9BU6 ... e=youtu.be

If anyone runs into a bug let me know.

CharlesFerraro · Post by **CharlesFerraro** » Fri Dec 23, 2011 3:27 am

I think... I'm going to give up on this project. MIDI Device programming severely lacks in the preset department. The best I could do is give you an initialized preset and the ability to store your own presets. Otherwise I would have to literally reprogram every damn preset by hand much like copy R3 parameters into the RADIAS Editor or something.

I could write a preset list that'll send a bank and program change message to the RADIAS with a correct label, but the device wont mimic the preset that is called up. You would still need to reprogram all the parameters and then save the preset as a "snapshot".

I found out that automating from the device itself works, however, that automation data does not show up in a lane for precision editing. Thus, automating from the RADIAS unit is more practical for editing purposes.

It was my idea that this endeavor would make the CC list names appear as their assigned values for the MIDI Device. That turns out to not be true so I'm stuck having to memorize the CC numbers and their corresponding RADIAS parameters anyway.

In conclusion, any real practical usage in the preset department would take much too much work with having to painstakingly copy parameters. Named preset aren't a big deal if I just make a note of the bank and program change numbers in the inspector. Automation via the panel is essentially just a nice visual without precision editing via a lane. Mac users can simply use the Korg RADIAS Editor/Librarian software in tandem with their DAW which will not communicate with Cubase, but is much more capable than any MIDI Device could be.

If only Korg had made their RADIAS software plug-in-capable like the M3, that would have been fantastic.

49erkid · Post by **49erkid** » Mon Dec 26, 2011 6:54 pm

Hey Charles thanks for giving this project a try, looks like you really did make some headway, perhaps someone else will be willing to take up the torch and continue the effort. Alas, I will download the XML file and try it my cubase 5 to see how it works. Thanks again and long live the Radias!

49erkid

CharlesFerraro · Post by **CharlesFerraro** » Mon Dec 26, 2011 7:13 pm

CharlesFerraro wrote:I found out that automating from the device itself works, however, that automation data does not show up in a lane for precision editing. Thus, automating from the RADIAS unit is more practical for editing purposes.

It was my idea that this endeavor would make the CC list names appear as their assigned values for the MIDI Device. That turns out to not be true so I'm stuck having to memorize the CC numbers and their corresponding RADIAS parameters anyway.

I was wrong on both those points. Turns out a separate track appears when you click write, like when automating the master bus. This new automation folder track contains all the programmed parameters of the device; available for point and click editing.

I'm going to delve deeper into the preset situation and finish this damn thing. Its important to note that snapshots are not going to work in the beta and know that I have already reprogrammed the full version to utilize patch banks. Just going to cram in some non-registered parameter numbers, get the effects section in line and finally work out subsequent bugs. I can't promise a delivery date but expect it before NAMM.

49erkid · Post by **49erkid** » Tue Dec 27, 2011 5:54 am

Charles,

Cool that you decided to forge ahead, good luck and keep up the good work. I can't wait to story the finished product, keep us posted.

Cheers,

49erkid

CharlesFerraro · Post by **CharlesFerraro** » Fri Dec 30, 2011 8:33 pm

Little update on this. I went against utilizing patch banks because they don't dump any CC information into the RADIAS. I decided to utilize snapshots in the inspector because you can automate a timbre to suddenly switch to a different snapshot, thereby editing all parameters in that individual timbre. A patch select command would change to a different preset and thus change all timbres, unless of course you disable program change on that timbre for the selected preset. I think snapshots just simplify things.

I'm also not going to program NRPN's because non static variables are over my head.

I also plan on making a MIDI Device Panel for the RADIAS vocoder and the TA-1VP/AVP-1 units.

CharlesFerraro · Post by **CharlesFerraro** » Sun Jan 01, 2012 3:16 am

Final version. I'm done working on this thing. I'll make one for the vocoder and ta-1vp when i need it.
http://www.file-upload.net/download-399 ... -.xml.html

snapshots don't work. software is too buggy to fix it. if anyone wants some tips or tricks on how to get the most out of it just hit me up.

Korg Forums

Radias running as a vst in Cubase 5

Radias running as a vst in Cubase 5

Radias and Cubase

Update

Re: Update