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?
If you have a moment to test - try using Adobe Media Encoder or Magic Bullet Grinder to make your ProRes files. I have used both of these and had no issues with my ProRes files in Premiere. That will take FCP out of the equation as a potential issue.
You could try using DNxHD. Although needles suggestion might work too.
But honestly I'd recommend at least attempting to just use H.264 so you can avoid
transcoding until you run into the time where it starts causing a problem. That's
what I would do.
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.
It's in the heading of the discussion thread. Based on the recommendations I'm going to scrap my ProRes idea and go straight for native. It's clearly not worth the headache at the moment. I should be stressing over the cut, not the format of my footage.
It's in the heading of the discussion thread.
Shows how much attention I pay to what I read...
I agree - it would be wonderful to stress about creatively cutting footage in Premiere and not tech issues. That's the story of this software.