-
23.98 time code window burn issue
Hey everybody,
I have quite a dilemma on my hands, so hopefully someone here can shed some light on this for me.
The short of it is I am handing over all content from my feature to the sound designer and dialog editor. I need to export a video track with burnt in time code, and my timeline is set at 23.98.
I have read every single time code post I could find on CC, and I found a lot of answers but nothing specific to my situation.
I know in FCP (6.06) you can either do a time code reader or generator. I have tried both and I have problems with both of them.
The big issue here is that I can’t nest any clips, because I am exporting the audio via OMF, and if everything is nested then all audio tracks get squashed down into 2 stereo tracks.
So nesting and just overlaying the time code reader is not an option.
I really need to be able to use the time code generator, however the problem is that there is no 23.98 setting. Only 24fps.
Even though my timeline and our audio departments timeline will be 23.98, can I still use the 24fps setting on the time code generator and be safe?
Does anyone have any other suggestions?
Thanks a bunch
-
12 Replies
-
Hey Cody,
Have you tried running the quicktime through compressor after you make it? In the Filters tab there is a ‘Timecode Generator’ that pulls the embedded TC from the quicktime you export from FCP and overlays it on the video.
Hope that helps.
-
I haven’t tried that, just because I have read that compressor is no god with 23.98 timecode and messes the sync up.
I think I might have found a work around though.
Im going to try and just export the OMF, THEN nest the sequence without changing anything, and add the time code (via TC Reader) in correct 23.98 and export right away. From that nothing should change between the OMF and the exported video with the timecode since I will not be touching anything in the edit.
I came up with this out of the blue, and I hope it works.
If anyone has any other suggestions or comments I would love to hear them.
I still can’t figure out why FCP can’t give me 23.98 timecode, its pretty standard
Thanks for the reply Dan!
-
Or duplicate the sequence, then nest one for the timecode. Export the OMF, then duplicate and nest. Or do you even NEED to duplicate? When you nest, it makes a new sequence called NEST.
I export a QT reference movie, take that into Compressor, and add the TIMECODE READER filter in there.
Shane
GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
Read my blog, Little Frog in High Def -
[Cody Hoerig] “I really need to be able to use the time code generator, however the problem is that there is no 23.98 setting. Only 24fps. “
Don’t use the GENERATOR…use the Timecode READER. That will read the timecode no matter WHAT the frame rate. That is the one you need to be using…NOT generator.
Shane
GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
Read my blog, Little Frog in High Def -
You an still use the 24fps option. I’ve used it before quite a few times and it’s accurate. My method of adding TC burn is create a black FCP title the same length as the sequence. You can type in how much you need in the duration TC box of the viewer. Than add this title to the highest track. I add the TC Gen to this title. Adjust the option of the TC Gen filter to 24fps. A simple test is the spot check down the timeline. You can see if the TC Gen matches the sequence timecode. In all my previous experiences, they have matched.
You said you can nest the sequence because of the audio but you can nest just the pix and add the reader to the pix nest. Audio tracks are still untouched and you can export your OMF.
CHL
Chi-Ho Lee
Film & Television Editor
Apple Certified Final Cut Pro Trainer
http://www.chiholee.com -
I agree with guys above… Make duplicates of sequence where you only nest video and then put timecode reader on it. Then I make another sequence where I strip all video and then export an omf.. then add two together on another timeline… it;s an organizational thing for me, doing it this way for film reels
Drew
https://www.imdb.com/name/nm2398405/ -
Drew wouldn’t it be easier to just open the nested sequence export the OMF, and then put that nested sequence into another sequence and drop TCR on it?
Basically how i was thinking of doing it, i didnt even realize, but a nested sequence can be “clicked” into to show its contents and i can export OMF right from there.
Thanks a bunch for the replies guys, much appreciated!
-
Just adding my $0.02:
I agree with everyone’s comments. Once you lock your edit, there is nothing stopping you from duplicating the sequence as many times as you want. Often, I’ll make a new copy for each deliverable: audio edl(s), audio omf(s), picture edl(s), etc…
I personally prefer Chi-Ho Lee’s approach of adding the slug track with timecode filter. If you manually modify the timecode track of the slug, you can then use the TC reader plug-in if you like.
And Cody, you shouldn’t confuse the timecode BASE with the picture FRAME RATE.
23.976 fps material still uses base-24 timecode, just like 29.97 video uses base-30 timecode. It is normal to not see a 23.976 setting in the filter.
[Cody Hoerig] “[I haven’t tried that, just because I have read that compressor is no god with 23.98 timecode and messes the sync up.”
It is true that Compressor is no God, but people often expect it to turn water into wine…
sorry, I couldn’t resist 🙂
But seriously, I’ve never had a sync problem with 23.98 material and Compressor. Or are you talking about a bug with the Compressor timecode burn in filter?
Matt Lyon
Editor
Toronto -
You can do that for sure.. I just like to make sequences for every element(omf,edl,timecode burnin) I am sending to a sound post house… It’s an origination thing
Drew
https://www.imdb.com/name/nm2398405/ -
Hi Matt,
I am having an issue with Compressor in timecode. I have source material which is EX3/Mpeg 2/1080 24p, I edited my sequence, exported it to self-contained file and it starts at 1:00:00:00 (playback in Quictime Pro 7 verifies this), when I open it in compressor and preview it the timecode starts at 00:59:56:10. I am suspecting this has to do with the framerate.
Any ideas?
Elijah
Reply to this Discussion! Login or Sign Up