Saving Zebra patches in Cubase 4

Official support for: u-he.com
RELATED
PRODUCTS

Post

Well, sad news, but thanks for your honest reply.

Unfortunately there's no such tool to convert from .fxp to .vstpreset. I'd code one, but all I remember is BASIC :hihi: Still I don't understand why Cubase' build-in tool to convert preset lists to the new format does work with many many VSTs and does not with others :?

Post

It does say fxp/fxb import in Cubase though so if we had the fxp file theoretically we could import the zebra 2.02.1 presets?

Of course that's good for Cubase but I can't even get KORE2 to recognize Zebra2 - will recognize Zrev though?

C

Post

C-note wrote:Of course that's good for Cubase but I can't even get KORE2 to recognize Zebra2 - will recognize Zrev though?

C
I've run into that myself- here's the fix.

Go to where your database cache for Kore is (you and I went through that before) and delete the Zebra.ksd in there. Now, start up Kore in standalone; Zebra will appear now. Done.

ew
Last edited by ew on Thu Jul 03, 2008 7:18 pm, edited 1 time in total.
A spectral heretic...

Post

I've run into that myself- here's the fix.

Go to where your plugin cache is (you and I went through that before) and delete the Zebra.ksd in there. Now, start up Kore in standalone. Done.

ew
Oh yeah, Thanks ew!

Post

Oh... if .fxp would be sufficient then I can help... is that so? Can .fxp be imported to C4? (That would make C4 a tool to convert .fxp to .vstpreset 8) )

Other than that... I would really love to help out here, but I'm miles deep in some stuff... it's really exciting stuff but also really draining a lot of energy... and today is pretty hot here and I'm totally stuffed...

Later,

;) Urs

Post

nope, .fxp won't help. You can manually save each preset as .vstpreset, that's not the issue, but you can't convert a whole bank in one go. That's the pitty. For whatever reason Cubase won't show that menu-entry when Zebra is loaded.

However I manually converted all of the presets that came with Zebra 2.2 one by one (bear in mind one has to type in each preset's name, cause Cubase doesn't automatically pick it up when using this method). If you're interested you can download them here:

http://projects.lanteraudio.nl/downloads/cubase/

But no way I'm gonna do that again for all the other 6 million presets :x

Cheers,
bM3w

Post

Sorry for bumping this old thread but are there any news on this issue? Cubase 5 still refuses to do batch conversion of fxps to vstpresets. :(

And Cubase 5 still refuses to export fxps or fxbs but this is another topic. :x

Post

I know this is an older topic,but was there ever any updates to this? Would love a better way of importing these as .vstpresets
INTERFACE: RME ADI-2/4 Pro/Antelope Orion Studio Synergy Core/BAE 1073 MPF Dual/Heritage Audio Successor+SYMPH EQ
SYNTHS: Arturia Polybrute 12/Roland Jupiter X + Juno X/Yamaha Montage M/Yamaha KX88/Softsynths + Samplers
PEDALS: Chase Bliss Mood MK II

Post

This is the same for every single preset and plugin out there. Bit sure why it's needed as universal presets for the plugin is all that's required if you migrate hosts.
Personally only use vst presets for defined use in projects however cubase saves all the presets for the plugins in the project anyway.

Post

I use my vstpresets in cubase as well as studio one. so i was hoping by now there was a legit solution. as S1 has proven to be another major daw by now right
INTERFACE: RME ADI-2/4 Pro/Antelope Orion Studio Synergy Core/BAE 1073 MPF Dual/Heritage Audio Successor+SYMPH EQ
SYNTHS: Arturia Polybrute 12/Roland Jupiter X + Juno X/Yamaha Montage M/Yamaha KX88/Softsynths + Samplers
PEDALS: Chase Bliss Mood MK II

Post

At least for Studio One I can assure you that there'll soon be a solution that we are working on with them.

As for Cubase, our export of native presets has always only saved .aupreset and .fxp. This has been the first time since we introduced our new preset browser a few years ago that I see anyone asking for such. We have it on our todo list to also export .vstpreset, but demand seemed so low that it never became prioritised enough to make it into a release.

Post Reply

Return to “u-he”