This is the main reason for intermediate codecs such as Cineform. if your editing and happen to CUT in-between FRAMES you put strain on your system because it needs to calculate exactly where the CUT took place. Of course, when you look at the footage on your PC they all look like real FRAMES, but that is the power of your CPU and the magic of the codec at work! The in-between frames are calculated mathematically- and for this we need a fast CPU for HD footage.Īlso. The in-between frames only account for the difference over time between the real FRAMES. In between lies several frames that don't contain all the information of a real FRAME or "photo". This way you get a real FRAME and then way later comes a new real FRAME. The files from your camera shoots Group Of Pictures (GOP). That is, if you shoot at 30 fps you want 30 FRAMES, or "snapshot photographs" for every second of video/film. for editing you normally want a file format, or codec, that gives you actual FRAMES of footage. as a 5D mkII owner, $99 might be a chunk small enough to swallow. The tip from Ray is generally a good one, but Cineform is a commercial product and is not free.
In your case we can rule out hardware as such, so it's more likely a codec problem, or at least your software setup.Īre you familiar with long GOP and the problems the raw files from your camera can create in editing?
Is it the edited and rendered files that play choppy in quicktime? Or even the original raw files?
You say you want help with Premiere, but then you say the problem is when you play your files in Quicktime. I think first we need to understand the problem exactly. Needless to say your PC is powerful enough, so that's not the problem.