Professional audio workflows often involve files that hold several channels inside a single WAV. For someone receiving location sound or field recordings, the file may look like one item in the file system while actually containing several independent audio channels.
Understanding that structure makes it easier to inspect, edit, split, map or deliver the recording correctly.
WHAT IS A MULTICHANNEL WAV FILE?
WAV is a container format that can store audio with different channel counts. A mono file holds one channel, a stereo file holds two, and a multichannel WAV file holds more than two channels within the same file.
HOW ARE MULTIPLE CHANNELS STORED IN ONE FILE?
In an interleaved WAV file, the samples of each channel are stored in alternation within a single file structure: one sample for channel 1, one for channel 2, and so on, before the sequence repeats. The channels share the file, but they remain separate audio streams. They are not mixed together.
Channel count is independent of the other technical properties of the file. A six-channel WAV can use the same sample rate and bit depth as a mono one; changing the rate is a separate operation, covered in sample rate conversion.
WHAT IS A POLYWAV?
PolyWAV is a term commonly used in professional production sound workflows for a WAV or BWF file containing several synchronized audio channels in a single file. On a location recorder, a PolyWAV typically holds the channels recorded during the same take.
The format describes how the channels are packaged, not what they contain. Depending on the recording, the channels may carry a boom microphone, lavalier microphones, a mix track, a plant microphone, an ambience microphone, an isolated microphone or a surround microphone channel.
When each channel needs to be handled as its own file, you can split a PolyWAV into individual mono tracks.
CHANNEL ORDER AND ASSIGNMENT
Channel 1, channel 2 and channel 3 only identify positions in the file. They do not inherently mean left, right, boom, lav, centre or surround. What each position contains depends on how the recording was configured. When channels need to be assigned to different destination positions, this is handled through channel mapping.
Before manipulating the file, it can be important to check the recorder configuration, the embedded metadata, the sound report and the file information. Splitting, remapping or delivering channels without knowing their assignment can easily lead to the wrong microphone ending up in the wrong place.
MULTICHANNEL DOES NOT ALWAYS MEAN SURROUND
A six-channel production sound PolyWAV is not automatically a 5.1 surround recording. Similarly, a multichannel field recording may contain independent microphone signals rather than a defined playback speaker layout.
The file tells you how many channels there are. Their function comes from the recording setup and its documentation.
HOW TO INSPECT A MULTICHANNEL WAV FILE
Before editing or converting a multichannel file, it helps to know its basic properties. Audio editors and dedicated file-inspection tools can display many of these properties.
If you need to check the technical structure of a WAV file before working with it, an audio inspector can help identify properties such as its channel count and audio format. One option is the Audio Inspector — Audio Tool Kit.
WHEN SHOULD YOU SPLIT THE CHANNELS?
Splitting is not always necessary. Many professional audio applications work directly with multichannel files. Separating the channels can still be useful when an application expects separate mono files, when individual microphones need to be handled separately, when a workflow requires one file per channel, or when specific channels need to be delivered independently.
WHEN SHOULD YOU KEEP THE FILE MULTICHANNEL?
Keeping the original structure can be preferable when the application supports the format directly, when channel relationships need to remain together, when the original production sound file should be preserved, or when the file represents an intentional multichannel recording.
Neither approach is universally better. The right choice depends on the recording and the workflow it is entering.