Copyright (c) Hyperion Entertainment and contributors.

Difference between revisions of "8SVX IFF 8-Bit Sampled Voice"

From AmigaOS Documentation Wiki
Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
= “8SVX” IFF 8-Bit Sampled Voice =
+
= 8SVX IFF 8-Bit Sampled Voice =
   
  +
; Document Date:
<table>
 
  +
: February 7, 1985
<tbody>
 
  +
; From:
<tr class="odd">
 
  +
: Steve Hayes and Jerry Morrison, Electronic Arts
<td align="left">'''Document Date:'''</td>
 
  +
; Status Of Standard:
<td align="left">7.9cmFebruary 7, 1985</td>
 
  +
: Adopted
</tr>
 
<tr class="even">
 
<td align="left">'''From:'''</td>
 
<td align="left">7.9cmSteve Hayes and Jerry Morrison, Electronic Arts</td>
 
</tr>
 
<tr class="odd">
 
<td align="left">'''Status Of Standard:'''</td>
 
<td align="left">Adopted</td>
 
</tr>
 
</tbody>
 
</table>
 
   
 
== Introduction ==
 
== Introduction ==
Line 40: Line 30:
 
describes the underlying conventions for all IFF files.
 
describes the underlying conventions for all IFF files.
   
Amiga is a registered trademark of Commodore-Amiga, Inc.
+
Amiga is a registered trademark of Amiga, Inc.
   
 
Electronic Arts is a trademark of Electronic Arts.
 
Electronic Arts is a trademark of Electronic Arts.
Line 147: Line 137:
 
The optional data chunk “ANNO” holds any text annotations typed in by the author.
 
The optional data chunk “ANNO” holds any text annotations typed in by the author.
   
An ANNO chunk is not a property chunk, so you can put more than one in a FORM 8SVX. You can make ANNO chunks any length up to 2<math>^{31}</math> - 1 characters, but 32767 is a practical limit. Since they’re not properties, ANNO chunks don’t belong in a PROP 8SVX. That means they can’t be shared over a LIST of FORMs 8SVX.
+
An ANNO chunk is not a property chunk, so you can put more than one in a FORM 8SVX. You can make ANNO chunks any length up to 2^31 - 1 characters, but 32767 is a practical limit. Since they’re not properties, ANNO chunks don’t belong in a PROP 8SVX. That means they can’t be shared over a LIST of FORMs 8SVX.
   
 
Syntactically, each of these chunks contains an array of 8-bit ASCII characters in the range “ ” (SP, hex 20) through “~” (tilde, hex 7F), just like a standard “TEXT” chunk. [See “Strings, String Chunks, and String Properties” in ''“EA IFF 85” Electronic Arts Interchange File Format''.] The chunk’s ckSize field holds the count of characters.
 
Syntactically, each of these chunks contains an array of 8-bit ASCII characters in the range “ ” (SP, hex 20) through “~” (tilde, hex 7F), just like a standard “TEXT” chunk. [See “Strings, String Chunks, and String Properties” in ''“EA IFF 85” Electronic Arts Interchange File Format''.] The chunk’s ckSize field holds the count of characters.
Line 205: Line 195:
 
[[File:DevIFF-16.png]]
 
[[File:DevIFF-16.png]]
   
In general, the BODY has ctOctave octaves of data. The highest frequency octave comes first, comprising the fewest samples: oneShotHiSamples + repeatHiSamples. Each successive octave contains twice as many samples as the next higher octave but the same number of cycles. The lowest frequency octave comes last with the most samples: 2<math>^{ctOctave-1}</math> * (oneShotHiSamples + repeatHiSamples).
+
In general, the BODY has ctOctave octaves of data. The highest frequency octave comes first, comprising the fewest samples: oneShotHiSamples + repeatHiSamples. Each successive octave contains twice as many samples as the next higher octave but the same number of cycles. The lowest frequency octave comes last with the most samples: 2^(ctOctave-1) * (oneShotHiSamples + repeatHiSamples).
   
 
The number of samples in the BODY chunk is
 
The number of samples in the BODY chunk is
   
(2<math>^{0}</math> + ... + 2<math>^{ctOctave-1}</math> ) * (oneShotHiSamples + repeatHiSamples)
+
(2^0 + ... + 2^(ctOctave-1) ) * (oneShotHiSamples + repeatHiSamples)
   
 
Figure 3, below, looks closer at an example waveform within one octave of a different BODY chunk. In this example, oneShotHiSamples / samplesPerHiCycle = 2 cycles and repeatHiSamples / samplesPerHiCycle = 1 cycle.
 
Figure 3, below, looks closer at an example waveform within one octave of a different BODY chunk. In this example, oneShotHiSamples / samplesPerHiCycle = 2 cycles and repeatHiSamples / samplesPerHiCycle = 1 cycle.
Line 217: Line 207:
 
To avoid playback “clicks” the one-shot part should begin with a small sample value, and flow smoothly into the repeat part. The end of the repeat part should flow smoothly into the beginning of the next repeat part.
 
To avoid playback “clicks” the one-shot part should begin with a small sample value, and flow smoothly into the repeat part. The end of the repeat part should flow smoothly into the beginning of the next repeat part.
   
If the VHDR field sCompression <math>\ne</math> sCmpNone, the BODY chunk is just an array of data bytes to feed through the specified decompresser function. All this stuff about sample sizes, octaves, and repeat parts applies to the decompressed data.
+
If the VHDR field sCompression != sCmpNone, the BODY chunk is just an array of data bytes to feed through the specified decompresser function. All this stuff about sample sizes, octaves, and repeat parts applies to the decompressed data.
   
 
Be sure to follow an odd-length BODY chunk with a 0 pad byte.
 
Be sure to follow an odd-length BODY chunk with a 0 pad byte.
Line 363: Line 353:
 
D1Unpack(source + 2, n - 2, dest, source[1]);
 
D1Unpack(source + 2, n - 2, dest, source[1]);
 
}</pre>
 
}</pre>
  +
  +
  +
= 8SVX.CHAN.PAN =
  +
  +
<pre>
  +
SMUS.CHAN and SMUS.PAN Chunks
  +
Stereo imaging in the "8SVX" IFF 8-bit Sample Voice
  +
---------------------------------------------------
  +
Registered by David Jones, Gold Disk Inc.
  +
  +
There are two ways to create stereo imaging when playing back a digitized
  +
sound. The first relies on the original sound being created with a stereo
  +
