Time Codes Don't Match

For seeking technical help with Digital Performer and/or plug-ins on MacOS.

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.
PoliticalBonobo
Posts: 205
Joined: Sat May 23, 2015 7:38 pm
Primary DAW OS: Windows
Location: Denver, Colorado

Re: Time Codes Don't Match

Post by PoliticalBonobo »

MIDI Life Crisis wrote: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.
As usual, you're correct :wink: . I didn't have any issues syncing up subsequent reels, just that first one. One trick with the first reel is to start the film very late (like 23:59:59:23 frames) and start the chunk 2 frames (the offset in my case) before that. The counter apparently resets at the 24 hour mark.
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
User avatar
MIDI Life Crisis
Posts: 26254
Joined: Wed May 18, 2005 10:01 pm
Primary DAW OS: MacOS
Contact:

Re: Time Codes Don't Match

Post by MIDI Life Crisis »

I'm not usually right but thanks for the compliment. :) Glad you're back in the saddle. Go get 'em!
2013 Mac Pro 32GB RAM

OSX 10.14.6; DP 10; Track 16; Finale 26, iPad Pro, et al

MIDI LIFE CRISIS
User avatar
bralston
Posts: 585
Joined: Fri Oct 15, 2004 10:01 pm
Primary DAW OS: MacOS
Location: Los Angeles, CA
Contact:

Re: Time Codes Don't Match

Post by bralston »

Make sure DP's sequence timecode flavor is set to be the same as the QT movie (23.98fps, 24fps, 29.97fps, etc...)

then...

1. "Set movie start time" is the timecode on the first frame of the actual QT .mov file you are referencing.

2. "Set chunk start time" is the timecode of the first frame of the specific cue you are working on. This allows you to have a new project file (or new chunk layer) with a "measure 1" for each cue you want to compose.

Youtube video playlist walking one through the process of setting up a reel...and spotting and setting up your individual cues.

https://www.youtube.com/playlist?list=P ... 9-DjQwaV8w
Regards,

Brian Ralston

___________________________________
- MacPro 7,1 3.2 GHz 16-core Intel Xeon W, 384GB 2933MHz DDR4 RAM, OS 10.15.7, 2TB SSD OS drive, 6TB Samsung Pro EVOPlus SSDs via Sonnet 4x4 M.2 PCIe card, Graphics card: AMD Radeon Pro Vega II 32GB, UAD-2 Quad, DP 10.13, DP 11.0,
- 15" MacBook Pro 2.3GHz 8‑core 9th‑generation Intel Core i9 processor, Turbo Boost to 4.8GHz, 32GB 2400MHz DDR4 mem, Radeon Pro Vega 20 w/4GB HBM2 mem, 2TB SSD storage, OS 10.15.7, 2TB SSD, DP 10.13
User avatar
Rick Cornish
Posts: 1127
Joined: Sun Feb 17, 2013 9:07 pm
Primary DAW OS: MacOS
Location: Ely, MN USA
Contact:

Re: Time Codes Don't Match

Post by Rick Cornish »

PoliticalBonobo wrote: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?
Setting the sequence start to -2fr is easy:
23:59:59:28

Think 24 hours in a day—when TC passes the end of the 23rd hour, it rolls back over to zero.
Rick Cornish

DP 11 on M2 Mac Studio (64mB mem. + 2tB int. SSD + two 2tB ext. SSDs, and Mac OS Sonoma). VIs from MOTU, Spectrasonics, NI, UVI, 8dio, Soniccouture, East West, Spitfire, Heavyocity, Vir2, and more; plus Waves 14, Brainworx, iZotope, Wavesfactory, Oeksound, Final Mix, JST, SPL, PSP, UVI, Valhalla DSP, and other FX plugs, Roland A-88, Apogee Quartet, iCON Platform Nano, Genelec 1032a and Westlake BBSM4 monitors, Gibson HR Fusion III. rickcornish.net
PoliticalBonobo
Posts: 205
Joined: Sat May 23, 2015 7:38 pm
Primary DAW OS: Windows
Location: Denver, Colorado

Re: Time Codes Don't Match

Post by PoliticalBonobo »

Rick Cornish wrote:Setting the sequence start to -2fr is easy:
23:59:59:28
Thanks, that's what ended up working for me. Didn't realize the frames eventually looped around again.
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
User avatar
Rick Cornish
Posts: 1127
Joined: Sun Feb 17, 2013 9:07 pm
Primary DAW OS: MacOS
Location: Ely, MN USA
Contact:

Re: Time Codes Don't Match

Post by Rick Cornish »

PoliticalBonobo wrote:Thanks, that's what ended up working for me. Didn't realize the frames eventually looped around again.
I'm occasionally seeing 00:00:00:00 movie start times from young/inexperienced editors who never had to drive a tape-based system, which often puked on TC rollover. This is a good workaround for work-in-progress; but I'd encourage them to use a 01:00:00:00 start time for layback and mastering.
Rick Cornish

DP 11 on M2 Mac Studio (64mB mem. + 2tB int. SSD + two 2tB ext. SSDs, and Mac OS Sonoma). VIs from MOTU, Spectrasonics, NI, UVI, 8dio, Soniccouture, East West, Spitfire, Heavyocity, Vir2, and more; plus Waves 14, Brainworx, iZotope, Wavesfactory, Oeksound, Final Mix, JST, SPL, PSP, UVI, Valhalla DSP, and other FX plugs, Roland A-88, Apogee Quartet, iCON Platform Nano, Genelec 1032a and Westlake BBSM4 monitors, Gibson HR Fusion III. rickcornish.net
Post Reply