RSS enclosures are MP3, so why do distributors still insist on a WAV middle hop from M4A first?
Real-world searches cluster on podcast loudness minus sixteen, true peak WAV, Apple Podcasts loudness guidance, m4a scratch track to mp3, and avoiding stacked lossy exports. The M4A from the host is often just a convenience snapshot; the actual release chain still meters LUFS, true peak, noise gates, and limiter staging inside a DAW before printing the MP3 or AAC subscriber file. Linear WAV gives metering plugins and batch QC scripts a stable front door instead of editing MP3 directly and re-encoding MP3 again. Platforms still care about inter-sample peaks and tail silence even when listeners only download lossy enclosures. Music beds, remote guests, and phone taps remain governed by copyright and privacy rules—WAV does not bypass clearance. Some international storefronts also want screenshots exported from measurement tools on the WAV bus rather than from MP3 waveforms alone.
Release order: M4A scratch → WAV bus → subscription encode with receipts
- Before exporting M4A from the host, freeze session rate and strip unnecessary bus FX, then decode to WAV and immediately read integrated loudness and true peak in a trusted meter.
- Only after meters pass should you print the MP3 or AAC preset, writing version strings and master-bus hashes into metadata fields instead of dumping unchecked peaks on a public CDN prefix.
- Regression-test on phone speakers and a cheap car Bluetooth path, capture rejection screenshots from platforms, and fix issues on the WAV bus rather than endlessly re-baking MP3 alone.