sampler: two different samples are digitized simultaneously, using right and
  +
left inputs. To play back this type of sample while maintaining the
  +
stereo imaging, both channels must be set to the same volume. The second type
  +
of stereo sound plays the identical information on two different channels at
  +
different volumes. This gives the sample an absolute position in the stereo
  +
field. Unfortunately, there are currently a number of methods for doing this
  +
currently implemented on the Amiga, none truly adhering to any type of
  +
standard. What I have tried to to is provide a way of doing this
  +
consistently, while retaining compatibility with existing (non-standard)
  +
systems. Introduced below are two optional data chunks, CHAN and PAN. CHAN
  +
deals with sounds sampled in stereo, and PAN with samples given stereo
  +
characteristics after the fact.
  +
  +
  +
Optional Data Chunk CHAN
  +
________________________
  +
  +
This chunk is already written by the software for a popular stereo sampler. To
  +
maintain the ability read these samples, its implementation here is
  +
therefore limited to maintain compatability.
  +
  +
The optional data chunk CHAN gives the information neccessary to play a
  +
sample on a specified channel, or combination of channels. This chunk
  +
would be useful for programs employing stereo recording or playback of sampled
  +
sounds.
  +
  +
#define RIGHT 4L
  +
#define LEFT 2L
  +
#define STEREO 6L
  +
  +
#define ID_CHAN MakeID('C','H','A','N')
  +
  +
typedef sampletype LONG;
  +
  +
If &quot;sampletype&quot; is RIGHT, the program reading the sample knows that it was
  +
originally intended to play on a channel routed to the right speaker,
  +
(channels 1 and 2 on the Amiga). If &quot;sampletype&quot; is LEFT, the left speaker
  +
was intended (Amiga channels 0 and 3). It is left to the discretion of the
  +
programmer to decide whether or not to play a sample when a channel on the
  +
side designated by &quot;sampletype&quot; cannot be allocated.
  +
  +
If &quot;sampletype&quot; is STEREO, then the sample requires a pair of channels routed
  +
to both speakers (Amiga pairs [0,1] and [2,3]). The BODY chunk for stereo
  +
pairs contains both left and right information. To adhere to existing
  +
conventions, sampling software should write first the LEFT information,
  +
followed by the RIGHT. The LEFT and RIGHT information should be equal in
  +
length.
  +
  +
Again, it is left to the programmer to decide what to do if a channel for
  +
a stereo pair can't be allocated; wether to play the available channel only,
  +
or to allocate another channels routed to the wrong speaker.
  +
  +
  +
  +
Optional Data Chunk PAN
  +
_______________________
  +
  +
The optional data chunk PAN provides the neccessary information to create a
  +
stereo sound using a single array of data. It is neccessary to replay the
  +
sample simultaneously on two channels, at different volumes.
  +
  +
#define ID_PAN MakeID('P','A','N',' ')
  +
  +
typedef sposition Fixed; /* 0 &lt;= sposition &lt;= Unity */
  +
/* Unity is elsewhere #defined as 10000L, and
  +
* refers to the maximum possible volume.
  +
* /
  +
  +
/* Please note that 'Fixed' (elsewhere #defined as LONG) is used to
  +
* allow for compatabilty between audio hardware of different resolutions.
  +
*/
  +
  +
The 'sposition' variable describes a position in the stereo field. The
  +
numbers of discrete stereo positions available is equal to 1/2 the number of
  +
discrete volumes for a single channel.
  +
  +
The sample must be played on both the right and left channels. The overall
  +
volume of the sample is determined by the &quot;volume&quot; field in the Voice8Header
  +
structure in the VHDR chunk.
  +
  +
The left channel volume = overall volume / (Unity / sposition).
  +
&quot; right &quot; &quot; = overall volume - left channel volume.
  +
  +
For example:
  +
If sposition = Unity, the sample is panned all the way to the left.
  +
If sposition = 0, the sample is panned all the way to the right.
  +
If sposition = Unity/2, the sample is centered in the stereo field.</pre>
  +
</pre>
  +
  +
  +
= 8SVX.SEQN.FADE =
  +
  +
<pre>
  +
SEQN and FADE Chunks
  +
  +
  +
Multiple Loop Sequencing in the &quot;8SVX&quot; IFF 8-bit Sample Voice
  +
---------------------------------------------------
  +
Registered by Peter Norman, RamScan Software Pty Ltd.
  +
  +
  +
  +
  +
Sound samples are notorious for demanding huge amounts of memory.
  +
  +
While earlier uses of digital sound on the Amiga were mainly in the form of
  +
short looping waveforms for use as musical instruments, many people today
  +
wish to record several seconds (even minutes) of sound. This of course eats
  +
memory.
  +
  +
Assuming that quite often the content of these recordings is music, and that
  +
quite often music contains several passages which repeat at given times,
  +
&quot;verse1 .. chorus .. verse2 .. chorus ..&quot; etc, a useful extention has been
  +
added to the 8SVX list of optional data chunks. It's purpose is to conserve
  +
memory by having the computer repeat sections rather than having several
  +
instances of a similar sound or musical passage taking up valuable sample
  +
space.
  +
  +
  +
The &quot;SEQN&quot; chunk has been created to define &quot;Multiple&quot; loops or sections
  +
within a single octave 8SVX MONO or STEREO waveform.
  +
  +
It is intended that a sampled sound player program which supports this chunk
  +
will play sections of the waveform sequentially in an order that the SEQN
  +
chunk specifies. This means for example, if an identical chorus
  +
repeats throughout a recording, rather than have this chorus stored several
  +
times along the waveform, it is only necessary to have one copy of the chorus
  +
stored in the waveform.
  +
  +
A &quot;SEQeNce&quot; of definitions can then be set up to have the computer loop back
  +
and repeat the chorus at the required time. The remaining choruses
  +
stored in the waveform will no longer be necessary and can be removed.
  +
  +
  +
eg. If we had a recording of the following example, we would find that
  +
there are several parts which simply repeat. Substantial savings can be made
  +
by having the computer repeat sections rather than have them stored in memory.
  +
  +
  +
  +
EXAMPLE
  +
  +
&quot;Haaaallelujah....Haaaallelujah...Hallelujah..Hallelujah..Halleeeelujaaaah.&quot;
  +
  +
  +
  +
Applying a sequence to the above recording would look as follows.
  +
  +
  +
Haaaallelujah....Haaaallelujah...Hallelujah..Hallelujah..Halleeeelujaaaah.
  +
