Learn
Seriously Simple Podcasting publishes your episode; it does not measure it. Here is where a loudness check fits into that workflow, and what to check before the feed goes out.
Seriously Simple Podcasting publishes episodes — post type, player, RSS feed. It does not measure the audio. Nothing in it will tell you that this week’s episode is 6 LU quieter than last week’s, so the check has to come from somewhere else, and it has to happen before the feed goes out.
This is not a shortcoming. Publishing and audio measurement are different jobs, and SSP is explicit about which one it does — its plugin description does not mention loudness, LUFS, true peak or normalisation anywhere.
| Step | Handled by SSP |
|---|---|
| Episode post type, show notes, series | Yes |
| Audio player and feed | Yes |
| Hosting and distribution | Yes (via Castos) |
| Is the episode loud enough? | No |
| Will it clip on playback? | No |
| Is there dead air in it? | No |
An RSS feed is a promise that a file is at a URL. Once an episode is out, podcast apps have fetched it and listeners have downloaded it. Replacing the file means re-uploading and waiting for caches to catch up — and anyone who already downloaded it keeps the old version forever.
The failure is rarely dramatic. It is one episode mastered on headphones at a different level, which listeners meet as a volume jump: they reach for the dial, and on the next episode they are already primed to. Consistency across a back catalogue is the thing worth protecting, and it is cheap to protect before publishing.
You can do the same with a desktop meter or a browser tool. The reason to do it in the editor is that a check living on the publishing screen is one nobody forgets — which, for a weekly show, matters more than the measurement itself.
No. Seriously Simple Podcasting handles the podcast post type, the episode player and the RSS feed — publishing, not measurement. Its plugin description does not mention loudness, LUFS, true peak or normalisation, and there is no loudness reading anywhere in the episode screen. Whatever file you attach is what ships.
Between attaching the file and publishing the episode. Once the feed has gone out, listeners and podcast apps have already fetched the file; replacing it afterwards means re-uploading and hoping caches catch up.
Not with AudioLinter. It adds the measurement to the post editor, so the check happens on the same screen where you prepare the episode. The alternative is a desktop meter or a browser tool, which works but takes the check out of the publishing flow.
No, and it is not meant to. SSP owns the feed, the player and the episode data. AudioLinter measures and repairs the audio file. They sit next to each other in the same editor.
Integrated loudness around −16 LUFS, true peak at or below −1 dBTP, and no long silent stretches. Those three catch the problems listeners actually notice: an episode that is too quiet, one that distorts on playback, and dead air someone forgot to trim.
