Music and Picture Lock: How to Sync Score to Your Edit Without Losing Your Mind

The Score That Arrived After the Cut Changed

A director reaches picture lock on a 78-minute feature. The composer has been working from a rough cut for six weeks, building themes and writing cues. The director sends the locked picture -- and then remembers that the editor trimmed 14 frames from a scene transition on reel three to fix a continuity problem. The change was made after the "locked" file was exported. The composer's cue for that scene now lands 14 frames late against the picture. The climactic music hit that was designed to coincide with the door slamming shut now happens while the door is still in motion.

Fourteen frames. Less than half a second. It takes two days to fix because the composer has to re-export six cues from a session where the tempo map was built against the wrong cut.

The music-to-picture workflow has specific failure points that are entirely avoidable with the right process. This post covers that process from the spotting session through delivery -- including how timecode, tempo mapping, and the Tempo to Frame Sync Calculator prevent the frame-offset disasters that cost time on nearly every first-time composer collaboration.

Industry workflow standards referenced in this post draw from standard practice as documented in the Berklee Online Film Scoring curriculum and the Professional Post Sound workshop series, supplemented by published accounts from composers including the scoring notes associated with Hans Zimmer's media masterclasses and Alexander Desplat's interviews with Film Score Monthly.

How Film Music and Picture Stay in Sync

The synchronization between music and picture rests on a shared temporal reference: timecode. The film's edit has a timecode start point (typically 01:00:00:00 for the program start). Every frame of the locked picture has a unique timecode address. When the composer builds a session in their DAW, they import the locked picture and align the video to the same timecode start point. Every musical cue they write is then anchored to a specific timecode position -- and as long as the picture doesn't change, the music will hit its marks on every playback.

The picture lock rule exists because of this dependency. Once a composer begins working against a cut, any change to the edit -- even a single frame -- breaks the timecode alignment of every cue that follows that change. The cost of a one-frame trim in reel two is that every cue from reel two onward must be re-checked and potentially re-exported, because their timecode start points have shifted.

Tempo mapping is how composers sync musical rhythm to picture events. A cue written in strict 4/4 time at 120 BPM may not naturally land a beat on the exact frame where a character fires a gun or a door closes. Tempo maps allow the composer to vary BPM slightly -- or insert meter changes -- so that musical accents align with picture events without sounding rushed or dragged. The Tempo to Frame Sync Calculator converts between BPM and frames-per-beat at any frame rate, letting you identify whether a given tempo will naturally sync accents to specific frames.

The formula for frames per beat is:

Frames Per Beat = (Frame Rate x 60) / BPM

At 24fps and 120 BPM: (24 x 60) / 120 = 12 frames per beat. A musical accent falls every 12 frames. If the picture event you want to hit falls on frame 14 of the bar, 120 BPM won't place a beat there without a tempo adjustment. At 102.9 BPM: (24 x 60) / 102.9 = 14 frames per beat exactly. The tempo adjustment needed to hit that frame is 17.1 BPM -- audible if made abruptly, but achievable through a gradual tempo ramp across the preceding 8 bars.

The Typical Film Scoring Timeline

The timeline above assumes a low-to-mid-budget production using a dedicated composer. Micro-budget projects often use a library music workflow instead, which compresses this timeline significantly but removes the custom tempo mapping advantage.

Three Real-World Scoring Collaborations

Example 1: Short Drama, Solo Composer with Library Music Supplement

A 22-minute short drama with a budget of $8,000. The director hired a composer friend for $1,500 to write original themes for four key scenes, supplementing with licensed library music for transitional cues from Musicbed.

Workflow: The director sent a ProRes 422 QuickTime export of the locked picture with timecode burned in (visible timecode overlay) plus a separate spotting document listing 11 cue positions, each with a timecode start and end, a note on the scene's emotional intent, and a reference track from the temp cut.

Problem encountered: Two library music cues were edited to picture at the wrong frame rate. The library tracks were in 25fps; the film was shot and edited at 24fps. On playback in the Resolve timeline at 24fps, the library cues drifted by 4% over their duration -- barely noticeable at the start, but a full half-second out by the end of a 2-minute cue.

Resolution: The editor re-imported the library tracks as 25fps audio, letting the NLE perform a sample rate conversion to maintain sync at 24fps playback. A 4-minute fix -- but one that required knowing the frame rate mismatch was the cause.

Example 2: Feature Documentary, Composer Working Remotely

A 74-minute documentary with a Los Angeles-based director and a Berlin-based composer. Score budget: $18,000. Post schedule allowed 8 weeks from picture lock to mix.

