[sdiy] Generic preset storage / converting presets between synths
Kenneth Martinez
kmartinez at bency.com
Mon May 26 20:13:47 CEST 2003
> ...What I can tell you is that there is often precious little
> similarity between synth models even under the same manufacturer...
> There may be some overlap where the sounds are rather simple.
> Pads, flutes, strings etc., which rely on simple waveforms and
> common modulations and a simple patch structure, can possibly be
> transmuted.
Yes, and I'm really thinking about sounds which can be created using
basic analog waveforms and structure.
>... IMHO, I think it would take more time to write the translator
> than to do the sound work and save the results...
Sounds like a challenge ;-)
I'd me more tempted to try this myself if I didn't have a 9-month-old.
Free time - what's that??
> This work multiplies in complexity for each new synth type
> you need translations for.
If you convert from any synth into meaningful real-life values
(half-steps for pitch, milliseconds for time, etc), you could then
convert from real-life values into any synth's corresponding parameter
value. Adding a new synth only means mapping its parameters to
real-life values... given the time to do that. (See comment above about
free time.)
> Deciding which synths should produce what sounds is part of the
> work of composition and takes thought and planning before you
> commit them to a piece. I use the near-copy approach only when
> I have run out of voices on the box which best makes that sound
> in the first place.
Point well taken... but if I later wish to switch boxes, I'm back to
manual labor. If I make sounds for a song on a bunch of analogs but
later decide I'd rather only take a couple synths somewhere to perform
it, again I have to either bite the bullet and do the conversions, or
drag along all the gear anyway.
Is it worth the effort to write the converters? Don't know, but I can
always dream
More information about the Synth-diy
mailing list