Rendering time is horribly long and not using GPU

[Matthew2843358703yp]

Hi all,

Im using a using i5-8300H and a GTX 1050 with 16GB DDR4. I have two clips, total 9 minutes. These clips are in a nested sequence, the effects are a posterize time with frame rate at 1.5 .. I’ve got the red bar on top of the sequence and am trying go and render the sequence, however when I render the sequence it wants to take an hour to two hours to render the sequence. It’s also only using up 100% of the cpu and 40% of the CPU’s GPU and 0% of the GTX 1050. How can I change it so it uses the GTX or it’s faster? 

when doing the same case on my 2016 MBP which is older, I get faster results. Now this may be because of OSes or not or just optimised hardware. But why is this the case?

[R Neil Haugen]

That's still a long discontinued 8th gen 4-core CPU ... and a 3-gen back GPU also. You don't mention your RAM, which is another potential issue. And how much room and type of drive for cache files.

Plus the media used ... 

[Matthew2843358703yp]

You're right. Apologies for not adding this in OP. In the first specs I mentioned it's got a config of 16GB ram and 120GB nvme ssd (not much) but has 70GB free. Second PC I mentioned (MBP) has 256GB SSD with maybe 100-70GB free, 8GB memory. 

As for the media used, 4k 120FPS footage, 9 minute clip. Is there other info you need?

[R Neil Haugen]

4k 120fps ... what created it, and what format/codec? Bit rate?

[Matthew2843358703yp]

GoPro 10 - I'd assume MP4 and Codec I'm not sure, with bit rate I'm not sure either on how to check?

[R Neil Haugen]

The free utility app MediaInfo is useful for that sort of thing. Install it, then drag/drop a clip onto that applet's desktop icon, it opens ... go to the view that was called the "tree view" ... that might have changed recently. Anyway, it lists all the details of the video and audio in separate sections.

GoPro ... 120fps 4k ... um, there's not much out there that puts anywhere near that much load on a system for playback let alone render/export. 6k ProRes 444 is a ton easier on the system ...

[Matthew2843358703yp]

Video stream: HEVC , bit rate 99.3Mb/s, 3840*2160 (16:9), 119.880 FPS, HEVC

[R Neil Haugen]

That device ... can create some of the truly nastiest long-GOP media made. I've seen people test the clips with apps that sort out the iframes and dependent intermediary frame-sets. There are apparently ways to create "partial iframes" ... so some clips have gone over a hundred frames between complete iframes.

At that point, the system has to decode and decompress two or three iframes, and then ... create from data sets ... most of the pixels of the other hundred and some frames ... before it's ready to play the next ... frame of video.

Yowza.

[Matthew2843358703yp]

Yeah right that explains the technical side. But what can I do to fix it? Surely my GTX 1050 pc isn't way worse than my MBP? 

[Ann Bens]

Posterize time is a non GPU accelerated effect, hence the long export time with an unfriendly editing codec.