-
Have we regressed 10 years?
Finishing up a show and I am shocked that a simple export with IN & OUT of a 48KHz Aiff downmix won’t sync back when reimported!? These are the types of issues we were experiencing with FCP ten years ago…
Sequence is:
TRT (IN to OUT): 15:28:04
1920X1080
Pixel Square
23.98
Apple Prores 422 (HQ)
Audio 48 KHz
16-bit
Stereo DownmixExported Audio to:
48KHz
16-bit
Stereo Downmix
TRT Reported in FCP when reimported: 15:29:02 -
7 Replies
-
Set non-drop time code?
-
Yes – no choice since this is 23.98
Frederic Lumiere
Producer
Lumiere Media -
[Frederic Lumiere] “Yes – no choice since this is 23.98”
And probably your Default Sequence is 29’97.
Read this:
https://library.creativecow.net/lyon_matt/fixing-fcp-assets/1
rafael -
Hi Frederic,
I wrote a tutorial for how to import audio properly to avoid this problem (you can skip the first section about xml editing)
https://library.creativecow.net/lyon_matt/fixing-fcp-assets/1
If you divide the frame counts of your two reported TRTs, you get 1.001, which as you probably know, is equivalent to the audio pulldown one would apply for telecine workflows. So FCP is trying to add pulldown. Import your audio properly and it will go away.
Hope this helps,
Matt Lyon
Editor
Toronto -
Matt,
Yes I remembered that it was important that your easy setup preset timebase matched the timebase of your destination sequence before importing audio files when I designed the Lumiere HD xml workflow – and I thought I had done that.
But – after reading your note, I reset the easy setup to prores 23.98 before the export as well and now you are correct, it sets the proper timebase for the audio when importing.
So THANK YOU for your excellent tutorial and for helping me solve this issue.
Best,
Frederic
Frederic Lumiere
Producer
Lumiere Media -
To answer the initial query, yes FCP has gone backwards and forwards with this one. It was necessary for FCP to handle broadcast wav files so they needed to handle timestamping and frame rates. They just implemented it strangely.
When importing a file into a project, the obvious methodology is to frame rate stamp a file based on the project that you are importing into. The default project, in this case, is clearly irrelevant. I have wondered for the past years why there have been so many posts on this (yours is about the third in four days) but it never affected me until I realised they were all from people who are using 29.97 or 23.98 frame rates. I work at 25 so there is no change from default for all my projects.
-
Thanks Frederic, I’m glad the tutorial was helpful!
best,
Matt
Reply to this Discussion! Login or Sign Up