Hi
This is an XML device file, which you can import in Cubase SX. It contains devices with the patch lists for most of the CW synths (Minimax, Vectron, BlueSynth, SixString, etc. etc.) About the only one missing is the ProTone which I don't own.
Just import the file from the Midi Manager (Import Device, if memory serves).
I only was able to do some testing, so please be a tad careful - it might be prudent to back up your existing midi device setup first. I constructed this by entering all patch names for all devices, and afterwards cutting and pasting from the midi device XML file. I tested it by deleting the devices from the XML files and then importing it , and that worked fine.
The only "rough edges" concern patch banks that contain more than 128 sounds - not all patches will be selectable. Luckily most of the patch banks "play nice" and contain 128 patches or less.
Xeers, and have fun,
Philip
Cubase SX Patchnames for almost all 'official' CW Devices
Cubase SX Patchnames for almost all 'official' CW Devices
- Attachments
-
- Creamware_All_Devices.zip
- (135.72 KiB) Downloaded 204 times
- Ben Walker
- Posts: 824
- Joined: Mon Apr 23, 2001 4:00 pm
- Contact:
Yes it was
It was done piecemeal though, generally shortly after I bought the device in question, which happened over time. And the "smaller synths" which you get automatically with Scope don't have that many presets anyway.
Mind you, you can optimize the effort - first get Cubase to create a range of empty presets with the correct parameters (a neat feature, one of the few things they got really right in their Midi Device Manager), and then it's a question of finding a good rhythm and the minimum amount of keystrokes to walk through the list, inputting the names...
Still, I would have been much happier if I could just've downloaded them

It was done piecemeal though, generally shortly after I bought the device in question, which happened over time. And the "smaller synths" which you get automatically with Scope don't have that many presets anyway.
Mind you, you can optimize the effort - first get Cubase to create a range of empty presets with the correct parameters (a neat feature, one of the few things they got really right in their Midi Device Manager), and then it's a question of finding a good rhythm and the minimum amount of keystrokes to walk through the list, inputting the names...
Still, I would have been much happier if I could just've downloaded them

Thanks to you, it will be easier 4 me.
The stock VSti synths in 4 are so weak compared to Zarg , SpaceF, and other 3rd party developers. But w/ the E series CPU's immense horsepower, VST programmers can probably start using more resources for algorhythmic quality.
Thanks Again 4 Another Work Saving Idea,
The stock VSti synths in 4 are so weak compared to Zarg , SpaceF, and other 3rd party developers. But w/ the E series CPU's immense horsepower, VST programmers can probably start using more resources for algorhythmic quality.
Thanks Again 4 Another Work Saving Idea,
Thanks for your effort RX. I know it must have been alot of work. I put together a patch name script for the supernova II ( when I stil used it) which has 16 banks A-H & a-h! Although further down the line not all banks are full 128, it took bloody ages! Actually I'm not even sure I finished it completely
With regards to cubase 4 im suprised you've jumped on it so early Jimmy! From what I've read it seems there is alot to iron out and fix. The cheap upgrade offer was tempting for me until I read reviews and also realised that there was nothing in the update that I needed. VST's/VSTi's, don't use them. Control room, well I monitor in scope. So the only thing that was really enticing was the preset manager, but I can't see that working very well, or at least any better than how scope handles preset. Not without ALOT of effort anyway.

With regards to cubase 4 im suprised you've jumped on it so early Jimmy! From what I've read it seems there is alot to iron out and fix. The cheap upgrade offer was tempting for me until I read reviews and also realised that there was nothing in the update that I needed. VST's/VSTi's, don't use them. Control room, well I monitor in scope. So the only thing that was really enticing was the preset manager, but I can't see that working very well, or at least any better than how scope handles preset. Not without ALOT of effort anyway.