[ Loop1 ]
  +
[ Loop2 ]
  +
[ Loop3 ]
  +
[ Loop4 ]
  +
[ Loop5 ]
  +
  +
[ Dead Space ] [ Dead Space ]
  +
  +
  +
The DEAD SPACE can be removed. With careful editing of the multiple loop
  +
positions, the passage can be made to sound exactly the same as the original
  +
with far less memory required.
  +
  +
  +
  +
Chunk Definitions...
  +
  +
  +
  +
Optional Data Chunk SEQN
  +
________________________
  +
  +
The optional data chunk SEQN gives the information necessary to play a
  +
sample in a sequence of defined blocks. To have a segment repeat twice,
  +
the definition occurs twice in the list.
  +
  +
This list consists of pairs of ULONG &quot;loop start&quot; and &quot;end&quot; definitions which
  +
are offsets from the start of the waveform. The locations or values must be
  +
LONGWORD aligned (divisable by 4).
  +
  +
  +
To determine how many loop definitions in a given file, simply divide the
  +
SEQN chunk size by 8.
  +
  +
eg if chunk size == 40 ... number of loops = (40 / 8) .. equals 5 loops.
  +
  +
  +
The raw data in a file might look like this...
  +
  +
  +
  +
'S-E-Q-N' [ size ] [ Loop 1 ] [ Loop 2 ] [ Loop 3 ]
  +
  +
5345514E 00000028 00000000 00000C00 00000000 00000C00 00000C08 00002000
  +
^
  +
^ 'Haaaallelujah..' 'Haaaallelujah..' 'Hallelujah..'
  +
^
  +
^
  +
40 bytes decimal / 8 = 5 loop or segments
  +
  +
  +
  +
[ Loop 4 ] [ Loop 5 ]'B-O-D-Y' Size Data
  +
  +
00000C08 00002000 00002008 00003000 424F4459 000BE974 010101010101010
  +
  +
'Hallelujah..' 'Halleeeelujah..'
  +
  +
  +
  +
  +
  +
In a waveform containing SEQN chunks, the oneShotHiSamples should be set to 0
  +
and the repeatHiSamples should equal the BODY length (divided by 2 if STEREO).
  +
  +
Remember the locations of the start and end of each segment or loop should
  +
be LONGWORD aligned.
  +
  +
  +
If the waveform is Stereo, treat the values and locations in exactly the same
  +
way. In other words, if a loop starts at location 400 within a Stereo
  +
waveform, you start the sound at the 400th byte position in the left data
  +
and the 400th byte position in the right data simultaneously.
  +
  +
  +
  +
#define ID_SEQN MakeID('S','E','Q','N')
  +
  +
  +
  +
  +
  +
Optional Data Chunk FADE
  +
_______________________
  +
  +
  +
The FADE chunk defines at what loop number the sound should begin to
  +
fade away to silence. It is possible to finish a sample of music in much
  +
the same way as commercial music does today. A FADE chunk consists of
  +
one ULONG value which has a number in it. This number corresponds to the
  +
loop number at which the fade should begin.
  +
  +
eg. You may have a waveform containing 50 loops. A FADE definition of 45 will
  +
specify that once loop 45 is reached, fading to zero volume should begin.
  +
The rate at which this fade takes place is determined by the length of time
  +
left to play. The playing software should do a calculation based on the
  +
following...
  +
  +
  +
Length of all remaining sequences including current sequence (in bytes)
  +
  +
divided by
  +
  +
the current playback rate in samples per second
  +
  +
= time remaining.
  +
  +
  +
  +
Begin stepping the volume down at a rate which will hit zero volume just as
  +
the waveform finishes.
  +
  +
  +
  +
  +
  +
  +
  +
The raw data in a file may look like this.
  +
  +
  +
  +
  +
'F-A-D-E' [ Size ] Loop No. 'B-O-D-Y' Size Data..
  +
  +
46414445 00000004 0000002D 424F4459 000BE974 01010101 01010101 etc etc
  +
^
  +
Start fading when loop number 45 is reached.
  +
  +
  +
  +
  +
#define ID_FADE MakeID('F','A','D','E')
  +
  +
  +
  +
Although order shouldn't make much difference, it is a general rule of thumb
  +
that SEQN should come before FADE and FADE should be last before the BODY.
  +
  +
Stereo waveforms would have CHAN,SEQN,FADE,BODY in that order.
  +
</pre>

Latest revision as of 19:11, 10 May 2012

8SVX IFF 8-Bit Sampled Voice

Document Date
February 7, 1985
From
Steve Hayes and Jerry Morrison, Electronic Arts
Status Of Standard
Adopted

Introduction

This is the IFF supplement for FORM “8SVX”. An 8SVX is an IFF “data section” or “FORM” (which can be an IFF file or a part of one) containing a digitally sampled audio voice consisting of 8-bit samples. A voice can be a one-shot sound or—with repetition and pitch scaling—a musical instrument. “EA IFF 85” is Electronic Arts’ standard interchange file format. [See “EA IFF 85” Standard for Interchange Format Files.]

The 8SVX format is designed for playback hardware that uses 8-bit samples attenuated by a volume control for good overall signal-to-noise ratio. So a FORM 8SVX stores 8-bit samples and a volume level.

A similar data format (or two) will be needed for higher resolution samples (typically 12 or 16 bits). Properly converting a high resolution sample down to 8 bits requires one pass over the data to find the minimum and maximum values and a second pass to scale each sample into the range -128 through 127. So it’s reasonable to store higher resolution data in a different FORM type and convert between them.

For instruments, FORM 8SVX can record a repeating waveform optionally preceded by a startup transient waveform. These two recorded signals can be pre-synthesized or sampled from an acoustic instrument. For many instruments, this representation is compact. FORM 8SVX is less practical for an instrument whose waveform changes from cycle to cycle like a plucked string, where a long sample is needed for accurate results.

FORM 8SVX can store an “envelope” or “amplitude contour” to enrich musical notes. A future voice FORM could also store amplitude, frequency, and filter modulations.

FORM 8SVX is geared for relatively simple musical voices, where one waveform per octave is sufficient, the waveforms for the different octaves follow a factor-of-two size rule, and one envelope is adequate for all octaves. You could store a more general voice as a LIST containing one or more FORMs 8SVX per octave. A future voice FORM could go beyond one “one-shot” waveform and one “repeat” waveform per octave.

