Poly WAV vs mono WAV: which one should you hand to Resolve or Premiere?

Every field recorder asks the same question in its setup menu: poly or mono. On set the choice looks harmless. In post it decides whether your editor spends the morning cutting picture or untangling multichannel clips.

The two formats, side by side

• Poly WAV: one file per take containing every channel interleaved, with one timecode stamp and one metadata block.
• Mono WAV: one file per channel, named TAKE01_1.wav, TAKE01_2.wav and so on, sharing the same timecode.
• Storage is identical. The audio data is the same; only the packaging differs.
• Poly is tidier at wrap. Mono is faster to route once the files hit a timeline.

Metadata: poly wins on set

A poly WAV carries scene, take, note and track names in its iXML and bext chunks, all in one place. Sound reports match the file list one to one, and nothing gets separated when someone copies a folder in a hurry. Mono sets repeat that metadata across every file, which works but multiplies the number of objects that can go missing.

Track handling: mono wins in the edit

An editor rarely wants eight channels glued together. They want the boom on one track, the lead lav on another, and the ability to mute the plant mic that picked up the fridge. Mono stems give that immediately. A poly clip has to be interpreted first, and how well that goes depends entirely on your NLE.

DaVinci Resolve

Resolve handles poly WAVs well. In the media pool you can right click a clip, open Clip Attributes and set the audio to multiple mono tracks, and Fairlight will expose each channel as its own linked source. Track names written by the recorder show up, which makes boom and lav obvious without auditioning.

• Poly is workable in Resolve, especially if you finish audio in Fairlight on the same project.
• Set Clip Attributes before syncing, not after, or you will redo the sync map.
• If you round trip to Pro Tools via AAF, mono stems export cleaner and avoid channel order surprises.
• For a documentary with hundreds of takes, mono stems still cut faster because dragging one track needs no per clip setup.

Adobe Premiere Pro

Premiere is the stricter of the two. A multichannel WAV comes in as a single clip whose channel mapping is governed by the project's default audio track settings, and changing that after the fact means modifying the clip in the Interpret Footage dialogue, one clip at a time. Multicam and merged clips add another layer where channels quietly collapse to stereo.

• Give Premiere mono stems whenever you can. It removes an entire category of routing bugs.
• If you must ingest poly, set Modify > Audio Channels to Mono and choose the right channel count before building sequences.
• Merged clips with mono stems keep every microphone on its own timeline track, which is what dialogue editing needs.
• Sending an OMF or AAF to a mixer is far more predictable from mono based sequences.

The practical recommendation

Record poly on set. It keeps takes intact, keeps metadata in one place, and it is what your recorder does best. Then split to named mono stems at the offload, before the assistant editor imports anything. Keep the original poly files in the camera raw folder as your archive, and hand the mono set to the edit.

That single step suits both NLEs: Resolve gets clean per microphone tracks without touching Clip Attributes, and Premiere never has to guess a channel map. Our poly WAV splitter does it in the browser, reads the track names your recorder wrote, keeps the original sample rate and bit depth, and never uploads a file.