Dave Smith Instruments SYNTHESIZERS group photo

Yahoo Groups archive

Dave Smith Instruments SYNTHESIZERS

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

Message

Patch File Nomenclature Standards

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

Yes, that's right.  A few comments....

- If we're going to put a "type/category" name in there, it's going 
to have to include an item like "various", "mixed", or "misc", for 
files that contain entire BANKS of patches that have multiple patch 
types.  

- The "location" portion of the name for files containing a single 
patch could be abbreviated by using "A", "B", and "C" to designate 
the bank (I think I remember Dave himself doing this in some emails 
we've traded).  Your example could then be "bass.moog3.B45.mid" 
rather than "bass.moog3.b2p45.mid".

- We also need a way to designate that a file contains an entire 
Bank, or Banks, of patches as opposed to a single patch, such 
as "misc.Ravi07.bank1.mid", or better yet, maybe 
just "misc.Ravi07.A.mid" to be somewhat consistent with the single 
patch nomenclature.  A file with all three banks could read 
like "misc.Ravi07.ABC.mid" or "misc.Ravi07.ALL.mid" (I think I like 
the second one better).


What's everyone think?


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 Sharma" <noision1@h...> 
wrote:
 
So then in regard to naming patchfiles, whether midi or sysex, a 
naming structure would be good. I.e., "type.name.location" 
ie. "bass.moog3.b2p45.mid" or "lead.killerz.b1p3.syx"

or something like that . . .

suggestions . . .



>From: "Ski " 
>Reply-To: DSI_Evolver@yahoogroups.com 
>To: DSI_Evolver@yahoogroups.com 
>Subject: [Evolver] Re: Patch Contest 
>Date: Tue, 07 Jan 2003 07:51:55 -0000 
> 
>If by "this problem", you mean the fact that you don't know where 
the 
>patches are going to load, then yes, SYSEX files have the same 
>problem. The patch bank(s) and the patch number(s) are both encoded 
>into the saved patch files... so they're always going to load back 
>into the same slot. So it's not really a MIDI or SYSEX "problem"; 
>it's just the patch format, coupled with the Evolver's inability to 
>let you specify a "destination location" for single patches that you 
>load. Shouldn't be too hard to write a little librarian, though, 
>that would let you rearrange the patches within a MIDI or SYSEX 
file. 
> 
> 
>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 Sharma" 
>wrote: 
> > No, I meant only for midifiles, obviously sysex route doesn't 
have 
>this problem, or does it? I got midiox to work, but I didn't know 
how 
>I did it . . . :) 
>

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.