Good dive into content creation/encoding/software/hardware limits and the "whys".

jmc

Active member
I don't do "content creation" just encoding MPGs to x264.MP4s.
But this was fascinating about the "why" when running into scrubbing slowly or why only 12 cores used with X264 and so much more.

Just to play 4k HEVC, "software decoding" took 12 of 16 xeon cores and then there is the
MPG is less then x264 as is less then HEVC as is less then (V1?).

Going to have to watch this more then once to let it soak in a little at a time...

How many CORES do you REALLY NEED for...

 

aradralami

New member
I can back up the higher resolution scaling with core count statement. I did some cineform proxies for some 1080p footage and it used about 80% of my Ryzen 7 3700X. Going to 4K footage made the CPU hit 100% usage.
 

jmc

Active member
I can back up the higher resolution scaling with core count statement. I did some cineform proxies for some 1080p footage and it used about 80% of my Ryzen 7 3700X. Going to 4K footage made the CPU hit 100% usage.
This video is the only place that I remember talking about resolution as a piece of paper and the bigger it was the more the program could break it into pieces for more cores to use.

Would love to know more on the "pieces" and how/why the higher resolution creates more pieces for more cores to use.

Now I may be misunderstanding about "GOP"s and "IDR"s but I thought that they were basically a completely self contained unit
as to the compression and the frames that are part of that compression.

So with that thinking it seemed that any compression program could just assign a core to each IDR or GOP.
But clearly that is not how the magic happens as to cores used.
 
Last edited:
Top Bottom