home *** CD-ROM | disk | FTP | other *** search
- 11-Jan-95-chh
- Jaleo insert.
-
- There are several patch sets available that are not to-specs according
- to the Forte/Gravis documentation. Below is a list and whether Ruckus
- supports them and on what Ruckus uses to identify them.
-
- Included with Jaleo now is PATCHIS.EXE, a GUS patch file browser. With
- it you can identify bogus patches. For patch header format, grab the
- current GUS SDK. Two or more sources are preferred since typos abound.
-
- --------
- 808DRUMS
- 909DRUMS
-
- Both these patch sets set the low and high bounds of the sample to
- values that are not appropriate for percussive instruments. Technically,
- it's legal, however, the builder assumes that the root frequency,
- as specified in the header, is to be used as the "normal" sound-at
- frequency (there is no "pitch to play at" for percussive instruments).
- This is not recommended because patches may be based on a root frequency
- that has nothing at all to do with the actual output frequency. The root
- frequency is used for calculations and is not used for anything else.
- However, since the standard GUS patches all have low=root=high, Ruckus
- will now use ROOT for drum patches to accommodate the bogus 808DRUMS and
- 909DRUMS patch sets. These patches also have their INSTRUMENT_SIZE=1 byte.
- This was caused by a bug in the tool used to create these patches (PATCH.EXE
- from early GUS SDKs).
-
-
- -------
- E_POWER
-
- These patches were created with Patch Maker 1.13. The problem with
- these is that their envelope rates are all set to 3F, or 1.4ms.
- This causes the drum sound to complete in 6 points * 1.4ms, or 8.4ms
- (about 0.0084 seconds). There is no immediate fix/work-around that I
- know of, other than having these rates set to realistic values, and
- that is beyond the scope of Ruckus (it can't know what values are
- realistic for all those patches). Compare to OEM patches included
- with your GUS. 3Fh is the fastest rate (shortest time on); C1h
- is the longest (often seen as point #2 on kick drums, for example).
-
- The designer of these drum patches can fix up most of the problem by
- enabling SUSTAIN for these patches. This way, the sound will remain
- on until the "note off" is issued by the MIDI stream. This, of course,
- only if a useable patch editor can't be used instead of the crippled
- PMlite program.
-
- ---------------
- To be continued
-