I'm editing a project with footage that was shot on a couple Canon T2i's. 1080p and 720p, 23.976fps and 59.94fps. I converted the H.264s to ProRes422 using Episode Pro (v6.3) and then from there added Reel Names to the clips using qtchange.
I wanted to edit with ProRes because I know down the line I'll be adding a lot of effects and color correction. I'm working on a 2010 iMac (i7, 2.3gHz, 8GB RAM, no nVidia card, OS 10.6.8) and I'll run into a processor bottleneck with the raw H.264s. In an effort to save time and sanity down the line, I chose to go ProRes with my workflow. I could just as easily edit this in FCP but I'm trying really hard to not go back to it and I wanted Dynamic Linking as well, again because it will be effects heavy.
After watching a few clips, I realized I was getting some bad drop frames on one or two occassions. I can't drag the clips into the timeline directly from the Project panel. I can't drag from the Source panel either.
A lot of times, I'll have a clip selected in the Project panel and I'll hit F10 or F9, the keys I've mapped Insert and Overwrite to. Nothing. Doesn't work. Every once in a while the whole app will freeze up. Keyboard shortcuts are rendered useless. No playback.
But, if I use an H.264, it's fine on all counts. Drag and drop, no drop frames, keyboard shortcuts. So I'm wondering if I should ditch the ProRes (once and for all) and stay with the native files. Will my iMac handle it? Will I hate myself later when I get into finishing?
Thanks for all the help in advance, guys (I know this is beating a dead horse by now).
Hmm I use ProRes daily and have no problems.
Although honestly I would try to just edit native files first and then if it seems like you are having issues then use something else. I always try to avoid changing things unless something isn't working. So my answer would be to just use Native files.
I usually don't have issues with it either. My regular workflow sees me using Log And Transfer in FCP to get the files into ProRes, so I'm wondering if using an alternative method has created the problem?
I know I will have issues later if I work with native H.264s. I'm trying to avoid that by converting, but even that is failing me. Maybe I should convert to an alternative codec?
Yeah, tried both of those. I have some 400 shots that are varying frame rates and resolutions and I wanted to convert them in a way that would have been similar to FCP, just blanket convert them into Quicktimes, without altering resolution or frame rate. I didn't want to have to go through and separate all my 24fps and my 60fps shots. Grinder would have been the other option, but it kept messing up the 60fps shots. And it's way too unstable on my machine.
All in all it was a messy and annoying road where Episode (which is actually a pretty good piece of software) mimiced FCP's Log and Transfer the best.
If only the DIT kept the directory structure in tact, I wouldn't be in this situation...
I guess I could compose my edit and then "Media Manage" the footage in the cut to ProRes and from there work with it in AE or Premiere. Again, I'm worried the H.264s will cause a bottleneck on my system. It's happened before. The longer I work on a project, the more I crame into my timeline, it chokes. Slow playback and app response time, drop frames, disastrous with affects applied. Feels like FCP7 all over again. And this was on a 12-core, maxed out Mac Pro!
I didn't see anywhere - are you on CS6 or earlier? I used to transcode over to ProRes when I was on 5.5 since H.264 playback from my 5D was sluggish and horrible. CS6 has been a much different experience, and i just use the H.264 out of the camera now even when doing effects and Colorista, etc.
North America
Europe, Middle East and Africa
Asia Pacific