2013/02/26 22:19:12
Rain
Thanks guys. I've started checking out for solutions on my side. One of the things which makes it harder to handle is that I don't have access to the individual presets, only banks of them. 

So I can call up a global preset bank from my host browser, but all the navigating from one patch to another happens via the synth's GUI.

Obviously, I could just skip problematic patches and not save them as presets, but, if there's any (relatively simple) way I can fix something instead of avoiding it, that would be my first option.

Did I mention I hate it when synth manufacturers and preset makers ignore all conventions and try to be original instead of just using simple/descriptive names? 

Sayeth the guy who's had a lot of fun re-saving the Zeta factory patches (or is it Z3t4 + ?)
2013/02/26 23:14:14
craigb
So you can't even rename the patches using the synth's own GUI?  What about saving it as a new patch to the "user" area (if it has one)?
2013/02/26 23:55:10
Rain
craigb


So you can't even rename the patches using the synth's own GUI?  What about saving it as a new patch to the "user" area (if it has one)?

Any "defective patch" cannot be re-saved, even in the generic plug-in shell - which is what I was trying to do in the first place.


The banks are accessed via the shell, but the presets can only be accessed through the synth itself. 


Here's how it looks in Logic - patch no 43 is one of the problematic one. As long as I have it selected in the synth, any saving - whether it's saving a preset or a song will result in a crash.


Same in Studio One, same in DSP Quattro (my audio editor). Only Cubase seems to be able to handle it.




2013/02/27 02:13:15
craigb
Wow, that sucks...  I guess there's always the LONG way:  Copy each parameter and create a new patch with all the same settings.

I'm a geek so I either found and downloaded, or created a blank mapping of most of my synths so I could write down patch settings.  Hey, that's an idea...  Search to see if someone already has these patches extracted.  There are some ways to dump and manually change things (even things loaded into memory).  Maybe someone has already done this and changed the names to something safer.  Not sure if you can change your font in Studio One or Quattro, but maybe that could work too?  Waldorf is a German company so maybe using Deutsch would work...  (Or not!  LOL.)
2013/02/27 02:16:00
craigb
A quick search found this:  An AIFF file of the factory sounds
Try cutting off the URL a bit too - lots of info there.
2013/02/27 02:17:23
craigb
That link came from this set of many links:  http://www.synthzone.com/waldorf.htm

2013/02/27 02:43:07
Rain
Wow man! Thanks a bunch - I'll give those links a try. :)

One thing I've just noticed - in whichever application I'm using, be it Logic or Cubase the synth's own display won't show the names properly. 




I thought the synth itself had all the necessary resources and fonts to display everything, but no. Apparently, it relies on the system, and there's nothing proprietary in its own display.


Which mean that Cubase must have some extra content because the missing character shows up in Cubase's GUI and its proprietary drop-down menu. So I guess Cubase doesn't use system fonts, or at least, not exclusively.






12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account