Section 2 defines the required property sound header “VHDR”, optional properties name “NAME”, copyright “(c) ”, and author “AUTH”, the optional annotation data chunk “ANNO”, the required data chunk “BODY”, and optional envelope chunks “ATAK” and “RLSE”. These are the “standard” chunks. Specialized chunks for private or future needs can be added later, e.g., to hold a frequency contour or Fourier series coefficients. The 8SVX syntax is summarized in Appendix A as a regular expression and in Appendix B as an example box diagram. Appendix C explains the optional Fibonacci-delta compression algorithm.

Reference

“EA IFF 85” Standard for Interchange Format Files

describes the underlying conventions for all IFF files.

Amiga is a registered trademark of Amiga, Inc.

Electronic Arts is a trademark of Electronic Arts.

Standard Data and Property Chunks

FORM 8SVX stores all the waveform data in one body chunk “BODY”. It stores playback parameters in the required header chunk “VHDR”. “VHDR” and any optional property chunks “NAME”, “(c) ”, and “AUTH” must all appear before the BODY chunk. Any of these properties may be shared over a LIST of FORMs 8SVX by putting them in a PROP 8SVX. [See “EA IFF 85” Standard for Interchange Format Files.]

Background

There are two ways to use FORM 8SVX: as a one-shot sampled sound or as a sampled musical instrument that plays “notes”. Storing both kinds of sounds in the same kind of FORM makes it easy to play a one-shot sound as an instrument or an instrument as a one-note sound.

A one-shot sound is a series of audio data samples with a nominal playback rate and amplitude. The recipient program can optionally adjust or modulate the amplitude and playback data rate.

For musical instruments, the idea is to store a sampled (or pre-synthesized) waveform that will be parameterized by pitch, duration, and amplitude to play each “note”. The creator of the FORM 8SVX can supply a waveform per octave over a range of octaves for this purpose. The intent is to perform a pitch by selecting the closest octave’s waveform and scaling the playback data rate. An optional “one-shot” waveform supplies an arbitrary startup transient, then a “repeat” waveform is iterated as long as necessary to sustain the note.

A FORM 8SVX can also store an envelope to modulate the waveform. Envelopes are mostly useful for variable-duration notes but could be used for one-shot sounds, too.

The FORM 8SVX standard has some restrictions. For example, each octave of data must be twice as long as the next higher octave. Most sound driver software and hardware imposes additional restrictions. E.g., the Amiga sound hardware requires an even number of samples in each one-shot and repeat waveform.

Required Property VHDR

The required property “VHDR” holds a Voice8Header structure as defined in these C declarations and following documentation. This structure holds the playback parameters for the sampled waveforms in the BODY chunk. (See “Data Chunk BODY”, below, for the storage layout of these waveforms.)

#define ID_8SVX MakeID('8', 'S', 'V', 'X')
#define ID_VHDR MakeID('V', 'H', 'D', 'R')

typedef LONG Fixed;    /* A fixed-point value, 16 bits to the left of the
                          point and 16 to the right.  A Fixed is a number
                          of 2^16ths, i.e., 65536ths.                    */
#define Unity 0x10000L /* Unity = Fixed 1.0 = maximum volume             */

/* sCompression: Choice of compression algorithm applied to the samples. */
#define sCmpNone       0    /* not compressed                            */
#define sCmpFibDelta   1    /* Fibonacci-delta encoding (Appendix C)     */
                            /* Can be more kinds in the future.          */
typedef struct {
    ULONG oneShotHiSamples, /* # samples in the high octave 1-shot part */
          repeatHiSamples,  /* # samples in the high octave repeat part */
          samplesPerHiCycle;/* # samples/cycle in high octave, else 0   */
    UWORD samplesPerSec;    /* data sampling rate                       */
    UBYTE ctOctave,         /* # octaves of waveforms                   */
          sCompression;     /* data compression technique used          */
    Fixed volume;           /* playback volume from 0 to Unity (full
                             * volume). Map this value into the output
                             * hardware's dynamic range.                */
    } Voice8Header;

[Implementation details. Fields are filed in the order shown. The UBYTE fields are byte-packed (2 per 16-bit word). MakeID is a C macro defined in the main IFF document and in the source file iff.h.]

A FORM 8SVX holds waveform data for one or more octaves, each containing a one-shot part and a repeat part. The fields oneShotHiSamples and repeatHiSamples tell the number of audio samples in the two parts of the highest frequency octave. Each successive (lower frequency) octave contains twice as many data samples in both its one-shot and repeat parts. One of these two parts can be empty across all octaves.

Note: Most audio output hardware and software has limitations. For example the Amiga computer has sound hardware that requires that all one-shot and repeat parts have even numbers of samples. Amiga sound driver software should adjust an odd-sized waveform, ignore an odd-sized lowest octave, or ignore odd 8SVX FORMs altogether. Some other output devices require all sample sizes to be powers of two.

The field samplesPerHiCycle tells the number of samples/cycle in the highest frequency octave of data, or else 0 for “unknown”. Each successive (lower frequency) octave contains twice as many samples/cycle. The samplesPerHiCycle value is needed to compute the data rate for a desired playback pitch.

Actually, samplesPerHiCycle is an average number of samples/cycle. If the one-shot part contains pitch bends, store the samples/cycle of the repeat part in samplesPerHiCycle. The division repeatHiSamples/samplesPerHiCycle should yield an integer number of cycles. (When the repeat waveform is repeated, a partial cycle would come out as a higher-frequency cycle with a “click”.)

More limitations: some Amiga music drivers require samplesPerHiCycle to be a power of two in order to play the FORM 8SVX as a musical instrument in tune. They may even assume samplesPerHiCycle is a particular power of two without checking. (If samplesPerHiCycle is different by a factor of two, the instrument will just be played an octave too low or high.)

The field samplesPerSec gives the sound sampling rate. A program may adjust this to achieve frequency shifts or vary it dynamically to achieve pitch bends and vibrato. A program that plays a FORM 8SVX as a musical instrument would ignore samplesPerSec and select a playback rate for each musical pitch.

The field ctOctave tells how many octaves of data are stored in the BODY chunk. See “Data Chunk BODY”, below, for the layout of the octaves.

The field sCompression indicates the compression scheme, if any, that was applied to the entire set of data samples stored in the BODY chunk. This field should contain one of the values defined above. Of course, the matching decompression algorithm must be applied to the BODY data before the sound can be played. (The Fibonacci-delta encoding scheme sCmpFibDelta is described in Appendix C.) Note that the whole series of data samples is compressed as a unit.

