Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnews!cbnewsm!nsw
From: nsw@cbnewsm.att.com (Neil Weinstock)
Newsgroups: comp.sys.amiga.audio
Subject: Re: Music-X
Message-ID: <1991Feb24.222432.22353@cbnewsm.att.com>
Date: 24 Feb 91 22:24:32 GMT
References: <21289@know.pws.bull.com> <7619@jhunix.HCF.JHU.EDU>
Distribution: usa
Organization: The Flying Squid Patrol
Lines: 37

In article <7619@jhunix.HCF.JHU.EDU> barrett@jhunix.HCF.JHU.EDU (Dan Barrett) writes:
>In article <21289@know.pws.bull.com> pmiller@vttcf.cc.vt.edu (Paul Miller) writes:
[ ... ]
>>and do the built-in librarians handle D-50 and Korg M-1 patches?
>
>	I recall seeing not only a D-50 librarian, but a D-50 patch
>editor included.  I don't think there's M-1 support supplied.
>
>	HOWEVER, it comes with a "generic" librarian protocol that
>captures almost any data.
>
>	ALSO HOWEVER, you can write your own protocol in about an hour if
>you understand MIDI system-exclusive format.
[ ... ]

The M-1 is tricky due to the funky way the sys-ex data is encoded.  There
is no explicit support for it in the Music-X generic librarian.

It should be possible to get a patch protocol up and running, though I
tried and failed a while back (I oughta try again, since I know more now...)
Limitations are:

	1)  The names will look at least a little funny, since there is 
	    character in the middle that corresponds to the high-order bits
	    of seven other characters.

	2)  Don't even *think* of trying the generic patch editor on the data,
	    unless you are some amazing kind of masochist.

Like I said, it should be possible, and the above limitations aren't too
terrible.  If I come up with one I'll post it.

                                   - Neil

--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--
Neil Weinstock @ AT&T Bell Labs        //     What was sliced bread
att!edsel!nsw or nsw@edsel.att.com   \X/    the greatest thing since?