Time Codes Don't Match
Moderator: James Steele
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
-
- Posts: 194
- Joined: Tue Oct 02, 2007 1:27 pm
- Primary DAW OS: MacOS
- Location: Las Vegas, NV
- Contact:
Time Codes Don't Match
Hello!
Working on a music cue for a movie.
Movie time code starts at 00:59:58:00 (black pre-roll). Picture starts at 01:00:00:00.
Sort of confused on "Set Chunk Start Time" vs "Set Movie Start Time." Not sure how to set each so that DP's time code matches the movie's time code. As of now, DP is exactly 1:00:02:00 frames off of the movie's time code.
For example, when the movie is at 1:00:07:20, DP is at 0:00:09:20. FPS is 23.976.
Any step-by-step instructions appreciated.
Aaron
Working on a music cue for a movie.
Movie time code starts at 00:59:58:00 (black pre-roll). Picture starts at 01:00:00:00.
Sort of confused on "Set Chunk Start Time" vs "Set Movie Start Time." Not sure how to set each so that DP's time code matches the movie's time code. As of now, DP is exactly 1:00:02:00 frames off of the movie's time code.
For example, when the movie is at 1:00:07:20, DP is at 0:00:09:20. FPS is 23.976.
Any step-by-step instructions appreciated.
Aaron
DP 11.31, Mac Studio M2 Ultra, 128GB Memory, Sonoma 14.3.1
- MIDI Life Crisis
- Posts: 26279
- Joined: Wed May 18, 2005 10:01 pm
- Primary DAW OS: MacOS
- Contact:
Re: Time Codes Don't Match
Search forum or manual for "set movie start time.." Be sure you're viewing FRAMES when you set that.
2013 Mac Pro 2TB/32GB RAM
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
Instagram
Facebook
MIDI LIFE CRISIS
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
MIDI LIFE CRISIS
-
- Posts: 194
- Joined: Tue Oct 02, 2007 1:27 pm
- Primary DAW OS: MacOS
- Location: Las Vegas, NV
- Contact:
Re: Time Codes Don't Match
I have read the manual, and generally, it is helpful; however, in this situation I have found it to be not very helpful at all.
Any links to articles or videos that give step-by-step instructions? Or, perhaps someone here could give a step-by-step? I've searched this forum's archives and haven't found anything that I could follow.
Any links to articles or videos that give step-by-step instructions? Or, perhaps someone here could give a step-by-step? I've searched this forum's archives and haven't found anything that I could follow.
DP 11.31, Mac Studio M2 Ultra, 128GB Memory, Sonoma 14.3.1
- MIDI Life Crisis
- Posts: 26279
- Joined: Wed May 18, 2005 10:01 pm
- Primary DAW OS: MacOS
- Contact:
Re: Time Codes Don't Match
Ok. I'll see if I can dig up the instructions.
2013 Mac Pro 2TB/32GB RAM
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
Instagram
Facebook
MIDI LIFE CRISIS
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
MIDI LIFE CRISIS
- MIDI Life Crisis
- Posts: 26279
- Joined: Wed May 18, 2005 10:01 pm
- Primary DAW OS: MacOS
- Contact:
Re: Time Codes Don't Match
Still looking but came across this. Seems it's been a problem for quite a while. This is your thread...
http://www.motunation.com/forum/viewtop ... es#p484617
http://www.motunation.com/forum/viewtop ... es#p484617
2013 Mac Pro 2TB/32GB RAM
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
Instagram
Facebook
MIDI LIFE CRISIS
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
MIDI LIFE CRISIS
- MIDI Life Crisis
- Posts: 26279
- Joined: Wed May 18, 2005 10:01 pm
- Primary DAW OS: MacOS
- Contact:
Re: Time Codes Don't Match
2013 Mac Pro 2TB/32GB RAM
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
Instagram
Facebook
MIDI LIFE CRISIS
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
MIDI LIFE CRISIS
-
- Posts: 194
- Joined: Tue Oct 02, 2007 1:27 pm
- Primary DAW OS: MacOS
- Location: Las Vegas, NV
- Contact:
Re: Time Codes Don't Match
Thanks for the link. I had found that thread when I was searching the archives, but I'm finding it difficult to follow. I've tried several variations where I have questions about his instructions, but nothing works. It's a little hard to follow, unfortunately.
DP 11.31, Mac Studio M2 Ultra, 128GB Memory, Sonoma 14.3.1
- MIDI Life Crisis
- Posts: 26279
- Joined: Wed May 18, 2005 10:01 pm
- Primary DAW OS: MacOS
- Contact:
Re: Time Codes Don't Match
I understand. I found it confusing for the longest time as well. I'll try again.
Your movie starts at 00:59:58:00 with visual code.
Set your DP TIME FORMAT to FRAMES. You can do this temporarily in the transport window, or set it as an AUX time format in prefs.
Set your CHUNK START TIME to 00:59:58:00.
Set you MOVIE START TIME to 00:59:58:00.
Done. Make sure the frame rate for the film matches the frame rate in DP.
In short: The start time of the chunk and the movie need to match to get the visual time code to match DP's displayed code.
To create a sequence that starts at a different part of the film (such as a later cue) AGAIN: BE SURE YOU ARE USING FRAMES (not real time or measures) in DP with the start times set as above. Then scroll to the segment you want to score next. Note the start time and enter it as the CHUNK START TIME. That is assuming you are using the same movie in all sequences and are using chunks for cues. The new sequence should start where you want and the sync should match.
Tip: set the start time to 2 seconds earlier if you want a pre-roll before your note start.
If you decide to use different projects per cue (a waste of time, IMO) then you have to set the start times as described above.
Again, BE SURE YOU ARE USING FRAMES!!!! when you set the start times. Then you can switch to real time or measures, etc. if you need to.
When you bounce, use BROADCAST WAVE to preserve and timestamp the movie time to match the film time. Then when your editor drops the file into his system, it should line up without a problem.
Note that DP isn't as reliable exporting OMF to Pro Tools 10 and AAF would be a much more reliable choice if your editor can accept that. Otherwise, just the BWAVE files should work in a less complex project if you are only supplying music stems and not a lot of dialogue and SFX.
Let me know if that works.
Your movie starts at 00:59:58:00 with visual code.
Set your DP TIME FORMAT to FRAMES. You can do this temporarily in the transport window, or set it as an AUX time format in prefs.
Set your CHUNK START TIME to 00:59:58:00.
Set you MOVIE START TIME to 00:59:58:00.
Done. Make sure the frame rate for the film matches the frame rate in DP.
In short: The start time of the chunk and the movie need to match to get the visual time code to match DP's displayed code.
To create a sequence that starts at a different part of the film (such as a later cue) AGAIN: BE SURE YOU ARE USING FRAMES (not real time or measures) in DP with the start times set as above. Then scroll to the segment you want to score next. Note the start time and enter it as the CHUNK START TIME. That is assuming you are using the same movie in all sequences and are using chunks for cues. The new sequence should start where you want and the sync should match.
Tip: set the start time to 2 seconds earlier if you want a pre-roll before your note start.
If you decide to use different projects per cue (a waste of time, IMO) then you have to set the start times as described above.
Again, BE SURE YOU ARE USING FRAMES!!!! when you set the start times. Then you can switch to real time or measures, etc. if you need to.
When you bounce, use BROADCAST WAVE to preserve and timestamp the movie time to match the film time. Then when your editor drops the file into his system, it should line up without a problem.
Note that DP isn't as reliable exporting OMF to Pro Tools 10 and AAF would be a much more reliable choice if your editor can accept that. Otherwise, just the BWAVE files should work in a less complex project if you are only supplying music stems and not a lot of dialogue and SFX.
Let me know if that works.
2013 Mac Pro 2TB/32GB RAM
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
Instagram
Facebook
MIDI LIFE CRISIS
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
MIDI LIFE CRISIS
-
- Posts: 194
- Joined: Tue Oct 02, 2007 1:27 pm
- Primary DAW OS: MacOS
- Location: Las Vegas, NV
- Contact:
Re: Time Codes Don't Match
VERY easy to follow. Thank you!
And, it works perfectly.
Thanks again for taking the time to explain this so easily. I now understand it very clearly.
Woo!
Aaron
And, it works perfectly.
Thanks again for taking the time to explain this so easily. I now understand it very clearly.
Woo!
Aaron
DP 11.31, Mac Studio M2 Ultra, 128GB Memory, Sonoma 14.3.1
- MIDI Life Crisis
- Posts: 26279
- Joined: Wed May 18, 2005 10:01 pm
- Primary DAW OS: MacOS
- Contact:
Re: Time Codes Don't Match
Good. When I forget now you can tell ME how to do it. It's really very simple, but I think when we start to think "I have to do all sorts of math to get this right" the simplicity of DP is lost.
Now go get 'em tiger!

