Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

29.97 FCP workflow

david_winters

Well-known member
Joined
Jan 27, 2007
Messages
512
Reaction score
0
Points
0
Location
Orange County, CA
Any issues, or workflow differences, between shooting 23.98, FCP editorial with proxies vs shoot 29.97, FCP editorial with proxies?

We've fully tested the workflow at 23.98, however we have a job next week which will shoot and finish as 29.97.

Thanks
Dave
 
Well it sort of depends how you intend to finish. Will you shoot 30fps and edit 29.97 or shoot and edit 24p and then output to a tape format and add pulldown. I'd recommend the latter.

Noah
 
The project will shoot 30/29.97 fps. Post is all 29.97fps, no pulldown. Any potential issues with hardware or workflow? We'll be recoding to the Red drive.

Edit: Does build 13 shoot at 29.97 of just 30fps? I need to check, but I think 13 is the build we are to shoot on.

Thanks
 
Planning to pull the camera generated proxies directly into the FCP bin, cut, export as Pro-Rez hq and then over to AE for compositing. I've run through the entire workflow with 23.98 proxies and we are happy with the results vs generating corrected proxies or ProRez files in RC/RA first.

I've played with L&C a little, but I don't think we'll need it for this job. It's a one day shoot and two day post turn around. Best takes are logged on set and we should be fine with the WB settings generated in camera.

Want to avoid a pass through RC or RA due to an extremely tight timeline.
 
I realize this is an Apple-centric post, but there are many MAC houses using FCP that are also toying with the idea of using Scratch in the pipeline. For those who are considering this as an option, please consider the following:

If you want to shoot at 4K and layoff high quality cutting copies or masters to 1080 in realtime using Scratch, be sure to shoot at 24p in the camera.

There is no system on the planet that can reliably decode and playout r3d files at full quality debayering @ 1080 (ow 2K) resoution @ 30 (or 29.97) FPS.

Once you have your 1080 24p footage on tape and/or ingested into your Mac Pro as ProRes, you can cut all day long in FCP and apply the 2:3 pulldown for 29.97.

Adam
BOXXlabs
 
i'm inclined to agree. also i'm worried for you cutting off the proxies, how much testing have you done with these. Running your system off of RT settings makes your entire cut ram powered rather than hardware powered. Why 29.97 shoot? If you want RED quality for NTSC finishing why not shoot 24 and pullback upon output?
 
This job has to shoot at 30/29.97 fps
and carry through in post. I'm fitting into an existing system and workflow. For this application we can not shoot 24fps or work with a 3:2 pulldown in post. Need 29.97/30 discreet frames in post, progressive.

Will it be possible to playback 30 fps proxies in fcp? Playback quality can be sub par as long as image quality is comparable in quality to the 23.98 proxies, once exported out of fcp as prorez.

Am I ok or do we have to shoot on another camera system to get 30fps?
Thanks
 
Back
Top