Workflow: The director shipped the locked cut as an H.264 QuickTime with embedded timecode (using SMPTE timecode track) at 24fps. The composer imported it into Logic Pro X, set the session to 24fps, and built a tempo map starting at 01:00:00:00. Spotting notes were delivered as a shared Google Doc with columns for timecode in, timecode out, cue name, duration in seconds, and director notes.

Key tool used: The Tempo to Frame Sync Calculator confirmed that the main theme at 84 BPM would place a beat every 17.1 frames at 24fps -- not a clean frame boundary. The composer adjusted to 84.7 BPM, which places a beat every 17.0 frames, allowing the theme to sync cleanly to whole-frame hit points throughout the film.

Outcome: All 23 cues were delivered as 48kHz / 24-bit WAV stems (separate files for strings, piano, and electronics per cue) with timecode start points listed in the file names. The re-recording mixer aligned every stem to picture using the timecode reference without any manual offset adjustments.

Example 3: Music Video, Director as Composer

A 4-minute music video where the director wanted to score additional ambient underscore under two spoken-word sections not covered by the original track. No external composer -- the director used Logic Pro X to write the ambient layers themselves.

Challenge: The director needed the ambient layers to sync to specific visual moments without knowing how to use Logic's tempo map tools.

Solution: Using the Tempo to Frame Sync Calculator, the director identified that their ambient loops at 72 BPM would place a phrase boundary every 2 seconds at 24fps (2.0 seconds = 48 frames / 24fps = exactly 2 seconds -- clean sync at any tempo that divides into 60 evenly). The loops were arranged so phrase boundaries landed on the visual moments the director wanted to hit, without requiring tempo map automation.

Step-by-Step: Managing the Composer Collaboration from Spotting to Delivery

Step 1: Call the spotting session within three days of picture lock. A spotting session is a viewing of the locked picture with the director, composer, and ideally the editor and supervising sound editor present. Walk through the film in real time. The composer takes notes on: where music starts and ends (in and out timecodes), the emotional intent of each cue, any specific sound references or instruments the director has in mind, and any picture events that need a musical hit point.

Step 2: Deliver the locked picture with timecode reference. Export a ProRes 422 or H.264 QuickTime from your NLE with SMPTE timecode embedded in the video track (not burned in as a visible overlay, which degrades the image). Include a text spotting document with each cue's timecode in/out, duration, and intent. Confirm the frame rate in writing -- 23.976fps, 24fps, 25fps, and 29.97fps are all "24fps" colloquially but produce different tempo calculations.

Step 3: Establish a revision protocol before the first cue is delivered. Agree on a maximum number of revisions per cue (typically two), what constitutes a revision versus a new cue, and the turnaround expectation for feedback. Put this in a simple written agreement even between friends -- it protects the relationship when revision requests escalate.

Step 4: Review cue deliveries against the locked picture. When the composer delivers cues for approval, import the audio file into your NLE at the timecode start point listed in the cue sheet. Play it against picture in real time. Check that hit points land on their target frames. If a hit point is more than 2 frames off, flag it for correction before accepting the cue.

Step 5: Confirm stems are delivered in the correct format for the re-recording mixer. Standard stem delivery is: each cue delivered as a separate WAV file, 48kHz / 24-bit, starting at the cue's timecode in point. No fades applied -- the mixer applies fades in the mix session. Stems separated by instrument group (strings, brass, percussion, electronics) where the budget allows for stem mixing. Verify timecode alignment before sending to the mix stage.

Step 6: Provide the mix stage with a cue sheet. The cue sheet lists every music cue in the film: cue number, cue name, timecode in, timecode out, duration, composer, publisher, and whether it's original score or licensed music. This document is required for music licensing, performing rights royalties (ASCAP / BMI / PRS registration), and festival submissions that ask for music clearance documentation.

Pro Tips and Common Mistakes

Pro Tip: Send the composer a "work picture" version of your cut with burned-in timecode during editing, before picture lock, so they can begin sketching themes and confirming session setup. Specify clearly that this is not the locked version and that timecode positions may change. A composer who has already built themes before the spotting session can focus the spotting conversation on placement and intent rather than starting from scratch.

Pro Tip: When evaluating temp music, note the BPM of any temp tracks the composer needs to match in feel. Use the Tempo to Frame Sync Calculator to confirm whether the target BPM will sync cleanly to your key picture events. If the temp track happens to sync well to a specific visual moment, it may be because the editor unconsciously trimmed the cut to align with the music -- which means the original score needs to match that BPM to maintain the same feel.

