A long WAV will not open? Check its container before converting

A recording arrives with a .wav filename, but the recipient's editor rejects it or reports an unexpected duration. Keep the original and the exact error. Before making another export, record the file's byte size, the creating application and the receiving application with their versions.
Give the next comparison a specific question: can this recipient open the container and preserve the material required for the handoff? A shorter filename or a larger destination drive does not answer that question.
Keep storage planning and import acceptance separate
Use the PCM storage worksheet when estimating audio payload. For an existing delivery, record its actual size as well. Keep the container and the sample encoding as separate fields: a format name shown in an export dialog is an intention to verify against the resulting file.
The blank container handoff card records the original, header observation, receiver version and actual import result. Begin with NOT CHECKED. If the sender has a delivery specification, attach its exact format wording rather than reducing it to “send a WAV”.
Use the right edition of the format reference
The current ITU-R BS.2088-2 record identifies the November 2025 recommendation as in force. Its specification describes BW64, including 64-bit size information and metadata provisions. The .wav extension is retained, so the suffix alone cannot establish the particular container.
The recommendation explains the size limit arising from conventional RIFF/WAVE's 32-bit addressing and the BW64 approach using a ds64 chunk. Keep that structural issue separate from available disk capacity. A file-format limit and free storage need different evidence.
For legacy RF64 material, EBU Tech 3306's publication history matters. EBU says its specification has been superseded by the ITU recommendation. The July 2009 version remains useful for interpreting an RF64 header, with that historical scope made explicit.

Make a bounded, read-only header observation
If Python 3 is already available, run the following command in Terminal to read at most twelve bytes. Replace the quoted placeholder with the path to a file you intend to inspect. It opens that file in read-only binary mode and prints two byte sequences.
python3 -c '
import sys
with open(sys.argv[1], "rb") as source:
header = source.read(12)
print("container tag:", repr(header[:4]))
print("form tag:", repr(header[8:12]))
' "./your-recording.wav"If Python is unavailable, record that limitation and ask the sender for a header report from their existing inspection tool. There is no need to install software just to complete the card.
| Observed container tag | Form tag | Initial interpretation |
|---|---|---|
| RIFF | WAVE | The header identifies a conventional RIFF/WAVE form |
| RF64 | WAVE | The header identifies the legacy RF64 form |
| BW64 | WAVE | The header identifies the BW64 form |
| Another value, or too few bytes | Any | Preserve the output and investigate the actual file with the sender |
Record this as a header observation. The command does not inspect the remaining chunks, verify audio, establish metadata completeness or test an editor. A truncated or incorrectly constructed file can still begin with familiar tags.
Check the recipient before choosing another export
Consult the receiving tool's documentation for its actual version and the container required by the delivery specification. Keep any unsupported format explicit. If a different delivery is agreed, export a separately named copy and preserve the source and the earlier result.
Open the actual delivered copy in the recipient workflow. Check duration, required channels, a recognisable passage and any metadata the recipient depends on. Record those outcomes separately; a completed import dialog supplies only part of the acceptance record.
If splitting or converting is proposed, agree on boundaries and required metadata first. Keep the new filenames and revisions with the card so the recipient can identify which result was inspected. Renaming an extension leaves the underlying bytes unchanged.
What the command check established
In the documented 4 November 2026 check, this read-only command used Python 3.13.1 and existing original synthetic fixtures. That was a bounded synthetic command check, not a current recipient test. A small silent WAVE fixture returned RIFF and WAVE. A plain-text fixture also produced output and exited successfully, demonstrating why a successful command exit is not a file-validation result. An absent path raised FileNotFoundError. Both existing input hashes were unchanged.
No RF64 or BW64 recording was created, decoded, played or imported into an editor for this guide. The card is blank. Recipient compatibility and a completed audio handoff still require the actual file and receiving workflow.
The cited documentation was rechecked on 13 November 2026.