PRACTICAL GUIDE
How to prepare music for video, podcasts and games
Compare six original audio examples, prepare short versions and loops, and check your delivery with a downloadable worksheet.
On this page9 sections
A delivery someone can use
You will prepare three things: music that leaves room for speech, a short version with an ending, and a loop that keeps the beat. Finish with a checklist for reviewing the files and explaining what you are delivering.
You can start without your own song. Listen to the six versions of Short weave, an original HertzKit study at 96 BPM in D minor, using recorded piano, guitar and double bass. No account is needed. To edit your own music, use your usual DAW or editor; this page does not compose or export versions of your files.
Download worksheet · TXTThe worksheet is blank. Fill it in on your device; nothing is submitted or saved automatically.
1. Define the brief before playing
“Music for a video” leaves too many decisions open. Before arranging, ask for a scene, script or reference edit and write down:
- Purpose: opening, background under speech, transition or gameplay area. What should the music do at that moment?
- Timing: exact duration, entries, pauses and ending. When working to picture, also agree on frame rate and sync points.
- Space: where speech, effects or silence will go. Mark the phrases that need to be understood.
- Delivery: versions, format, sample rate, bit depth, channels and deadline. Ask for the destination specifications; one file setting does not suit every use.
Practice brief: a 10-second introduction to a podcast about an instrument workshop. Speech occupies the first 7 seconds; the music resolves before second 10. Also prepare a two-bar background that can repeat. The music needs to support an explanation rather than compete with it.
2. Leave room for the main content
An engaging melody can distract when it occupies the same moment as a spoken phrase. Before reaching for EQ, try removing notes, changing register or saving the musical response for a gap in the speech.
Compare the arrangement
The same harmony, with and without a lead melody. Playback starts at a moderate level. Set your device to a comfortable volume.
Choose a version to play.
Save prepared WAVListen this way: read aloud, “Today we are opening the workshop to show how an idea becomes an instrument.” Repeat the same sentence over each version, at a comfortable level without raising your voice. Which takes less effort? These examples contain no recorded speech. This is an arrangement listening exercise, not an intelligibility measurement.
Try it with your music: duplicate the arrangement, mute the main melody and keep the accompaniment. Listen with the actual voice from the project. If it still competes, first review balance and entry points. A “no lead melody” file can still contain harmonies or figures that get in the way.
The two versions have approximately matched integrated loudness, so level does not make the decision for you. This is a comparison condition, not a delivery target. Use the mix comparison tool with your own files and check what changes when loudness matching is on or off.
3. Give a short version somewhere to land
A 10-second version is not always the first ten seconds of the long one. It needs to introduce the idea and reach an ending in time. Reserve space for the resolution and its natural decay; do not stretch or squeeze the entire piece just to reach a number.
Compare the ending
Two 10-second files: a direct cut and a prepared ending.
Choose a version to play.
Save prepared WAVListen to the ending: the cut keeps the beginning of the long arrangement and stops without resolving. The short version changes the last bar and lets the final chord decay within ten seconds. A fade can soften an edge, but it cannot replace a musical arrival.
Your task: mark the end time in your DAW. Work backwards: place the final chord, hear its decay and decide how much preceding material you need. Play from several seconds before the ending. Then check the exported file duration, not just the project selection.
| Version | Useful for | Check |
|---|---|---|
| Full | Presenting the musical idea | Opening, development, ending and tail |
| Short | An opening or transition with an agreed duration | A musical arrival before the time limit |
| No lead melody | Supporting speech | Whether the accompaniment also leaves room |
| Loop | A gameplay area or wait of variable duration | Beat, seam, ambience and destination playback |
Do not prepare ten versions out of habit. Agree on what the recipient needs. If they request stems, confirm groups, start point, length and effects handling. A percussion or harmony stem is a rendered group, not necessarily each individual project track.
4. Check a loop over several repeats
At 96 BPM, two bars of 4/4 last 5 seconds: 8 beats × 60 ÷ 96. That sets the rhythmic duration, but you still need to check the seam. A cut off the beat changes the cycle; a missing tail can reveal the restart even when the cut is on the bar line.
Compare the seam
Each file plays three times so you can check the seam.
Choose a version to play.
Save prepared WAVListen for three cycles: count “1, 2, 3, 4” and keep the beat. The 4.7-second cut restarts too soon. The 5-second loop keeps both bars and wraps the tail onto the beginning. The pattern should return without asking you for an extra beat.
Your task: choose a section whose harmony and dynamics can return to the start. Export it, import it again and repeat it at least four times without gaps. Listen to attacks, bass and reverb at each join. A short crossfade can prevent a click; a long one can double attacks or disturb the beat.
For a file that loops by itself, you can wrap the tail onto the start. A system with separate intro, loop and outro playback may need different handling: preserve the margins requested by the implementer. A wrapped tail can also be audible on the very first start. Test in the destination player or engine. This example is a continuous audio loop. It does not implement game states, transitions or adaptive music.
Use the timing calculator to check rhythmic durations and the trimmer to inspect a section. Files are not sent to those tools automatically. Download a WAV and load it there if you want to examine it.
5. Listen and measure before exporting
- In context: listen with speech, picture or effects. Then check headphones, a small speaker and mono. If something disappears in mono, review the mix before turning everything up.
- With headroom: check peaks, clipping and level differences between versions. Integrated loudness describes the whole; it does not prove a word is intelligible or an isolated hit is appropriate.
- With the final file: open it outside the DAW. Check channels, duration, beginning and ending. Make sure you did not export an earlier selection or leave a track muted by mistake.
The audio analyzer and mix review help locate things worth listening to. Do not turn a measurement into an automatic correction. A LUFS specification for a finished podcast does not necessarily apply to its isolated background music. Ask for the delivery specification instead of normalizing every piece to a universal number.
These examples download as 16-bit stereo PCM WAV at 44.1 kHz so you can inspect them. This is not a specification for your commission. If the client requests 48 kHz or 24-bit, export that format from the original project. Converting a 16-bit copy to 24-bit does not recover lost detail. Read which audio format to export to distinguish review copies from final deliveries.
6. Deliver files people can identify
Choose a stable piece name and revision number. For example: Workshop_v03_short10s_96bpm_Dm.wav. That is enough if the details are correct; a filename does not need to be a full specification sheet. Use the same revision in the delivery note and record what changed since the previous one.
The worksheet from the start brings together the brief, versions, technical checks and permissions. Record who composed, who performed and what third-party material was used. For stems, say whether they should reconstruct the mix and how shared effects are handled. A playable file does not itself grant a license.
For other people's music or samples, retain the permission and check that it covers the intended use. “Royalty-free” does not mean no conditions or exclusivity. Separating instruments from a song does not authorize reuse. Do not promise freedom from automatic claims: a license and Content ID operation are separate matters.
Final check: someone else should be able to open the folder, identify the right version, play it and know whom to contact without asking what “final_final2” means. Keep the editable project separate from the delivery files.
If you’re sending WAV files, check them against the delivery order and include the manifest with the files. The recipient can use it to verify they received the same files. Keep the worksheet with the brief and permissions alongside them.
Check the WAV files for a delivery →
Examples and permission
Short weave was composed and prepared for this guide. The six audio examples are provided under CC0 1.0. You may download, edit and use them, including commercially. Do not present the recordings as exclusive or claim exclusive rights over the shared material. The composition does not reproduce a reference song.
The instruments come from CC0 banks of acoustic recordings. The provenance note identifies the sources and the treatment of each example. This permission covers these six audio examples; it does not change the terms for the rest of the site.
Download provenance and permission · TXTReferences for specific details
The explanation and exercises are written by HertzKit. These external sources document specific points; they do not imply affiliation or endorsement.
- YouTube: how Content ID works — matching and claims.
- Audiokinetic: The Wwise Project Adventure — English PDF, sections on music segments and looping. It explains entries, exits and tails in that system, rather than a universal delivery specification.