WAV, known for WAVE (Waveform Audio File Format), is a subset of Microsoft's Resource Interchange File Format (RIFF) specification for storing digital audio files. The format doesn't apply any compression to the bitstream and stores the audio recordings with different sampling rates and bitrates.

RIFF (.wav) file format has been around unchanged since the early 1990s and still in common use today. This goes back to a time when CD audio formats were king and RIFF .wav follows the red book convention pretty closely, with the change that the number of channels, bits per sample and samples per second can vary as described in the file header.

As an example file, I have selected TADA.WAV from Windows 10, windowsmediatada.wav. This file is 285,228 bytes, the important part is in the first 44 bytes shown here.

* OFFSET +0 +4 +8 +C
00000000 52494646 245A0400 - 57415645 666D7420 *RIFF$Z.WAVEfmt *
00000010 10000000 01000200 - 44AC0000 10B10200 *....D¬..±.*
00000020 04001000 64617461 - 005A0400 00000000 *..data.Z...*

The first thing to notice is that .wav files and indeed all RIFF files always have 'RIFF' as the first 4 characters. The RIFF header is immediately followed by a WAVE header. RIFF is 'Resource Interface File Format' and in the formatting of file data, RIFF refers to everything as 'chunks'. A chunk is a collection of data that starts with a 4 character code identifier and is follwed by a 32-bit length which is the amount of data in the chunk not including the chunk header. These and all numbers in RIFF are stored little endian formatted. Chunk sizes are usually even, but where it would be odd, the parser looks for the next chunk at the even address following. That is, chunks are padded to an even size.

The RIFF chunk is at the start of the file, and for TADA.wav, the size of the RIFF chunk is 0x245A0400, which is 0x00045a24 in big endian equals 285,220 in decimal. The total file size equals the size of the RIFF chunk plus the 8 bytes that describe that it is a RIFF chunk and for TADA.wav, these add up and match.

• Filesize = 285,228 = 8 + 284,220

Next we dig into the sub-chunks of the RIFF chunk. The RIFF chunk contains other chunks as its data.

Right away we see a 'WAVE' chunk. This is a .WAV file! We knew that from the file extension, but now we really know it.

'WAVE' identifies the start of wave formatted data. This always starts with a 'fmt ' chunk immediately following and yes, that is a space at end. Four character codes always have 4 characters even if the code is only 3 characters. Four character codes do not include line feeds, just the ASCII text (not UNICODE). The format chunk says the format of the data.

The format chunk for this file disected is..

PCM (format '1') is the most common value for format. Backuptrans whatsapp serial key. There are a number of other formats defined primarily for compressed audio and these include Microsoft ADPCM as '2' and ITU G.711 a-law and u-law as 6 and 7. It is entirely possible that a 'valid' wav file can be processed by an audio player who will reply that it has been given an audio format that it does not understand, or that it has been an audio format that no audio devices in the machine know how to process. PCM is the most common audio format in .wav and PCM is 'Pulse Code Modulation' which equals sound pressure levels measured by an analog to digital converter and stored into memory or file with no compression.

After the format chunk is USUALLY the 'DATA' chunk. For TADA.wav, this is true and the DATA chunk starts at offset 0x14 and has the following contents.

Since the data chunk started at offset 0x14 (20 decimal) we can add 20 decimal plus the size of the data chunk header (8) plus 285,184 (data size) to find the start of the first chunk beyond the data. Add those up, get 20 + 8 + 285,184 = 285220 which is the size of the file, so parsing is complete.

Everything inside the DATA chunk is PCM formatted data. In this case, 16 bits per sample, stereo data at 44,100 samples per second. This is CD audio format, stored in a WAV file.

The first PCM sample starts at offset 0x2C and it is 00000000. Notice the sample is the collection of left and right channel and the size here equals the block alignment. By convention, the left channel comes at the lower address which in this example is the 16 bits (2 bytes) at 0x2C equals 0x0000 and the right channel is 2 bytes later at 0x2E and it is also 0x0000. For PCM, 16 bit audio data is stored little endian (intel format).

Once you've purchased a song, all subsequent mixes are unlimited and free. The vows go unbroken mp3 music player download free.

• 16-bit PCM data is 'signed' and zero represents silence (no sound pressure)
• 8 bit PCM data is 'unsigned' and the half way point at 0x80 represents silence (no sound pressure)

With a little bit of programming, you can plot this out and see sound waves, SIN waves even if you look at a file with perfect tone.

RIFF includes additional chunk definitions and if a parser encounters a chunk type it does not understand, it should skip it and continue at the next chunk identified by the chunk length. Some wav file editors include provisions for including copyright text for example. Looking at the TADA.wav shipped with Windows, this is not present.

Joe Nord

How to store metadata in RIFF/WAV files is not straight forward thing:Looks like there are two options (which can be combined):. Store metadata in the RIFF-LIST-INFO chunk. Store metadata in non-standard, but better supported: RIFF/ID3v2.3There is also some inconsistency in storing the ID3v2.3 chunk, some application use 'id3 ', others use 'ID3 '. This is how some applications handle the RIFF/WAV metadata:v2.8Windows 10 Explorer1.3.14Windows 10 Explorer Media PlayerReads RIFF/LIST-INFO✖✖✖✖Writes RIFF/LIST-INFO✔does not write✔does not writeWrites RIFF/ID3v2✔does not write✔does not writeReada RIFF/'id3 '/ID3v2✔✔✔✔Reada RIFF/'ID3 '/ID3v2✔✔✔✔Writes RIFF/ID3v2 chunk-id'ID3 'does not write'id3 'does not writeNotice that I did not found a single application which was able read from the RIFF/INFO tag; although it is apparently written in addition to the ID3v2.3 chunk.Useful stuff:. Utility to visualize RIFF chunks:.