RFC - PEAK chunk
martinp at microsoft.com
Tue Nov 3 13:23:05 EST 1998
Just a random comment:
We need to convert all timestamp and size fields to 64-bit numbers. A
32-bit numBytes field doesn't get you very far with 8-channel, 96 kHz,
There is a proposal within MS for a RIFF64 chunk that would solve this (I
believe), with the obvious negative implication that yesterday's SW would
not understand that chunk. I'll see if I can find the proposal and send it
From: bakker35 at euronet.NL [mailto:bakker35 at euronet.NL]
Sent: Tuesday, October 27, 1998 1:05 PM
To: Multiple recipients of list
Subject: Re: RFC - PEAK chunk
>I think that we could make a region chunk which was a wrapper for two
>chunks and a peak chunk. So:
> MarkerChunk start;
> MarkerChunk end;
> PeakChunk peak;
> Non-float types could simply ignore the peak chunk. And this uses
>existing Marker specification.
A region would require a time stamp (or more than one) that indictates at
which time it was recorded, or which time it is placed in an editing
If this region struct is supposed to become a chunk there will be two
sorts of marker chunk, those as they are now in the spec, and those
INSIDE a region chunk.
OSType chunkType; // would be something like 'RLst'
long id; // list of id's of region chunks
OSType chunkType; // would be something like 'Regn'
long startMarkerID; // Refers to marker in regular marker chunk
long stopMarkerID; // Refers to marker in regular marker chunk
long peakID; // Refers to peak chunk, so that could do
with an ID no.
long timeStamp; // List of time stamps
The region list chunk can be used for playlists.
More information about the music-dsp