Writing the track is the fun part. Delivering it is where library composers lose their evenings. I have a long publishing relationship with Extreme Music and several hundred songs in their catalog, so I have made a lot of deliveries. The music was never the problem. The stems, the alt mixes, the renaming and the re-exporting were.
Every library has its own spec, and the specs do not agree with each other. One wants ring-outs on every cut. Another wants hard ends. One wants stingers at five seconds, another at seven. One insists every alt line up sample-accurate with the full mix. Another does not care. Scroll through any TAXI forum thread on deliverables and you will find composers hand-rolling Keyboard Maestro macros and tracking it all in spreadsheets. That was me too.
Here is what libraries actually ask for, why they ask for it, and how to make it repeatable.
What libraries ask for, and why
Full mix. The master. Mastered, ready to place, usually 48k/24-bit WAV. This is the version editors audition.
Instrumental. Same mix, no vocals. If your track has a vocal, this is not optional. Editors need to run dialogue over it.
No-melody or no-lead. The mix with the main hook removed, but everything else intact. Editors use this under voiceover when even the instrumental is too busy. It also sells well as a bed.
Drums-only and no-drums. Rhythm-only beds for montage and transitions, and drumless versions when the picture already has a strong rhythm.
Stems. Submixes of the main groups: drums, bass, guitars, keys, synths, vocals, FX. Full length, same start point, so they sum back to the mix. Libraries ask for these so editors (or the library's own in-house team) can rebalance, strip parts, or build custom edits without coming back to you.
Unmastered versions. Some libraries master in-house for consistency across the catalog. They want the full mix and instrumental with no limiter on the stereo out.
Cut-downs. 60, 30 and 15 second edits, sometimes with stingers. These are for advertising and promo use, where the slot length is fixed. Some libraries make these themselves. Many expect you to.
Metadata and naming. Title, composer, PRO info, tempo, key, and a file naming pattern that lets their system ingest files without a human renaming them.
The "why" behind all of it is the same. The library wants to say yes to a music supervisor at 4:55 on a Friday without emailing the composer. Everything they ask for is a version of that.
The checklist
Copy this into your notes and adapt per library. Do the deliverables only after a track is accepted. Making full deliveries for tracks that get passed on is the fastest way to burn a weekend.
Before you start
- Track accepted in writing, with the library's current spec sheet
- Sample rate and bit depth confirmed (usually 48k/24-bit WAV)
- Naming convention confirmed (see below)
- Session cleaned: unused tracks deleted, tracks named, project end past the last tail
- Stem groups decided: which buses, whether FX returns are separate or folded in
Mixes
- Full Mix (mastered)
- Instrumental (mastered)
- Unmastered Full Mix, if requested
- Unmastered Instrumental, if requested
- No-melody / no-lead, if requested
- Drums-only and/or no-drums, if requested
- Any other alt the spec names (TV mix, underscore, etc.)
Stems
- One file per stem group, full length, same start point
- Normalization off
- Master-bus processing bypassed (unless told otherwise)
- Send effects accounted for: included in the group stem or delivered as an FX stem
- Stems sum back to the mix (spot check in a fresh session)
Cuts
- 60 / 30 / 15 second edits, per spec
- Ring-out vs hard end, per spec
- Stingers at the requested length
- Alts line up with the full mix if the library requires it
Documents
- Metadata sheet (title, writer, PRO, IPI, tempo, key, description, keywords)
- Lyric sheet if the track has vocals
- Cue sheet info if the library asks for it up front
Final
- Every file named exactly to the convention
- Every file opened and played for one second (catches silent exports)
- Folder structure matches what the library asked for
- Delivered through the channel they specified
Naming conventions
Most libraries want something close to Title_Mix_Version.wav. Examples:
Midnight_Run_Full_Mix.wav
Midnight_Run_Instrumental.wav
Midnight_Run_No_Lead.wav
Midnight_Run_Full_Mix_60.wav
Midnight_Run_Stem_Drums.wav
Midnight_Run_Stem_Bass.wav
Some want the composer name in front. Some want catalog numbers. Some want no spaces, some want no underscores, some want all caps. The specific pattern does not matter. What matters is that you do not type it by hand for 14 files per track, because you will typo one and the ingest will reject it.
Write the pattern down per library. Then make your export tool produce it, rather than renaming afterward.
How to make it repeatable
The composers who stay sane in this business treat delivery as a system, not a task. Three habits:
1. One template per library. Each library's spec becomes a saved template: which mixes, which stems, what naming, what format. When a track is accepted, you load the template instead of re-reading the spec PDF.
2. Deliver in batches. Do not deliver songs one at a time as they are accepted. Wait until you have three or five, then run them all together. Set it up at the end of the day, let it run, check in the morning.
3. Verify once, at the end. Open the delivery folder and check file count, names and durations against the checklist. Do not verify as you go, because you will stop and fix things and lose the flow.
Where QuickStem fits
I built QuickStem to do the first two habits for me in Logic Pro. It scans the session's mixer and routing and finds the stem structure. I review what it found, keep the groups or combine channels into custom stems, and pick the mix versions: Full Mix, Instrumental, Unmastered Full Mix, Unmastered Instrumental, and any custom mixes like no-lead or no-drums. For the unmastered versions, I choose which master-bus plug-ins to bypass.
The naming convention, the mix list and the settings get saved as a template. One per library. When a track is accepted, I load the template, hit Bounce All, and the delivery lands in STEMS, MIX DELIVERABLES and DOCUMENTS folders. With several tracks accepted, I add them to the batch queue and let it run overnight.
QuickStem drives Logic through Apple's Accessibility API, soloing and bouncing each stem the way I would by hand. It never touches audio files directly, and it verifies the session is unchanged afterward.
QuickStem Plus adds two things that help with the Documents column. Lyric Transcription turns the lead vocal into a lyric sheet I review before approving. Smart Click + Cues builds a stereo file with click on the left and spoken section cues on the right, placed from the session's song structure, which is useful when a library or artist wants to re-record or sync live players.
What QuickStem does not do
QuickStem does not make cut-downs. The 60, 30 and 15 second edits, the stingers, the ring-out decisions, those are still editing work in Logic. I would rather be honest about that than have you find out after you buy. QuickStem handles the full-length mixes and stems; the musical edit itself is yours.
It also does not write your metadata sheet for you, and it does not know your library's spec. You still have to read the PDF once and set up the template. After that, it is one click.
QuickStem runs on macOS 14 or later with Logic Pro 11 or later (verified on Logic Pro 12). It is signed and notarized by Apple, and one licence covers two of your own Macs. Ableton Live and Pro Tools versions are coming.
See the full feature list on the QuickStem product page, or buy QuickStem for $49 or QuickStem Plus for $79 before the opening sale ends November 30. Every purchase includes one free Soundwall master.
FAQ
What stems do music libraries usually want? Drums, bass, guitars, keys or synths, vocals, and FX are the most common groups. Some libraries want finer splits (kick, snare, overheads). Always check the spec, and when in doubt, ask before you export.
Should library stems be mastered or unmastered? Almost always unmastered, with no limiter on the stereo out. Full mixes are often delivered both ways. Stems that have been through a limiter will not sum back to the mix.
What sample rate and bit depth do libraries want? 48k/24-bit WAV is the most common ask for broadcast and sync. Some still take 44.1k. Confirm per library and set your project accordingly before you export, not after.
Does QuickStem create 60/30/15 second cut-downs? No. QuickStem automates full-length mixes, alt mixes and stems from a Logic Pro session. Cuts and stingers are still manual edits you make in Logic.
Author: John Coggins is the founder of Soundwall Studios in Westlake Village, CA, a songwriter and producer with 1,000+ works registered with ASCAP and a long-time Extreme Music writer. He built QuickStem because he was sick of bouncing stems one at a time for library deliveries.