Saving Zebra patches in Cubase 4
-
- KVRian
- 710 posts since 17 Jan, 2005 from Amsterdam
OK, I already asked this in the beta thread, but it seems that my question was overlooked. So this is another attempt to get some clarification on the issue: I'd like to know if it's possible (or understand when it's not) to save ALL Zebra presets in ONE GO to the new .vstpreset format of Cubase 4. Let me explain: When you load a VSTi in Cubase 4 you can usually select presets via Cubase' own internal menu/preset switch, which sits on top of the VSTi window. One option in the menu is to "convert program-list to VST presets". What it actually does is saving all presets to the new Cubase .vstpreset format and makes them available in MediaBay. The problem with Zebra is (not only Zebra, but a few other VSTs as well) that this option doesn't show up. The only workaround would be to save every single presets individually, which is a nightmare considering manually naming and saving thousands of sounds. I'm not sure what the problem is and why this option is not available when using Zebra. I tried to explain the same in the Tone2 forum (happens with their software as well), but I didn't get an answer on the actual issue. Maybe you, Urs, know why Cubase 4 is so selective and makes this option available to some, but not all VSTs. Any idea ?
Thanks,
bM3w
Thanks,
bM3w
- u-he
- 30206 posts since 8 Aug, 2002 from Berlin
Sorry, I meant to answer but got caught up in other things...
I don't think there's a proper documentation of the vstpreset format for VST2 plugins.
I suppose that .vstpreset is the preset format for VST3 which I will possibly support if more hosts than Cubase get into this. The problem is, afaiaa no other host developer will take on VST3 within the next year(s).
#---
I guess that Cubase expects VST2 plugins to show their presets in .fxp format. I use my own format for various reasons, but there are loads of patches already in .fxp format, i.e. the old factory presets from V2.0 - V2.1:
http://www.zebrasynth.com/index.php?item=downloads (bottom)
The current factory presets are not yet available in .fxp, but if above presets work with C4's "convert program-list to VST presets" then I'll happily have them converted for you
On the other hand, they might mean their old .fxb / bank system, I don't know.
Please let me know, if .fxp is the answer
#---
What is the advantage of Cubase's patch management over Zebra's? - The more feedback I get, the better it's gonna be
Urs
I don't think there's a proper documentation of the vstpreset format for VST2 plugins.
I suppose that .vstpreset is the preset format for VST3 which I will possibly support if more hosts than Cubase get into this. The problem is, afaiaa no other host developer will take on VST3 within the next year(s).
#---
I guess that Cubase expects VST2 plugins to show their presets in .fxp format. I use my own format for various reasons, but there are loads of patches already in .fxp format, i.e. the old factory presets from V2.0 - V2.1:
http://www.zebrasynth.com/index.php?item=downloads (bottom)
The current factory presets are not yet available in .fxp, but if above presets work with C4's "convert program-list to VST presets" then I'll happily have them converted for you
On the other hand, they might mean their old .fxb / bank system, I don't know.
Please let me know, if .fxp is the answer
#---
What is the advantage of Cubase's patch management over Zebra's? - The more feedback I get, the better it's gonna be
-
- KVRAF
- 2327 posts since 13 Apr, 2004 from Vancouver, Canada
Really, not a whole lot Urs. My personal opinion is that all VSTIs should have an internal preset manager along the lines of Z2 and/or LinPlug synths.Urs wrote:What is the advantage of Cubase's patch management over Zebra's? - The more feedback I get, the better it's gonna be![]()
Urs
The world would be a much happier place.
-
- KVRian
- Topic Starter
- 710 posts since 17 Jan, 2005 from Amsterdam
Thanks for your quick reply Urs and no need to apologize
Well, .fxp is unfortunately not the answer. I also think it's not fully VST3 related as other (even very old) 3rd party plugins do make this option available. I'd like to show you some screenshots, but I actually don't know how to include screenshots here. Maybe I can send them to you by email...Anyway, back to the topic: It might be the bank / .fxb thing, but only you know if that's somehting that is not fully implemented in Zebra2.
In opposit to advaya's opinion I think there is some advantage: the good thing about this new preset system in Cubase is the ability to "preview" sounds from within the MediaBay, another new feature of Cubase 4. It's basically a database with file browser and a nice tag system. Searching for sounds through MediaBay is simply awesome and very helpful when you have to manage thousands of different sounds.
Now the weird thing is, that I can save every single Zebra2 patch to the new format, just not the complete patch list in one go. I get the option to save the actual loaded patch manually. But doing that patch by patch means 1. select patch, 2. click menu and select save patch 3. give it a name 4. hit save. I did that for the included presets and I almost went crazy. It took me hours and hours...and then I found out about the other hundreds of factory presets from the previous Zebra release
No way I go through this torture again.
Altogether the new format and it's availability in MediaBay is pretty handy. Nothing wrong with your preset handling - especially since you added the programm change feature - but it's an added value to all Cubase 4 users.
Let me know if I can be of any help to get you a better understanding of this feature.
Thanks,
bM3w
Well, .fxp is unfortunately not the answer. I also think it's not fully VST3 related as other (even very old) 3rd party plugins do make this option available. I'd like to show you some screenshots, but I actually don't know how to include screenshots here. Maybe I can send them to you by email...Anyway, back to the topic: It might be the bank / .fxb thing, but only you know if that's somehting that is not fully implemented in Zebra2.
In opposit to advaya's opinion I think there is some advantage: the good thing about this new preset system in Cubase is the ability to "preview" sounds from within the MediaBay, another new feature of Cubase 4. It's basically a database with file browser and a nice tag system. Searching for sounds through MediaBay is simply awesome and very helpful when you have to manage thousands of different sounds.
Now the weird thing is, that I can save every single Zebra2 patch to the new format, just not the complete patch list in one go. I get the option to save the actual loaded patch manually. But doing that patch by patch means 1. select patch, 2. click menu and select save patch 3. give it a name 4. hit save. I did that for the included presets and I almost went crazy. It took me hours and hours...and then I found out about the other hundreds of factory presets from the previous Zebra release
Altogether the new format and it's availability in MediaBay is pretty handy. Nothing wrong with your preset handling - especially since you added the programm change feature - but it's an added value to all Cubase 4 users.
Let me know if I can be of any help to get you a better understanding of this feature.
Thanks,
bM3w
- u-he
- 30206 posts since 8 Aug, 2002 from Berlin
Well, I'll check it out. Maybe there is some sort of documentation for the vstpreset patch format after all, but I don't recall having seen any in the VST3 SDK. I can probably ask the guys at Musikmesse.
For normal conversions (h2p <-> fxp) there's always that secret (not so anymore) shift-alt-click (or some combination of modifiers, command-shift-click on Macs, gotta try) that juggles you through instantly with just mouse clicks...
Cheers,
Urs
For normal conversions (h2p <-> fxp) there's always that secret (not so anymore) shift-alt-click (or some combination of modifiers, command-shift-click on Macs, gotta try) that juggles you through instantly with just mouse clicks...
Cheers,
-
- KVRian
- Topic Starter
- 710 posts since 17 Jan, 2005 from Amsterdam
Thanks Urs. I'd really appreciate if you can follow up on this. I understand this is certainly not your number one priority, but this issue is really driving me crazy and I bet many others as well. Again, if I can be of any help on the Cubase side to sort out the issue, just let me know.
Cheers,
bM3w
Cheers,
bM3w
- u-he
- 30206 posts since 8 Aug, 2002 from Berlin
Yep, been to the VST3 conference and they told us there'll be some documentation (and a new VST3 SDK) somewhen by next week... fingers crossed!
I need some days off now though... was quite stressy as you can imagine...
I need some days off now though... was quite stressy as you can imagine...
- u-he
- 30206 posts since 8 Aug, 2002 from Berlin
I've pretty much written off VST3 as no other host developer nor any plugin developer I know is willing to support it within the next couple of years. Even the ones who demonstrated VST3 plugins (did they?) on Winter NAMM have not yet published any. Hence I guess it's slightly dead.bM3w wrote:Any news on this topic?
Thanks,
bM3w
I might try the VST file stuff in the SDK, but I'd highly appreciate if people could request Steinberg to support the de-facto .fxp standard instead of just the de-facto proprietary .vstpreset.
Or maybe is there a tool to convert .fxp into .vstpreset?
- KVRAF
- 9217 posts since 23 Jul, 2002 from Pequot Lakes, MN
?Urs wrote:I've pretty much written off VST3 as no other host developer nor any plugin developer I know is willing to support it within the next couple of years. Even the ones who demonstrated VST3 plugins (did they?) on Winter NAMM have not yet published any. Hence I guess it's slightly dead.
Sorry, Urs- that's not quite true. Harry from Virsyn's published five of them- all his effects plugins are VST3...
ew
A spectral heretic...
- u-he
- 30206 posts since 8 Aug, 2002 from Berlin
Yes, I know. It doesn't help much though.ew wrote:Harry from Virsyn's published five of them- all his effects plugins are VST3...
I'd love to support VST3 if it made VST2 go away. But as long as VST2 is not going away, VST3 is just too much extra effort for one single host application that happily also works with the old format...
- KVRAF
- 9217 posts since 23 Jul, 2002 from Pequot Lakes, MN
Can I get an amen?Urs wrote:I'd love to support VST3 if it made VST2 go away. But as long as VST2 is not going away, VST3 is just too much extra effort for one single host application that happily also works with the old format...
ew
A spectral heretic...
- u-he
- 30206 posts since 8 Aug, 2002 from Berlin
I wished they had released the SDK in 2003. That would've been a totally different thing. At least for me...
