Dave Smith Instruments SYNTHESIZERS group photo

Yahoo Groups archive

Dave Smith Instruments SYNTHESIZERS

Index last updated: 2026-04-28 22:43 UTC

Message

Re: [Evolver] Many thanks to Ravi

2003-01-07 by Ski <ex5tech@excite.com>

Thanks for the info.  I wanted to make sure that Dave didn't have 
things set up any differently in the Evolver before I started playing 
a MIDI file into it.

Your other ideas are all good.  Dave pretty much uses #128 as 
a "utility/test" patch anyway.  I wouldn't even mind designating Bank 
3 as a "test Bank", rather than having to load one patch at a time!  
One question... did you mean to imply below that we settle on a 
policy in which we use only MIDI format for storing/sharing patches?  
I kind of prefer SYSEX myself.  I'm probably not average, but I don't 
always have a sequencer running on my computer, and if you don't 
already have it running, it's a lot more convenient to just launch a 
little utility like MIDIox to save/load Evolver patches.  If everyone 
else wants to go MIDI, though, I'll go with the flow.

A patch contest would be great, too.  An added incentive for people 
is that I'm sure Dave would consider including the best of the best 
in the next "official" version of the presets.  For a simple 
beginning, the contest could be broken into two categories:  
1) "regular" playable patches, and 2) sequences.  Of course, if we 
had a ton of entries, you could easily start breaking things down 
further.


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


--- In DSI_Evolver@yahoogroups.com, "Ravi Ivan Sharma" 
<noision1@h...> wrote:
> This brings another point.
> 
> Perhaps we should talk about the idea of building some patch 
libraries for the Evolver. First we might simply start with a naming 
standard so that everyone knows where the patch will load into if 
useing midi files. Either that, or (pending the hopeful temp 
patch/compare feature request) we could agree that all patches saved 
in midi format be first moved to say patch 128 then saved so that 
users loading patches can generally keep patch 128 as a scratch 
preset for loading and saving purposes . . .  etc.
> 
> Another way we could do this is to incorporate a patch contest. 
That one is easy. We can set a deadline, and people can submit 
patches. Then we can vote using the polls and have fun. All the while 
we build a library of patches, etc.
> 
> feedback . . .
> 
> Ravi
>   ----- Original Message ----- 
>   From: Ski <ex5tech@e...> 
>   To: DSI_Evolver@yahoogroups.com 
>   Sent: Monday, January 06, 2003 10:08 PM
>   Subject: [Evolver] Many thanks to Ravi
> 
> 
>   I know that most people here already know this, but Ravi really 
does 
>   a great job here.  I was reminded of that today when I went 
cruising 
>   through the "Files" section online.  Ravi has made sure to 
include 
>   anything and everything Evolver related in here.  Not to mention 
the 
>   fact that he answers nearly every single post to this group.  So 
>   anyway, I just wanted to pass along a public "Thanks"!
> 
>   While in the Files section, I came across Ravi's "b1p1v2.mid" 
patches 
>   file.  I'm embarrassed to ask (*really* embarrassed!), but how do 
you 
>   load patches into the Evolver from a MIDI file?  Can I assume 
that 
>   it's like many others, and as simple as "playing" the file with 
your 
>   digital sequencer into the Evolver MIDI IN?  Just wanted to be 
sure, 
>   because I've used nothing but SYSEX files with MIDIox for patch 
>   loading/saving on the Evolver.
> 
>   Thanks a lot.
> 
> 
>   Ski
>   www.ex5tech.com
> 
> 
>         Yahoo! Groups Sponsor 
>               ADVERTISEMENT
>              
>        
>        
> 
>   To unsubscribe from this group, send an email to:
>   DSI_Evolver-unsubscribe@yahoogroups.com
> 
> 
> 
>   Your use of Yahoo! Groups is subject to the Yahoo! Terms of 
Service.

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.