How to Write Metadata and Descriptions for Sync Pitches
Build factual, searchable sync metadata and concise scene-use descriptions that disclose rights, versions, restrictions, and reliable licensing contacts.
The short answer
Build sync metadata from verified release, recording, composition, and rights records, then describe how the track sounds, develops, and might support picture. Include title, artist, version, duration, identifiers, writers, publishers, master owner, control status, contact, vocal and language details, instrumentation, verified tempo, mood, themes, energy arc, ending, alternates, territories, and restrictions. Use defensible tags, separate internal notes from client-facing fields, and never hide samples or inflate one-stop status. A supervisor should be able to find, audition, compare, and route the track confidently.
Three things to know
- 01
Metadata is an operational rights and discovery record, not a bag of promotional keywords.
- 02
Describe observable sound, structure, lyric, and scene function in plain language, using verified technical values and precise control status.
- 03
Keep one authoritative source, map fields to each delivery tool, validate rendered links and downloads, and record every correction.
Sync metadata and description record
Turn verified files, rights, and creative observations into searchable, licensable catalog data.
- 01
Identify the asset
Lock title, artist, catalog ID, version, duration, ISRC, release, explicit status, format, source revision, filename, and artwork.
- 02
Map the rights
Record master, writers, publishers, shares, administrators, control status, territories, samples, approvals, restrictions, and monitored contact.
- 03
Describe the sound
Verify vocal, language, instrumentation, BPM, key, texture, genre, era, themes, energy arc, structure, dialogue space, and ending.
- 04
Write for picture
Summarize immediate sound, emotional development, plausible scene functions, and available versions without hype or placement promises.
- 05
Control the tags
Use defined, defensible vocabulary; separate private, public, creative, and rights fields; and remove contradictions or keyword stuffing.
- 06
Map and verify
Test platform fields, links, downloads, rendering, duplicates, owners, sources, dates, corrections, and recipient-facing accuracy.
What identity and file fields should every track include?
Start with a stable catalog ID, exact track title, primary and featured artists, version label, album or release, duration, release date, explicit status, ISRC where assigned, audio format, sample rate, bit depth, channel layout, filename, artwork reference, and source master revision. Distinguish main, instrumental, clean, TV, underscore, cutdown, edit, mix, and a cappella versions instead of placing them under one ambiguous title. DISCO's current documentation reads common embedded fields including title, artist, album, composer, grouping, genre, year, release date, BPM, ISRC, comments, and lyrics, and supports nested version labels. Treat that as a product example; maintain your own canonical record because platforms expose and interpret fields differently.
What rights and contact fields make a pitch actionable?
List the master owner or authorized representative, writers, writer shares, publishers, publisher shares, administrators, performing-rights affiliations and identifiers when appropriate, composition and master control status, territories, term limits, approval requirements, samples, interpolations, re-records, featured performers, producers, union or guild notes where relevant, and known conflicts. Provide a monitored business contact with name, company, role, email, and response coverage. Use precise labels such as verified one-stop for defined scope, single clearance contact, partial control, or rights review required. Do not place sensitive contracts or personal addresses in public metadata. A missing or exaggerated rights field can make otherwise excellent creative metadata unusable.
How should musical qualities be described accurately?
Record vocal presence, vocal type and language, lyric themes, genre and subgenre, era or production references, key only when verified, BPM only when measured reliably, time feel, major instruments, texture, intensity, energy curve, structural landmarks, dialogue space, edit points, and ending type. Prefer concrete combinations over broad adjectives: 'dry baritone over muted guitar and brushed drums, moving from restrained doubt to a full-band release' communicates more than 'emotional indie anthem.' Separate facts from judgments and allow multiple reviewers to challenge ambiguous tags. Do not assign cultural, regional, religious, identity, or language labels by guesswork. Ask the creator or a qualified reviewer when the context matters.
How can a description explain scene use without becoming hype?
Write two or three sentences in a consistent order: immediate sound and vocal identity, emotional or lyrical development, then plausible picture uses and available versions. Describe the movement across the track, not an imagined placement claim. For example: 'Sparse piano and close female vocal hold a reflective first verse before drums and strings lift the final chorus. The lyric moves from isolation toward cautious resolve, fitting a reconciliation, recovery montage, or quiet brand story. Instrumental, clean, and 30-second edit available.' Avoid best-ever language, guaranteed fit, invented awards, fake previous placements, unsupported celebrity comparisons, and ten incompatible scenes. A useful description narrows the search while leaving room for creative interpretation.
How should tags and controlled vocabulary be managed?
Choose a small vocabulary for genre, mood, energy, theme, vocal, instrumentation, tempo band, era, use case, ending, and version. Define every tag, permitted synonym, exclusion, owner, and review rule. Apply tags that a listener can defend from the audio or approved lyric, not every term that might attract a search. DISCO's current tag documentation illustrates using playlist and track tags to organize assets by categories such as job type, genre, or instrumentals. Keep private operational tags, client-facing tags, and rights restrictions distinct. Audit empty, duplicate, contradictory, overly broad, and stigmatizing labels. Search the catalog after tagging to see whether the returned group actually shares the promised quality.
How should metadata be mapped and quality-checked?
Maintain one authoritative table or catalog record, then map each field to embedded audio metadata, delivery platforms, pitch tools, playlists, spreadsheets, and public pages. Document fields that truncate, merge, reject punctuation, lose line breaks, or cannot carry multiple values. Validate required fields, controlled vocabulary, shares totaling correctly where resolved, contact monitoring, valid links, version-to-file identity, audio duration, duplicate ISRC use, territory, explicit status, and download permissions. Open the recipient-facing link in a clean browser session and download a file to verify the rendered result. DISCO notes that readable embedded metadata varies by audio format, which is another reason not to rely on a single file container as the source of truth.
How should corrections and evidence be governed?
Give each track an owner, approver, source URL or document, last-reviewed date, and change log. When a writer share, publisher, contact, version, lyric, sample, restriction, or descriptive field changes, update the authoritative source first and then every mapped destination. Preserve the old value, reason, requester, evidence, submission date, and verification result. Run periodic audits for stale contacts, catalog acquisitions, administrator changes, broken links, lost files, withdrawn permissions, and inconsistent tags. Do not let a client correction disappear inside an email thread. Metadata carries legal and reputational consequences, so unresolved ownership or authority questions should be marked for review rather than guessed. This workflow is operational guidance, not legal advice.
What supports this metadata workflow?
Practical notes
- DISCO documents readable embedded fields, metadata editing, multiple file formats, nested versions, and track and playlist tags used for catalog organization.
- The U.S. Copyright Office's two-work distinction supports separate master and composition control fields rather than a single vague ownership label.
Source notes
- DISCO Support Center: Adding & Editing Metadata, Managing Track File Formats, Track Nesting, and Playlist & Track Tags, accessed July 18, 2026.
- U.S. Copyright Office: What Musicians Should Know about Copyright, accessed July 18, 2026.
Frequently asked questions
- How long should a sync pitch description be?
- Usually two or three concise sentences are enough to cover sound, emotional arc, plausible scene use, and important available versions.
- Should sync metadata include BPM and musical key?
- Include them when they are measured and useful, but do not guess; tempo changes, half-time interpretation, tuning, and modal harmony can make simple labels misleading.
- Can artists use famous-artist comparisons in sync metadata?
- Use comparisons sparingly, clearly as descriptive references, and only when defensible; observable instrumentation, vocal, era, and energy details are usually more durable.
- Where should sample information appear?
- Record it in the controlled rights metadata and disclose it to the licensing party; do not hide a sample inside private notes or omit it from clearance review.
- Should every available keyword become a tag?
- No. Use a defined vocabulary and only defensible tags, then test whether searches return a coherent group of tracks.