Your GPU is rather ancient, though it looks like the Turing cards still get the newer drivers ... what driver number are you using?
Next, your CPU does have internal processing for long-GOP, but ... isn't a particularly new/hot CPU. So "adequate" I guess.
Now ... what you're wanting to do is to process up to 20 tracks, simultaneously!!!!... of the nastiest format/codec out there for editing purposes ... that is something you need to understand.
To play back one track of that, the computer must process, create frames for, and store between 9 and 50 or more "partial" frames, both in front of and behind the 'current' frame. Note that the vast majority of frames have only a number of pixels in them ... much of the image is from another frame, and so the computer needs to mesh frames from several frames to create the next displayed frame.
That is why colorists ... who have typically 'heavy iron' hardware that dwarfs yours, do not want to work with long-GOP for grading ... and typically as soon as they get such from a client, do a transcode to say ProRes422 or something, that they will import and grade with.
Yet editors, with much lesser machines, want the original long-GOP to "just work".
With a really, really high-end rig you might get 10 or more tracks of H.265 to play back ... maybe. Other than that, proxies, rendering sections of the timeline, or t-codes are what are the practical working methods for you.
1
Reply
AdChoices