![]() |
FCP workflow
I don't know if perhaps I've simply been spoiled by using DVCproHD for the past couple of years, but it seems as though 7D footage converted to ProRes 422 is quite taxing on my system. Is there something I'm missing that would be causing this or is it just the difference in the codecs that I'm now noticing?
|
I'm not having any problems with it. Works fine. I use a 17" MacBookPro.
|
Quote:
|
There might be a setting in either the timeline or the transfer into ProRes that might be causing an issue?
I have been using MPEG Streamclip to do my batch transfer from H.264 to ProRes (been doing HQ so far). It seems to be a little more straight forward to convert that Compressor—less to mess up I think. I just let Final Cut change the timeline settings when I drop the newly converted ProRes file in. ProRes might be taxing your system if it's an older machine with minimal ram. Your drive that the ProRes files reside on might be the problem too, if the drive is a slow connection (USB2 instead of Firewire800 or Sata). See if it's just a setting thing first (if you have a fast machine). |
My machine is kind of old (2.26 GHz Quad Core Mac Pro/8GB RAM). Playback in 24fps is fine, but 30 is always choppy. I haven't tried 720p/60 yet.
|
FCP workfrom from Canon 7D continued
I was wondering about the workflow and what codecs people are capturing and editing in? Out of the camera the file is h.264.(correct?) can you just import into FCP?....and then edit in the codec of your choice? (Apple Pro res?)
|
Its better to render your clips first in the right codec.
Because if you work direct with h.264 files every change in your timeline will need extra rendering. Daniel |
All times are GMT -6. The time now is 12:26 PM. |
DV Info Net -- Real Names, Real People, Real Info!
1998-2025 The Digital Video Information Network