Pro Tip: For documentaries with extensive archive footage and varying frame rates in the original recordings, deliver a single-frame-rate master to the composer. Archive footage that was originally shot at 25fps but is cut into a 24fps timeline has already been frame-rate converted by your NLE. The composer only needs to know the timeline frame rate -- 24fps -- not the original acquisition frame rate of the archival material.

Common Mistake: Sending a compressed MP4 or H.264 at a low bitrate as the picture reference. If the composer's video decode is stuttering or dropping frames, they cannot accurately identify hit points. Send ProRes 422 or a high-bitrate H.264 (at least 20 Mbps for a 1080p reference). The extra upload size is worth the confidence that the composer's picture reference matches yours frame-for-frame.

Common Mistake: Requesting "revisions" to a delivered cue by sending a new video cut rather than annotated timecode notes. If the composer receives a new cut with changes, they must re-evaluate every hit point in the cue from scratch. Instead, provide feedback as a list: "Bar 12, beat 3 (timecode 01:24:38:14) -- the chord hit needs to move 6 frames earlier to catch the cut to close-up." Timecode-referenced feedback is actionable in minutes; a new cut requires a full re-sync session.

Frequently Asked Questions

What's the difference between a stem and a cue?

A cue is the complete music track for a specific section of the film -- it starts at a defined timecode and ends at a defined timecode. A stem is one isolated instrument group or processing layer within that cue. A single cue might have four stems: strings, brass, rhythm, and solo instrument. Stems give the re-recording mixer the ability to balance the elements of the score against dialogue and sound effects in the final mix without having to go back to the composer for a remix. Not every budget allows for stem delivery -- a single stereo cue file is acceptable for lower-budget projects.

How long before the final mix should I have picture lock?

For a feature film with an original score, picture lock should happen at least 10-12 weeks before the final mix start date to give the composer time to write, record, and deliver. For a short film with a small original score (under 15 minutes of music), 6-8 weeks is workable. Documentary films using library music can compress to 4-6 weeks if the licensing process moves efficiently. The most common mistake is locking picture too late and then either rushing the composer or starting the mix with an incomplete score.

What does "picture lock" actually mean and who declares it?

Picture lock is the moment at which the director and editor declare that no further editorial changes will be made to the timeline. The frame count, frame sequence, and duration of every scene are frozen. In practice, "picture lock" on low-budget productions often means "we're mostly done but might trim a frame here and there" -- which is operationally different from true lock and must be communicated clearly to the composer. True picture lock means the editor has exported a master file, everyone with approval authority has signed off, and no changes will be made for any reason short of a broadcast standards compliance correction.

Can I use temp music from commercial releases as a reference for the composer without licensing it?

Yes, in an internal creative reference context. Sending a commercial track to your composer as a reference for mood, tempo, or instrumentation falls under fair use for private creative communication. What's not permitted is including that commercial track in a deliverable that will be publicly screened or distributed without a sync license. Many directors share temp tracks freely as composer reference and then ensure the final film uses original score or licensed library music. The legal risk begins when the temp music appears in a publicly screened or submitted cut.

What format should the composer deliver final cues in?

The professional standard is: 48kHz / 24-bit WAV files, one file per cue (or one file per stem if stems are required), named with the cue number and timecode start point. File names like "M32_Score_01-24-38-14.wav" communicate the reel, cue number, and timecode start without requiring the mixer to consult the cue sheet for every alignment. Avoid MP3, AAC, or any lossy format for final score delivery -- the re-recording mixer needs full-quality audio for the mix session.

Related Tools

The Tempo to Frame Sync Calculator converts between BPM and frames-per-beat at any standard frame rate, letting composers and directors confirm that a given tempo places accents on clean frame boundaries. For understanding the loudness standards the final mix must meet, LUFS, dBFS, and loudness normalization explains what your re-recording mixer needs to achieve in the final pass. The post on audio delivery standards for film and television lists the platform-specific LUFS targets, channel configurations, and file formats that the delivered score and mix must meet. The Timecode Calculator is useful for converting between timecode formats when working with a composer whose DAW uses a different timecode display.

Conclusion

The music-to-picture workflow is a precision handoff between two creative departments that use fundamentally different tools. The failure points -- frame-rate mismatches, post-lock changes, imprecise hit point feedback, wrong delivery formats -- are all procedural. None of them require creative compromise. They require a clear process, a written spotting document, and a shared understanding that picture lock means exactly that.

This post covers the standard workflow for a single composer and single score. Multi-composer projects, music supervisors working with a library catalogue, and Atmos music delivery each involve additional coordination layers that extend well beyond this framework.

If you've worked with a composer on a scored project: what was the communication tool that worked best for giving hit point feedback -- timecode notes, annotated screenshots, or something else entirely?