Finished audio or still a mastering task?
Measure first. If speech, peaks or loudness need correction, finish the production workflow before calculating final enclosure metadata.
Elysia Tools
Navigation
Workflow Playbook
Check one finished podcast episode against its RSS entry, verify final-file size, type and duration, and separately test public media access and player behavior before publication.
Hubs
This workflow is for a publisher who has finished editing one episode. Production cleanup and mastering belong in the related podcast and loudness workflows. Keep the final program, feed snapshot and target item together. Measure streams, codec, duration, loudness and peak headroom against the agreed policy; the tools do not decide whether the story is ready or establish current platform acceptance.
Tags and embedded artwork can change file size without changing audible duration. Finish those edits before recording enclosure length. Preserve the source format when only metadata should change, then inspect the resulting file again; choosing another format may transcode audio. Artwork embedded in a file is not the same asset as feed-level show artwork. Keep their roles explicit and do not add a cover merely to complete a checklist.
Format a feed copy for review rather than blindly replacing production XML. Inspect the target GUID, date with timezone and media address; do not assign a new identity simply because a filename changed. URL syntax checks do not prove a public download works. Confirm rights and remove secrets before sharing diagnostic material.
Run the enclosure checker with both the feed and the frozen audio. Verify the row it matched. The implementation can pair by filename, identical byte size or similar duration, so a match is a candidate association, not proof of identity. Two episodes of similar length can be confused. Unmatched entries do not receive a cross-file check; keep them explicitly unverified.
Compare the full-file byte count, actual container and declared type, and measured versus declared duration. Inspect the underlying file format when its extension is misleading rather than trusting extension-based MIME expectations. Duplicate findings apply to the supplied snapshot, not every past version of the feed. Resolve failures and explain accepted warnings; a platform profile is not a live submission test.
Use the authorized media URL for response inspection, including redirects and the final destination. A successful HEAD request or plausible Content-Length is not a complete-download test. Download the actual served episode, check its size and content against the final render and test it in the intended player, including seeking where required. If byte-range responses are tested, their segment length is not the enclosure's full-file length.
Check without publisher login cookies so a private session does not hide an access failure. Cached media may still be an older render even when the URL is unchanged. Record the tested feed revision, media address, time, player and unresolved issues. The HTTP analyzer is one observation from its network location, not proof that all listeners or platforms can access the file. Feed aggregation belongs in the digest workflow; this result is a scoped episode publication check, not automatic upload, scheduling or platform approval.
Workflow playbook
Probe container, codec, streams and duration, measure loudness and true peak, and compare with the agreed delivery policy without treating technical readings as editorial approval.
Edit only required tags and embed artwork where supported and needed; preserve the intended format, reopen the result and freeze the final bytes before declaring feed size.
Format a copy for inspection, review GUID, date and enclosure fields, and check URL structure; a valid-looking address does not demonstrate reachability.
Supply the feed and final file, choose the intended profile, inspect the exact pairing and review byte count, type, duration and feed findings; unmatched or ambiguous items require manual verification.
Measure first. If speech, peaks or loudness need correction, finish the production workflow before calculating final enclosure metadata.
Inspect the matched item and filename explicitly. Matching can fall back to equal byte count or close duration; neither proves episode identity.
A local pass does not fetch the enclosure. Test the served address and player separately; built-in platform profiles are checks, not approval guarantees.
Inspect the actual media response and final redirect destination, independently download the delivered file and test playback and seeking; record timestamps and exceptions before handing off.