Why podcast hosts still ask for WAV even when Vorbis exists
Ad stitching, loudness normalization, and multi-bitrate ladders often start from linear PCM; some ingest scripts still mis-sniff Ogg MIME types. Queries like podcast host wav requirement, rss audio format, true peak podcast show teams scrambling when the master was only ogg. Decoding to WAV is one hop in delivery, not mastering magic—you still owe true-peak readings and sidecar metadata about beds. Platforms disagree on silence tails, stereo width, and bumper lengths—never one preset for every host. ISRC and composer credits belong in manifests and tags. Huge WAVs belong on signed URLs with expiry, not email.
Stream-ready variant: pass machine ingest and private RSS tests
- Read the latest host spec, highlight rate, depth, peak ceilings, and mandatory silence tails before exporting.
- Measure true peak and integrated loudness after export, log numbers beside chapter markers for dynamic ad slots.
- Publish a private RSS or test episode slot, verify fetchers and ad stitching, then scale—keep OGG and WAV hashes until dashboards go green.
FAQ: stream-ready OGG to WAV
Re-wrap WAV inside FLAC to dodge the same encoder check?
Unlikely—decode the rejection code and diff against their golden sample instead of container hopping.
One WAV for Apple Podcasts and a domestic aggregator without remeasuring?
Replay gain and ad policies diverge; AB both ecosystems or fork masters instead of skipping QA.
Skip composer metadata to speed review?
Incomplete credits breach contracts; delay launch rather than omit ISRC or rights notes.
Hard-zero the last thirty seconds of silence to pass silence-length bots?
Hard cuts can fail other detectors—use documented fades or prescribed room tone tails.
Pad WAV for dynamic ads but skip shownotes updates?
Chapter JSON and shownotes must track new timings or listeners jump into mid-roll awkwardly and file complaints.