Naw, it's simply having the H.264/5 long-GOP media there. That stuff is nasty fast for the camera to encode, because they have a special chip made to precisely do the encoding. Your computer doesn't have that specific chip, right? So it has to do the decoding by "software" ... by computations.
Some computer CPUs have various bits built in to do H.264/5 long-GOP decoding/encoding, and fed the 'right' encoded clip, do an amazing job of speed work on that decode or encode. But that same CPU, with a different encoded H.264/5 file, may not do so well.
Yea, that all gets really frustrating. Two steps forward and four back at times. And when you get a new rig that doesn't do something that "seems so basic" compared to an older, in general lesser rig, well ... one naturally gets into a bit of a huff. To be polite about it ... I certainly do!
It's just one of those tons of questions you have to learn how to ask when getting the gear. And still, there's gonna be questions you wished you'd thought of asking.
As noted by others here in various threads, on some rigs you really either need to transcode some of the long-GOP stuff, especially the 4k 10-bit ones, to something like ProRes, Cineform, or DNxHR to get good playback and editing performance. Or at the least, make proxies.
Is it frustrating to still need those "old workaround" with hot new gear? Yea. But as a practical matter, what works ... works ... and one gets on with Life. Sigh.
Neil
(Who gets on with Life but still has underlying ... irritations ... )
8
Replies
AdChoices