FORUMS: list search recent posts

DELIVERY SYNC PROBLEM - must deliver - mind blown

COW Forums : Apple Final Cut Pro Legacy

<< PREVIOUS   •   FAQ   •   VIEW ALL   •   PRINT   •   NEXT >>
Timothy Anderson
DELIVERY SYNC PROBLEM - must deliver - mind blown
on Oct 29, 2011 at 8:38:38 pm


To keep it short: We are delivering a 24 FPS DCP feature by Monday and are experiencing sync issues nobody can seem to figure out. ANY help would be greatly appreciated as we have to render tonight!

The facts:
1. The film was shot at 24p and edited in a 23.98 timebase.

2. The sound mix was done in Protools in a 23.976 environment.

3. The 23.976 session mix stems sync with the 23.98 video.

4. The film was corrected in a 23.98 MISTIKA color session and exported as a 24 FPS DPX sequence.

5. The sound house performed the necessary pull-up and rebounced the stems for 24 FPS.

6. These stems DO NOT SYNC with our 24 FPS DPX sequence nor the 24 FPS ref. QT we created from the DPX sequence in a 24 fps seuqnece in FCP or AE.

7. HOWEVER, the sound house says in the session itself, the mix IS IN SYNC with this 24 FPS ref. QT (the one created from the DPX sequence).

8. The duration is exactly 01:30:00:00 (or TC 02:30:00:00), but when the file is brought into a 24 FPS video editing sequence in both FCP and After Effects, the file is displayed as being exactly 5 seconds and 6 frames SHORTER.

9.When the 1 hr. 30 min. stems are opened in ProTools, Quicktime, Soundtrack, etc. they ARE shown as the 01:30:00:00 duration. What gives

10. I can sync both the 24 FPS QT ref. and the 24 FPS audio in QT 10.0 when I open both and guerilla sync by playing at the same time.

Our final destination is DCP which of course is 24 FPS. Any ideas?


Return to posts index

Michael Gissing
Re: DELIVERY SYNC PROBLEM - must deliver - mind blown
on Oct 29, 2011 at 11:30:32 pm

Are you reimporting the 24 fps back into FCP? If so FCP stamps a frame rate in the file metadata which is based on your default project rate which is probably 23.98. It changes the file so if you import that same file into AE it probably reads the incorrect metadata as well.

If that is the case then delete the sound files on the Mac and then copy them from an external source with a name change. Try syncing in AE first. Don't let FCP import the files.

Return to posts index

Timothy Anderson
Re: DELIVERY SYNC PROBLEM - must deliver - mind blown
on Oct 30, 2011 at 12:04:41 am

Ah - ok - wow yeah that makes sense - I suspected there was some metadata darkness going on -

Great - trying everything now and will do a test DCP...


Return to posts index

<< PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
© 2018 All Rights Reserved