[sdiy] Generic preset storage / converting presets between synths

[Scott Gravenhorst]

As was previously mentioned, "to the extent that they are compatible",
these conversions ought to be possible.  

I do see the value in what you are trying to get to.  It will require that
you learn how sysexe messages are constructed for each synth.  Roland and
Korg supply a nice map of this structure (at least for the ones I own). 
The Wavestation has this as C data structures.  It should be fairly easy
to provide an editor front end for it too with your idea of a common layer
to and from which all patches are translated.  The editor would manipulate
the common layer.  Nice idea.

I also wrote an editor for a Quadraverb... That was an experience in
bizarro world reverse engineering.  It works, but Alesis did some wierd
things and they don't document the sysexe data structure in the manual.

BTW, if you don't already have a way to back up what is currently in your
victim synths, that would be a good thing to start with.




Kenneth Martinez <kmartinez at bency.com> wrote:
> > ...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
>
>

=========================================================  
- Hydrogen is pointless without solar.
- That which gets rewarded, gets done.
- What good are laws that only lawyers understand?
- The media's credibility should always be questioned.
- Governments do nothing well, save collect taxes.

-- Scott Gravenhorst | LegoManiac / Lego Trains / RIS 1.5
-- Linux Rex         | RedWebMail by RedStarWare
-- FatMan: home1.gte.net/res0658s/FatMan/
-- NonFatMan: home1.gte.net/res0658s/electronics/