Skip to main content

create-an-audio-delivery-package

Create an audio delivery package with correct masters, stems, channel layouts, timing, loudness, metadata, rights, and verification. Use when a finished mix must move to broadcast, platform, archive, localization, or another production.

Source facts

Repository
protosphinx/sphinxstack
Last source activity
July 29, 2026 at 13:55
Detected SKILL.md language
English
Stars
3
Forks
0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
2 files

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
create-an-audio-delivery-package
category
media
description
Create an audio delivery package with correct masters, stems, channel layouts, timing, loudness, metadata, rights, and verification. Use when a finished mix must move to broadcast, platform, archive, localization, or another production.
# create-an-audio-delivery-package Deliver files another operator can identify and verify without guessing. ## When to use - Use for podcasts, video mixes, radio, broadcast, film, games, ads, localization, and archives. - Do not include unlicensed sources, private session material, or credentials in the delivery. ## Procedure 1. Obtain the current specification for formats, sample rate, bit depth, channels, layout, duration, start time, loudness, peaks, naming, metadata, and transfer. 2. Freeze the approved mix version and source session. 3. Export full mix, clean, music and effects, dialogue, voice, ambience, or other required stems from identical timing. 4. Preserve channel order, phase, fades, handles, sync marks, and silence policy. 5. Measure loudness, true peak, duration, head and tail, channel assignment, and file integrity. 6. Populate program, episode, language, version, rights, contact, and checksum metadata as required. 7. Listen to every full mix and spot-check every stem at start, transitions, loud points, and end. 8. Package files with a manifest, spec, known limitations, and secure delivery route. 9. Verify transfer hashes and recipient access. ## Failure plan - If stems do not recombine to the approved mix, correct routing or automation before delivery. - If specification is ambiguous, obtain written clarification rather than choosing a destructive default. ## Done - A delivery package contains approved masters, stems, manifest, metadata, rights, specification, checksums, and limitations - Technical, playback, recombination, timing, channel, loudness, peak, and transfer checks verify the delivered files
View on GitHub