Conference napalm::commusic_v1

    I've thought of doing this myself, but have never had the time or the
    patience to do it. 

    The "system" I employ now is kind of a kludge.  I use a super-librarian
    that knows about the internal format of SYSEX dumps of over 100 synths
    (not a small task).  I use this to manage the actual patch dumps for
    each synth.  

    I've got a set of around 100 favorite patches for my TXes, and 60 for
    the ESQs.  I keep a written sheet with these patch names and some notes
    by each patch denoting modulation characteristics.  I also try to name
    patches meaningfully (like notes topics) to reduce the lookup time. 

    If I were going to "key" it (in traditional terms), I'd probably use
    model (no hyphens, of course 8-) and patch name as a segmented P key.
    I'd then have a separate field for each "popular" modulator.  I'd allow
    a segmented string (or facsimile) for a descriptive text string (like
    "gritty sax"), and finally would include the patch data on the end.
    Record structure similar to: 

	|<---- KEY ---->|
	model:10  name:10 PB MW CP PP BC OT text:30 patch_data:??

	PB: pitch bend  MW: Mod Wheel   CP: Chan Press	(all 1 byte
	PP: Poly Press  BC: breath ctl  OT: other   	 boolean fields)

    Of course, you will run into a problem in that some patch settings are
    stored in a performance memory, which is distinct from the actual patch
    parameters. 

    Have I missed the point or is this what you're thinking about? 

-b

    re .2 - yep, that's the sort of thing I was thinking about.
    
    Right now, my "patch database" is maintained on paper; it gets
    out of date quite quickly, and it's practically impossible to search.
    
    Uhm, what's a "segmented P key" (I ain't no steenking database
    jock...)?
    
    You've got the same idea I had, that some indication of performance
    options would be useful (e.g., responds to aftertouch).
    
    I'll remember to bring my notes next time, won't I?
    
    And what happened to reply .1?
    
    len.
    

    A segmented P key (P is short for Primary) means a primary key that
    consists of two separate fields.  You generally want a P key to be
    unique, because overhead with duplicates is a pig in terms of lookups. 

    For example:

	|    PRIMARY KEY   |

Field:	|  Model  | Patch  |

	ESQ1______FARTBL____etc
	ESQ1______DIGPNO____etc
	DX7_______FM PIANO__etc

    That way, you could do a

	for PATCHES with MODEL="ESQ" and DESCRIPTION containing "GRIT"

    speaking in Datatrieve-ese.

    And .1 was a reply to the another note, so I moved it.

-b

    The Steinberg editor for the Roland D50 has a database library facility
    (one of the reasons I went for it). For each patch you can associate
    up to 8 terms (like "brassy", "fat" etc) from a semantics file of
    256 terms (user defined). You can then perform searches using from
    1 to 8 terms as match criteria.
    
    I've found it useful.  The only drag is having to catalogue your
    patches with the approriate terms. Having done this however, the
    rest is easy.                   
    
    Alex
    

    I have a librarian for the DX7/TX802 that I wrote for the P/D that
    allows you to do a search on all the banks you have on disk for
    a character or string of characters such as "strings". It then creates
    new banks (now called libraries) with these new patches that you
    can then edit etc. 
    It runs on a PC/AT and requires an MPU-401. If anybody is interested
    send mail and we can figure out how to get it to you. 
    
    I've used it now for about two years and couldnt do without it.
    
    Ken
    

< Note 1903.0 by DRUMS::FEHSKENS >
                        -< Patch Databases/Librarians >-

Len,

I just purchased Microsoft Works to database my patches and sampler disk
library. John Arnold also uses it. I have a Mac, but I imagine it is
available for the AMIGA. It combines the best features of dbase, spread
sheet, word processor, etc. There was an article by Craig Anderton in
Keyboard several months back about using MS Works to catalog his EPS
disks. It is working out perfect for my needs. I use the following fields...


Disk #	Description			Quality		Equipment
-----------------------------------------------------------------
103	Solo Flute Orchestral		fair		EPS
241	Solo Flute Orchestral		good		S550
278	Unison Flute Orchestral		good		S550

The biggest advantage is doing a search. You can search any combination
of fields, with boolean rules, for keywords. For instance, you can...

List all solo flutes AND quality=good AND equipment=S550

or

List all disk=103

Data base entry is very fast. It jumps from field to field in sequence as
you enter the data. You can go backwards and forwards between fields.

dave

    Hi - I'm looking for good librarians for my D-50 and ESQ-Ms. By that
    I mean ones that will allow you to group sounds together into a new
    sound bank according to what criteria you specify (i. e. a search
    key for piano sounds, etc.), as well as auto-generating of new patches,
    easy parameter editing, etc.

    I own a Compaq (IBM compatible) and am beginning to think of getting
    a MAC or an ATARI also, since IBM seems to be the last machine that
    anyone writes MIDI software for (it's always MAC, ATARI, then IBM or
    AMIGA, etc.).

    I've been looking around (Keyboard magazine and the notes file) and
    haven't come up with anything that fills the bill except the latest
    offering by Steinberg (D-50 librarian for the Atari ST).

    Any suggestions for the Compaq?

    Thanks, Bill

Check the back of keyboard magazine. It usually has some stuff. I also 
remember (I think) seeing some demos or free stuff on either Compuserve or 
Genie. You may want to check there (I'll check next time I log on).

Geoff

    I know of no patch librarians that are intelligent enough to do the
    things you're asking Bill (unless Uncle Len has written his killer A/I
    package 8-). 

    If you're interested in using the computer to do patch EDITING as well
    as librarian functions, I'd check Dr. T and Steinberg (although you're
    going to pay a pop or two per package - around $250 I'd guess). 

    If you're looking for a good "generic" librarian and have an Atari ST,
    I *highly* recommend OMNI-BANKER ST by Paradigm (see topic 1668). It's
    a great piece of code. 

-b

    
    I have the STEINBERG D50 editor. It works well.. Any questions ?
    
    				
    					Paul.
    
      
    
    

    RE: .13 - Yea, will it work on a 520? Since I don't want to spend
    $$$ on a 2nd PC, I was thinking of getting a used 520.
    
    By the way - I was thinking (and this will take a lot of time,
    but having to initialize the search string parameters on the Steinberg
    would also) of picking out my favorite patches off of all of my
    banks, and copying them to an E-PROM2 (I have only one), such that
    the 1st ten patches are strings, for example, and the 2nd ten are
    piano, etc. As it stands now, I have written notes on most of my
    patches, but they are scattered over several banks in the PC, and
    to listen to each one just to pick out the one that best suits the
    current song, well, takes just too long!

    Bill

    
    
    re -1
    
    That's about the only question I can't answer as I don't have a
    520. I can't believe that it would need a megabyte though !
    
    
    					Paul.