The field volume gives an overall playback volume for the waveforms (all octaves). It lets the 8-bit data samples use the full range -128 through 127 for good signal-to-noise ratio. The playback program should multiply this value by a “volume control” and perhaps by a playback envelope (see ATAK and RLSE, below).

To store a one-shot sound in a FORM 8SVX, set oneShotHiSamples = number of samples, repeatHiSamples = 0 , samplesPerHiCycle = 0, samplesPerSec = sampling rate, and ctOctave = 1. Scale the signal amplitude to the full sampling range -128 through 127. Set volume so the sound will playback at the desired volume level. If you set the samplesPerHiCycle field properly, the data can also be used as a musical instrument.

Experiment with data compression. If the decompressed signal sounds OK, store the compressed data in the BODY chunk and set sCompression to the compression code number.

To store a musical instrument in a FORM 8SVX, first record or synthesize as many octaves of data as you want to make available for playback. Set ctOctave to the count of octaves. From the recorded data, excerpt an integral number of steady state cycles for the repeat part and set repeatHiSamples and samplesPerHiCycle. Either excerpt a startup transient waveform and set oneShotHiSamples, or else set oneShotHiSamples to 0. Remember, the one-shot and repeat parts of each octave must be twice as long as those of the next higher octave. Scale the signal amplitude to the full sampling range and set volume to adjust the instrument playback volume. If you set the samplesPerSec field properly, the data can also be used as a one-shot sound.

A distortion-introducing compressor like sCmpFibDelta is not recommended for musical instruments, but you might try it anyway.

Typically, creators of FORM 8SVX record an acoustic instrument at just one frequency. Decimate (down-sample with filtering) to compute higher octaves. Interpolate to compute lower octaves.

If you sample an acoustic instrument at different octaves, you may find it hard to make the one-shot and repeat waveforms follow the factor-of-two rule for octaves. To compensate, lengthen an octave’s one-shot part by appending replications of the repeating cycle or prepending zeros. (This will have minimal impact on the sound’s start time.) You may be able to equalize the ratio of one-shot-samples to repeat-samples across all octaves.

Note that a “one-shot sound” may be played as a “musical instrument” and vice-versa. However, an instrument player depends on samplesPerHiCycle, and a one-shot player depends on samplesPerSec.

To play any FORM 8SVX data as a one-shot sound, first select an octave if ctOctave > 1. (The lowest-frequency octave has the greatest resolution.) Play the one-shot samples then the repeat samples, scaled by volume, at a data rate of samplesPerSec. Of course, you may adjust the playback rate and volume. You can play out an envelope, too. (See ATAK and RLSE, below.)

To play a musical note using any FORM 8SVX, first select the nearest octave of data from those available. Play the one-shot waveform then cycle on the repeat waveform as long as needed to sustain the note. Scale the signal by volume, perhaps also by an envelope, and by a desired note volume. Select a playback data rate s samples/second to achieve the desired frequency (in Hz):

4.5em frequency = s / samplesPerHiCycle

for the highest frequency octave.

The idea is to select an octave and one of 12 sampling rates (assuming a 12-tone scale). If the FORM 8SVX doesn’t have the right octave, you can decimate or interpolate from the available data.

When it comes to musical instruments, FORM 8SVX is geared for a simple sound driver. Such a driver uses a single table of 12 data rates to reach all notes in all octaves. That’s why 8SVX requires each octave of data to have twice as many samples as the next higher octave. If you restrict samplesPerHiCycle to a power of two, you can use a predetermined table of data rates.

Optional Text Chunks NAME, (c), AUTH, ANNO

Several text chunks may be included in a FORM 8SVX to keep ancillary information.

The optional property “NAME” names the voice, for instance “tubular bells”.

The optional property “(c) ” holds a copyright notice for the voice. The chunk ID “(c) ” serves as the copyright characters “©”. E.g., a “(c) ” chunk containing “1986 Electronic Arts” means “© 1986 Electronic Arts”.

The optional property “AUTH” holds the name of the instrument’s “author” or “creator”.

The chunk types “NAME”, “(c) ”, and “AUTH” are property chunks. Putting more than one NAME (or other) property in a FORM is redundant. Just the last NAME counts. A property should be shorter than 256 characters. Properties can appear in a PROP 8SVX to share them over a LIST of FORMs 8SVX.

The optional data chunk “ANNO” holds any text annotations typed in by the author.

An ANNO chunk is not a property chunk, so you can put more than one in a FORM 8SVX. You can make ANNO chunks any length up to 2^31 - 1 characters, but 32767 is a practical limit. Since they’re not properties, ANNO chunks don’t belong in a PROP 8SVX. That means they can’t be shared over a LIST of FORMs 8SVX.

Syntactically, each of these chunks contains an array of 8-bit ASCII characters in the range “ ” (SP, hex 20) through “~” (tilde, hex 7F), just like a standard “TEXT” chunk. [See “Strings, String Chunks, and String Properties” in “EA IFF 85” Electronic Arts Interchange File Format.] The chunk’s ckSize field holds the count of characters.

#define ID_NAME MakeID('N', 'A', 'M', 'E')
/* NAME chunk contains a CHAR[], the voice's name.          */

define ID_Copyright MakeID('(', 'c', ')', ' ')
/* "(c) " chunk contains a CHAR[], the FORM's copyright notice.*/

#define ID_AUTH MakeID('A', 'U', 'T', 'H')
/* AUTH chunk contains a CHAR[], the author's name.         */

#define ID_ANNO MakeID('A', 'N', 'N', 'O')
/* ANNO chunk contains a CHAR[], author's text annotations. */

Remember to store a 0 pad byte after any odd-length chunk.

Optional Data Chunks ATAK and RLSE

The optional data chunks ATAK and RLSE together give a piecewise-linear “envelope” or “amplitude contour”. This contour may be used to modulate the sound during playback. It’s especially useful for playing musical notes of variable durations. Playback programs may ignore the supplied envelope or substitute another.

#define ID_ATAK MakeID('A', 'T', 'A', 'K')
#define ID_RLSE MakeID('R', 'L', 'S', 'E')

typedef struct {
    UWORD duration; /* segment duration in milliseconds, > 0 */
    Fixed dest;     /* destination volume factor             */
    } EGPoint;

