Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!ucsd!ucbvax!kepler.Berkeley.EDU!me128-aw
From: me128-aw@kepler.Berkeley.EDU (me128 student)
Newsgroups: comp.sys.amiga.tech
Subject: Re: limited interoperability of SMUS files
Message-ID: <27305@ucbvax.BERKELEY.EDU>
Date: 2 Jan 89 02:33:10 GMT
References: <3192@sugar.uu.net>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: me128-aw@kepler.Berkeley.EDU (me128 student)
Organization: University of California, Berkeley
Lines: 13

In article <3192@sugar.uu.net> karl@sugar.uu.net (Karl Lehenbauer) writes:
>Programs that read and write SMUS files are not stellar in their 
>interoparability.  For example, the SMUS files written by Soundscape
>cause Deluxe Music to get a "Software Error/Task Held."  Examination has 
[stuff deleted]

I found another error in DMCS.  When reading SMUS files, it ignores the
iRegister field in an INS1 chunk, instead assuming that the instruments
are all contiguously numbered starting from 0.  Thus, if the score was
created in a program such as SONIX and lots of instruments loading and
deleting was done, all the wrong instruments will be played.

-Vince Lee