Dave Smith Instruments SYNTHESIZERS

Don, you're right, there's nothing on the Evolver itself to indicate 
that any sequence data is stored within a given program.  Good 
patch/sequence organization is key.  Without that, I usually just hit 
the sequence "Start" button to see if there's a sequence inside a 
given program.

For single program SysEx dumps, we've been using "seq." as a prefix 
for programs that contain sequence data.  For 
example:  "seq.Ski.KitchenSink.A128.syx"

Even knowing that a program does or doesn't have a sequence won't 
tell the whole story, though.  Some programs intended as "normal" 
leads, basses, etc. can contain "leftover" sequence data from a 
program from which they were cloned.  Some programs with sequence 
data are keyboard gated, and meant to be played as leads (for 
instance, with the sequencer changing filter values).  Some sequences 
can be transposed with a MIDI keyboard, while some can not.  Some 
patches without sequences are "drones" with the filter and amp open, 
and do not need to be played with by a MIDI keyboard.

The organization that Dave used in the Evolver presets really isn't 
too bad.  It does a decent job of separating programs into the basic 
groups.  I find it's a good idea to use something similar in 
organizing my own collections of patches/sequences.

BTW, thanks again for sending the 13 programs for the User Forum 
Soundset!


Ski
www.ex5tech.com
EX5Tech Evolver forum:
http://www.ex5tech.com/ex5ubb_cgi/ultimatebb.cgi?ubb=forum&f=23


--- In DSI_Evolver@yahoogroups.com, "Don Gothard" <gothard@s...> 
wrote:

> 
> Which reminds me, there needs to be a way in the evolver to 
determine
> whether a patch was saved with a sequence or not, as some of the 
patches I
> have are sequence based and a couple are not but you couldn't tell 
by just
> looking at the Evolver.
> 
> 
> Don