/* ATAK and RLSE chunks contain an EGPoint[], piecewise-linear envelope.*/
/* The envelope defines a function of time returning Fixed values. It's *
 * used to scale the nominal volume specified in the Voice8Header.      */

To explain the meaning of the ATAK and RLSE chunks, we’ll overview the envelope generation algorithm. Start at 0 volume, step through the ATAK contour, then hold at the sustain level (the last ATAK EGPoint’s dest), and then step through the RLSE contour. Begin the release at the desired note stop time minus the total duration of the release contour (the sum of the RLSE EGPoints’ durations). The attack contour should be cut short if the note is shorter than the release contour.

The envelope is a piecewise-linear function. The envelope generator interpolates between the EGPoints.

Remember to multiply the envelope function by the nominal voice header volume and by any desired note volume.

Figure 1 shows an example envelope. The attack period is described by 4 EGPoints in an ATAK chunk. The release period is described by 4 EGPoints in a RLSE chunk. The sustain period in the middle just holds the final ATAK level until it’s time for the release.

DevIFF-15.png

Note: The number of EGPoints in an ATAK or RLSE chunk is its ckSize / sizeof(EGPoint). In RAM, the playback program may terminate the array with a 0 duration EGPoint.

Issue: Synthesizers also provide frequency contour (pitch bend), filtering contour (wah-wah), amplitude oscillation (tremolo), frequency oscillation (vibrato), and filtering oscillation (leslie). In the future, we may define optional chunks to encode these modulations. The contours can be encoded in linear segments. The oscillations can be stored as segments with rate and depth parameters.

Data Chunk BODY

The BODY chunk contains the audio data samples.

#define ID_BODY MakeID('B', 'O', 'D', 'Y')

typedef character BYTE;     /* 8 bit signed number, -128 through 127. */
/* BODY chunk contains a BYTE[], array of audio data samples.         */

The BODY contains data samples grouped by octave. Within each octave are one-shot and repeat portions. Figure 2 depicts this arrangement of samples for an 8SVX where oneShotHiSamples = 24, repeatHiSamples = 16, samplesPerHiCycle = 8, and ctOctave = 3. The major divisions are octaves, the intermediate divisions separate the one-shot and repeat portions, and the minor divisions are cycles.

DevIFF-16.png

In general, the BODY has ctOctave octaves of data. The highest frequency octave comes first, comprising the fewest samples: oneShotHiSamples + repeatHiSamples. Each successive octave contains twice as many samples as the next higher octave but the same number of cycles. The lowest frequency octave comes last with the most samples: 2^(ctOctave-1) * (oneShotHiSamples + repeatHiSamples).

The number of samples in the BODY chunk is

(2^0 + ... + 2^(ctOctave-1) ) * (oneShotHiSamples + repeatHiSamples)

Figure 3, below, looks closer at an example waveform within one octave of a different BODY chunk. In this example, oneShotHiSamples / samplesPerHiCycle = 2 cycles and repeatHiSamples / samplesPerHiCycle = 1 cycle.

DevIFF-17.png

To avoid playback “clicks” the one-shot part should begin with a small sample value, and flow smoothly into the repeat part. The end of the repeat part should flow smoothly into the beginning of the next repeat part.

If the VHDR field sCompression != sCmpNone, the BODY chunk is just an array of data bytes to feed through the specified decompresser function. All this stuff about sample sizes, octaves, and repeat parts applies to the decompressed data.

Be sure to follow an odd-length BODY chunk with a 0 pad byte.

Other Chunks

Issue: In the future, we may define an optional chunk containing Fourier series coefficients for a repeating waveform. An editor for this kind of synthesized voice could modify the coefficients and regenerate the waveform.

See the IFF Registry and the Third-Party Specification section for details on additional 8SVX Chunks such as CHAN, PAN, SEQN and FADE.

Appendix A. Quick Reference

Type Definitions

#define ID_8SVX MakeID('8', 'S', 'V', 'X')
#define ID_VHDR MakeID('V', 'H', 'D', 'R')

typedef LONG Fixed;    /* A fixed-point value, 16 bits to the left of  *
                          the point and 16 to the right. A Fixed is a  *
                          number of 2^16ths, i.e., 65536ths.           */
#define Unity 0x10000L /* Unity = Fixed 1.0 = maximum volume           */


/* sCompression: Choice of compression algorithm.                    */
#define sCmpNone       0    /* not compressed                        */
#define sCmpFibDelta   1    /* Fibonacci-delta encoding (Appendix C) */
                            /* Can be more kinds in the future.      */

typedef struct {
    ULONG oneShotHiSamples, /* # samples in the high octave 1-shot part */
          repeatHiSamples,  /* # samples in the high octave repeat part */
          samplesPerHiCycle;/* # samples/cycle in high octave, else 0   */
    UWORD samplesPerSec;    /* data sampling rate                       */
    UBYTE ctOctave,         /* # octaves of waveforms                   */
          sCompression;     /* data compression technique used          */
    Fixed volume;           /* playback volume from 0 to Unity (full    *
                             * volume). Map this value into the output  *
                             * hardware's dynamic range.                */
    } Voice8Header;


#define ID_NAME MakeID('N', 'A', 'M', 'E')
/* NAME chunk contains a CHAR[], the voice's name.                     */

#define ID_Copyright MakeID('(', 'c', ')', ' ')
/* "(c) " chunk contains a CHAR[], the FORM's copyright notice.        */

#define ID_AUTH MakeID('A', 'U', 'T', 'H')
/* AUTH chunk contains a CHAR[], the author's name.                    */

#define ID_ANNO MakeID('A', 'N', 'N', 'O')
/* ANNO chunk contains a CHAR[], author's text annotations.            */

#define ID_ATAK MakeID('A', 'T', 'A', 'K')
#define ID_RLSE MakeID('R', 'L', 'S', 'E')


typedef struct {
    UWORD duration; /* segment duration in milliseconds, > 0           */
    Fixed dest;     /* destination volume factor                       */
    } EGPoint;


/* ATAK and RLSE chunks contain an EGPoint[],piecewise-linear envelope. */
/* The envelope defines a function of time returning Fixed values. It's *
 * used to scale the nominal volume specified in the Voice8Header.      */

#define ID_BODY MakeID('B', 'O', 'D', 'Y')
typedef character BYTE;     /* 8 bit signed number, -128 through 127.   */
/* BODY chunk contains a BYTE[], array of audio data samples.           */

8SVX Regular Expression

Here’s a regular expression summary of the FORM 8SVX syntax. This could be an IFF file or part of one.

