Before downmixing an audio file, check its streams and channel layout

A file arrives with “six channels” in the handoff note. Before making a stereo copy, establish what those channels are meant to contain. A channel count does not tell you whether they represent speaker positions, separate microphones or another agreed arrangement.

Start with a read-only inspection of a working copy. Keep three observations separate: the audio streams reported in the file, the channels within each stream and the content you actually hear. This guide stops before choosing a downmix.

Inspect all audio streams

If you already have FFprobe installed, run this command in Terminal, replacing the quoted path with your local file. Keep the path quoted when it contains spaces.

ffprobe -v error -select_streams a \
  -show_entries stream=index,codec_name,sample_rate,channels,channel_layout \
  -of json -i "./your-audio-file.wav"

The FFprobe 8.0.1 documentation describes stream selection, selected output entries and JSON output. Here, a selects audio streams rather than only the first audio stream. The command prints the requested information; it does not contain an audio conversion or output-media instruction.

Record the FFprobe version with the report. If the command reports an error, keep the error and stop before using its output to make a conversion decision. An unreadable file and a valid file with no selected audio streams are different findings.

Want small practice inputs before inspecting your own recording? The silent FFprobe examples contain five original generated media files and one deliberately invalid text file, with reference JSON, a README and input checksums. Our 3 November 2026 check used FFprobe 8.0.1 and left the input hashes unchanged. These silent files demonstrate reported fields and inspection failure. They cannot establish audible content, real speaker order or downmix quality. FFmpeg software is not included.

Count streams and channels separately

Each object in the streams array describes a selected stream. Its index identifies that stream in this file. Its channels value describes the channel count within that stream.

For example, two one-channel streams are not the same structure as one two-channel stream. Ask which stream the recipient needs and whether separate sources should remain separate. Do not quietly collapse them because both descriptions involve the number two.

MediaInfo's field reference, labelled for version 23.10, likewise distinguishes channel count from channel layout and channel positions. That reference is useful for interpreting the concepts if you use another inspector; its field names are not FFprobe command options.

An absent layout is an unresolved observation

In our small local check with FFprobe 8.0.1, a generated silent six-channel WAV reported channels: 6 without a channel_layout field. A separately generated silent WAV with a declared 5.1 layout reported six channels and channel_layout: "5.1".

That is a result for those synthetic fixtures, not a guarantee about every WAV or probe version. The FFprobe documentation also notes that JSON output can omit invalid or non-applicable fields. If your report lacks a layout, record “not reported”. Do not replace it with a guessed speaker arrangement.

A reported layout is still not a listening result. Ask the sender for the intended channel order and a reference passage that identifies each source. Keep “reported layout”, “sender's intended order” and “heard content” in separate columns of the blank stream and channel review ledger.

Agree on the target before making a copy

Write down what the recipient needs: which stream, which sources, whether a stereo listening reference is enough and whether the original multichannel material must also be retained. This avoids turning a technical inspection into an unapproved editorial decision.

When the intended order is unclear, return the report and the specific question to the sender. Do not relabel the only source file to make an inspector look tidy. A separately named listening copy can be reviewed once the required content is agreed.

If you later create that copy, check the result in the intended player and listen for every required source. A successful conversion command or a two-channel label does not establish that all the intended content survived. The Audacity stereo and mono guide covers a separate track-editing decision; it is not a universal downmix recipe.

What we actually checked

On 3 November 2026, we ran the displayed inspection options using FFprobe 8.0.1 against five short generated silent media files: one-channel, two-channel and six-channel WAVs without declared layouts, a WAV with a declared 5.1 layout, and a container holding two mono audio streams. We also checked an invalid text input, which returned a nonzero exit code. Hashes before and after inspection matched for all six inputs.

No user recording was opened, uploaded, played or downmixed. The check validates this narrow command example on these fixtures. It does not validate their audible content, a real handoff, a speaker setup or a downmix's quality.