-
matching archival and shot footage
Hello,
I’ve recently begun importing archival footage to my Final Cut project. The default sequence settings for my project are vid rate 23.98, DVCPRO HD 720p24. The shot footage for the project has a vid rate of 23.98, but compression 720p60. Finally, when I convert my archival footage from a video_ts file to quick time for use in Final Cut, I use DVCPRO HD 720p60 compression, but the vid rate is 29.97. Obviously, I have to use both frame rates and compression in the same sequence, so I am using my default settings and allowing Final Cut to render the archival footage to match the properties of our shot footage (but archival footage properties are still 29.97, 720p60). I’m wondering if there are any unforeseen consequences that will be difficult to deal with down the line. Unfortunately, as of yet, I do not have any monitor other than the computer’s, so I’m unable to tell if there are any immediate problems. Should I be handling these different frame rates this way, or is there a more Final Cut (and editor) friendly approach? Any advice would be greatly appreciated.
Thank you,
Matt -
2 Replies
-
There will be problems with that. Use Compressor to convert the footage to the proper frame rate.
Shane
GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
Read my blog, Little Frog in High Def -
Thanks Shane. At what point in the process should I use Compressor? Before importing the quicktime files into Final Cut, or can Compressor be used once the project is edited on only those clips that require it? I am new to this and I very much appreciate your help. I actually took over this project from a previous editor and recently saw that there was a difference between the default sequence settings compression, which is DVCPRO HD 720p24, and the compression of the shot material, whose item properties format compression setting is DVCPRO HD 720p60. This does not seem to pose any problems, but, again, is there something that I should be aware of in terms of this divergence?
Thanks again,
Matt
Reply to this Discussion! Login or Sign Up