8SVX     ::= "FORM" #{  "8SVX" VHDR [NAME] [Copyright] [AUTH] ANNO*
                        [ATAK] [RLSE] BODY }

VHDR     ::= "VHDR" #{ Voice8Header     }
NAME     ::= "NAME" #{ CHAR*    } [0]
Copyright::= "(c) " #{ CHAR*    } [0]
AUTH     ::= "AUTH" #{ CHAR*    } [0]
ANNO     ::= "ANNO" #{ CHAR*    } [0]

ATAK     ::= "ATAK" #{ EGPoint* }
RLSE     ::= "RLSE" #{ EGPoint* }
BODY     ::= "FORM" #{ BYTE*    } [0]

The token “#” represents a ckSize LONG count of the following <math>\{</math>braced<math>\}</math> data bytes. E.g., a VHDR’s “#” should equal sizeof(Voice8Header). Literal items are shown in “quotes”, [square bracket items] are optional, and “*” means 0 or more replications. A sometimes-needed pad byte is shown as “[0]”.

Actually, the order of chunks in a FORM 8SVX is not as strict as this regular expression indicates. The property chunks VHDR, NAME, Copyright, and AUTH may actually appear in any order as long as they all precede the BODY chunk. The optional data chunks ANNO, ATAK, and RLSE don’t have to precede the BODY chunk. And of course, new kinds of chunks may appear inside a FORM 8SVX in the future.

Appendix B. 8SVX Example

Here’s a box diagram for a simple example containing the three octave BODY shown earlier in Figure 2.

DevIFF-18.png

The “0” after the NAME chunk is a pad byte.

Appendix C. Fibonacci Delta Compression

This is Steve Hayes’ Fibonacci Delta sound compression technique. It’s like the traditional delta encoding but encodes each delta in a mere 4 bits. The compressed data is half the size of the original data plus a 2-byte overhead for the initial value. This much compression introduces some distortion, so try it out and use it with discretion.

To achieve a reasonable slew rate, this algorithm looks up each stored 4-bit value in a table of Fibonacci numbers. So very small deltas are encoded precisely while larger deltas are approximated. When it has to make approximations, the compressor should adjust all the values (forwards and backwards in time) for minimum overall distortion.

Here is the decompressor written in the C programming language.

/* Fibonacci delta encoding for sound data. */
BYTE codeToDelta[16] = {-34,-21,-13,-8,-5,-3,-2,-1,0,1,2,3,5,8,13,21};

/* Unpack Fibonacci-delta encoded data from n byte source buffer into
 * 2*n byte dest buffer, given initial data value x.  It returns the
 * last data value x so you can call it several times to incrementally
 * decompress the data.                                             */
short D1Unpack(source, n, dest, x)
    BYTE source[], dest[];
    LONG n;
    BYTE x;
    {
    BYTE d;
    LONG i, lim;

    lim = n << 1;
    for (i = 0; i < lim; ++i)
            { /* Decode a data nibble; high nibble then low nibble. */
            d = source[i >> 1];    /* get a pair of nibbles        */
            if (i & 1)              /* select low or high nibble?   */
                    d &= 0xf;       /* mask to get the low nibble   */
            else
                    d >>= 4;       /* shift to get the high nibble */
            x += codeToDelta[d];    /* add in the decoded delta     */
            dest[i] = x;            /* store a 1-byte sample        */
            }
    return(x);
    }

/* Unpack Fibonacci-delta encoded data from n byte source buffer into
 * 2*(n-2) byte dest buffer. Source buffer has a pad byte, an 8-bit
 * initial value, followed by n-2 bytes comprising 2*(n-2) 4-bit
 * encoded samples.                                                 */

void DUnpack(source, n, dest)
    BYTE source[], dest[];
    LONG n;
    {
      D1Unpack(source + 2, n - 2, dest, source[1]);
    }


8SVX.CHAN.PAN

                     SMUS.CHAN and SMUS.PAN Chunks
            Stereo imaging in the "8SVX" IFF 8-bit Sample Voice 
            ---------------------------------------------------
                 Registered by David Jones, Gold Disk Inc.

There are two ways to create stereo imaging when playing back a digitized
sound. The first relies on the original sound being created with a stereo
sampler: two different samples are digitized simultaneously, using right and
left inputs. To play back this type of sample while maintaining the
stereo imaging, both channels must be set to the same volume. The second type
of stereo sound plays the identical information on two different channels at
different volumes. This gives the sample an absolute position in the stereo
field. Unfortunately, there are currently a number of methods for doing this
currently implemented on the Amiga, none truly adhering to any type of
standard. What I have tried to to is provide a way of doing this
consistently, while retaining compatibility with existing (non-standard)
systems. Introduced below are two optional data chunks, CHAN and PAN. CHAN
deals with sounds sampled in stereo, and PAN with samples given stereo
characteristics after the fact.


Optional Data Chunk CHAN
________________________

This chunk is already written by the software for a popular stereo sampler. To
maintain the ability read these samples, its implementation here is 
therefore limited to maintain compatability.

The optional data chunk CHAN gives the information neccessary to play a
sample on a specified channel, or combination of channels. This chunk
would be useful for programs employing stereo recording or playback of sampled
sounds. 
        
        #define RIGHT           4L
        #define LEFT            2L
        #define STEREO          6L
        
        #define ID_CHAN MakeID('C','H','A','N')
        
        typedef sampletype LONG;
        
If "sampletype" is RIGHT, the program reading the sample knows that it was
originally intended to play on a channel routed to the right speaker,
(channels 1 and 2 on the Amiga). If "sampletype" is LEFT, the left speaker
was intended (Amiga channels 0 and 3). It is left to the discretion of the
programmer to decide whether or not to play a sample when a channel on the
side designated by "sampletype" cannot be allocated. 

If "sampletype" is STEREO, then the sample requires a pair of channels routed
to both speakers (Amiga pairs [0,1] and [2,3]). The BODY chunk for stereo
pairs contains both left and right information. To adhere to existing
conventions, sampling software should write first the LEFT information,
followed by the RIGHT. The LEFT and RIGHT information should be equal in
length.

Again, it is left to the programmer to decide what to do if a channel for
a stereo pair can't be allocated; wether to play the available channel only,
or to allocate another channels routed to the wrong speaker. 



Optional Data Chunk PAN
_______________________