Now go get 'em tiger!

2013 Mac Pro 2TB/32GB RAM
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
Instagram
Facebook
MIDI LIFE CRISIS
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
MIDI LIFE CRISIS
-
- Posts: 205
- Joined: Sat May 23, 2015 7:38 pm
- Primary DAW OS: Windows
- Location: Denver, Colorado
Re: Time Codes Don't Match
I'm having an issue where the video has about 2 frames delay at the start. In other words, film code holds 00:00:00:00 while DP counter counts to 00:00:00:02. So the entire film is behind DP's counter for 2 frames.
I don't think there's a way to fix this without asking the director to resubmit. Any suggestions?
I don't think there's a way to fix this without asking the director to resubmit. Any suggestions?
DP9.5 64bit, Windows 10 Pro 64bit, UA Apollo Quad FireWire interface, Desktop: Intel i7 5820K at 4.0ghz, MSI X99A Gaming 7 mobo, 48gb RAM (DDR4 at 2133 mhz), MSI GTX 960 2GD5T 2GB, 512GB Samsung 950 Pro m.2 SSD (project/system drive). VEP 6
- MIDI Life Crisis
- Posts: 26279
- Joined: Wed May 18, 2005 10:01 pm
- Primary DAW OS: MacOS
- Contact:
Re: Time Codes Don't Match
Move the sequence start time. Be sure it's at zero when the timecode starts, not at the top of the movie file.
2013 Mac Pro 2TB/32GB RAM
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
Instagram
Facebook
MIDI LIFE CRISIS
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
MIDI LIFE CRISIS
-
- Posts: 205
- Joined: Sat May 23, 2015 7:38 pm
- Primary DAW OS: Windows
- Location: Denver, Colorado
Re: Time Codes Don't Match
I basically need to set the sequence chunk time to -2 frames, but you can't do that. If I insert measures and start the sequence earlier, the start frame is always 00. Or am I missing something?
DP9.5 64bit, Windows 10 Pro 64bit, UA Apollo Quad FireWire interface, Desktop: Intel i7 5820K at 4.0ghz, MSI X99A Gaming 7 mobo, 48gb RAM (DDR4 at 2133 mhz), MSI GTX 960 2GD5T 2GB, 512GB Samsung 950 Pro m.2 SSD (project/system drive). VEP 6
- MIDI Life Crisis
- Posts: 26279
- Joined: Wed May 18, 2005 10:01 pm
- Primary DAW OS: MacOS
- Contact:
Re: Time Codes Don't Match
It can be done. Maybe mess with the movie start time? I don't remember exactly how to compensate for that and don't have DP running.
2013 Mac Pro 2TB/32GB RAM
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
Instagram
Facebook
MIDI LIFE CRISIS
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
MIDI LIFE CRISIS
-
- Posts: 205
- Joined: Sat May 23, 2015 7:38 pm
- Primary DAW OS: Windows
- Location: Denver, Colorado
Re: Time Codes Don't Match
Movie start time allows me to start later than the chunk, but I can't seem to get it to start earlier (can't do negative frame start-time from what I can tell). I also feel like there has to be a way, but none of my finagling is doing it!
DP9.5 64bit, Windows 10 Pro 64bit, UA Apollo Quad FireWire interface, Desktop: Intel i7 5820K at 4.0ghz, MSI X99A Gaming 7 mobo, 48gb RAM (DDR4 at 2133 mhz), MSI GTX 960 2GD5T 2GB, 512GB Samsung 950 Pro m.2 SSD (project/system drive). VEP 6