The optional data chunk PAN provides the neccessary information to create a
stereo sound using a single array of data. It is neccessary to replay the 
sample simultaneously on two channels, at different volumes. 

        #define ID_PAN MakeID('P','A','N',' ')
        
        typedef sposition Fixed; /* 0 <= sposition <= Unity */
                                                         /* Unity is elsewhere #defined as 10000L, and
                                                          * refers to the maximum possible volume.
                                                          * /
        
        /* Please note that 'Fixed' (elsewhere #defined as LONG) is used to 
         * allow for compatabilty between audio hardware of different resolutions.
         */
         
The 'sposition' variable describes a position in the stereo field. The
numbers of discrete stereo positions available is equal to 1/2 the number of
discrete volumes for a single channel.

The sample must be played on both the right and left channels. The overall
volume of the sample is determined by the "volume" field in the Voice8Header
structure in the VHDR chunk. 

The left channel volume = overall volume / (Unity / sposition). 
 "  right   "       "   = overall volume - left channel volume.
 
For example:
        If sposition = Unity, the sample is panned all the way to the left.
        If sposition = 0, the sample is panned all the way to the right.
        If sposition = Unity/2, the sample is centered in the stereo field.


8SVX.SEQN.FADE

                          SEQN and FADE Chunks


       Multiple Loop Sequencing in the "8SVX" IFF 8-bit Sample Voice 
            ---------------------------------------------------
           Registered by Peter Norman, RamScan Software Pty Ltd.




Sound samples are notorious for demanding huge amounts of memory. 

While earlier uses of digital sound on the Amiga were mainly in the form of
short looping waveforms for use as musical instruments, many people today 
wish to record several seconds (even minutes) of sound. This of course eats 
memory.

Assuming that quite often the content of these recordings is music, and that
quite often music contains several passages which repeat at given times,
"verse1 .. chorus ..  verse2 .. chorus .." etc, a useful extention has been
added to the 8SVX list of optional data chunks. It's purpose is to conserve
memory by having the computer repeat sections rather than having several
instances of a similar sound or musical passage taking up valuable sample 
space.


The "SEQN" chunk has been created to define "Multiple" loops or sections
within a single octave 8SVX MONO or STEREO waveform. 

It is intended that a sampled sound player program which supports this chunk
will play sections of the waveform sequentially in an order that the SEQN
chunk specifies. This means for example, if an identical chorus 
repeats throughout a recording, rather than have this chorus stored several
times along the waveform, it is only necessary to have one copy of the chorus
stored in the waveform.

A "SEQeNce" of definitions can then be set up to have the computer loop back
and repeat the chorus at the required time. The remaining choruses
stored in the waveform will no longer be necessary and can be removed.


eg. If we had a recording of the following example, we would find that 
there are several parts which simply repeat. Substantial savings can be made
by having the computer repeat sections rather than have them stored in memory.



EXAMPLE

"Haaaallelujah....Haaaallelujah...Hallelujah..Hallelujah..Halleeeelujaaaah."



Applying a sequence to the above recording would look as follows.


Haaaallelujah....Haaaallelujah...Hallelujah..Hallelujah..Halleeeelujaaaah.
[     Loop1     ]
[     Loop2     ]
                                 [  Loop3   ]
                                 [  Loop4   ]
                                                         [     Loop5     ]

                [   Dead Space   ]          [ Dead Space ]


The DEAD SPACE can be removed. With careful editing of the multiple loop
positions, the passage can be made to sound exactly the same as the original
with far less memory required.



Chunk Definitions...



Optional Data Chunk SEQN
________________________

The optional data chunk SEQN gives the information necessary to play a
sample in a sequence of defined blocks. To have a segment repeat twice,
the definition occurs twice in the list.
        
This list consists of pairs of ULONG "loop start" and "end" definitions which
are offsets from the start of the waveform. The locations or values must be
LONGWORD aligned (divisable by 4).


To determine how many loop definitions in a given file, simply divide the
SEQN chunk size by 8. 

eg if chunk size == 40 ... number of loops  = (40 / 8) .. equals 5 loops.


The raw data in a file might look like this...



'S-E-Q-N' [ size ] [     Loop 1    ] [     Loop 2    ] [     Loop 3    ] 

 5345514E 00000028 00000000 00000C00 00000000 00000C00 00000C08 00002000
             ^
             ^     'Haaaallelujah..' 'Haaaallelujah..'   'Hallelujah..'
             ^
             ^
             40 bytes decimal / 8 = 5 loop or segments



       [     Loop 4    ] [    Loop 5     ]'B-O-D-Y'   Size     Data

       00000C08 00002000 00002008 00003000 424F4459 000BE974 010101010101010
 
        'Hallelujah..'  'Halleeeelujah..'





In a waveform containing SEQN chunks, the oneShotHiSamples should be set to 0
and the repeatHiSamples should equal the BODY length (divided by 2 if STEREO).

Remember the locations of the start and end of each segment or loop should
be LONGWORD aligned.


If the waveform is Stereo, treat the values and locations in exactly the same
way. In other words, if a loop starts at location 400 within a Stereo
waveform, you start the sound at the 400th byte position in the left data
and the 400th byte position in the right data simultaneously.



        #define ID_SEQN MakeID('S','E','Q','N')
        
        



Optional Data Chunk FADE
_______________________


The FADE chunk defines at what loop number the sound should begin to 
fade away to silence. It is possible to finish a sample of music in much
the same way as commercial music does today. A FADE chunk consists of
one ULONG value which has a number in it. This number corresponds to the 
loop number at which the fade should begin.

eg. You may have a waveform containing 50 loops. A FADE definition of 45 will
specify that once loop 45 is reached, fading to zero volume should begin.
The rate at which this fade takes place is determined by the length of time
left to play. The playing software should do a calculation based on the
following...


Length of all remaining sequences including current sequence (in bytes)

divided by 

the current playback rate in samples per second

= time remaining.



Begin stepping the volume down at a rate which will hit zero volume just as
the waveform finishes.
 






The raw data in a file may look like this.




 'F-A-D-E'  [ Size ]   Loop No.  'B-O-D-Y'   Size   Data..

  46414445  00000004   0000002D   424F4459 000BE974 01010101 01010101 etc etc
                          ^
                          Start fading when loop number 45 is reached.




        #define ID_FADE MakeID('F','A','D','E')



Although order shouldn't make much difference, it is a general rule of thumb
that SEQN should come before FADE and FADE should be last before the BODY.

Stereo waveforms would have CHAN,SEQN,FADE,BODY in that order.