Software vs Hardware Encoding ....hmmm

[STUDIO29K]

respect
when it is software encoding, I get the size of the output file as in the picture 9652MB (as it should be)...when I switch to hardware encoding with the same settings...I get an output file of 562 MB. I want to say that I don't get the calculated size of the output file that Pp determines, but I get a smaller size.......why does this happen ...it's the same with H265....

Target bitrate 1000 Mbps
bitrate encoding is CBR
graphics GTX 3090Ti 24GB

[MyerPj]

Why Constant Bit Rate? It's Variable Frame rate that is the problem, and variable bit rate is generally a good thing. You should get used to Hardware rendering, as Adobe is seriously thinking of removing the Software rendering option. That estimated size is a quess, or 'estimate' 🙂

[MyerPj]

Here's a link to the tread in the Beta Forum, regards Software Rendering:

https://community.adobe.com/t5/premiere-pro-beta-discussions/new-in-beta-software-rendering-option-r...

[STUDIO29K]

Thanks....

[STUDIO29K]

"Why Constant Bit Rate?"

why CBR is not good in your opinion....for hardware encoding I only have CBR and VBR, 1 pass...when I switch to VBR, 2 pass, it switches to software encoding again....can you give me a little more detail explain if you have the nerve and time 😉 😉 😉 ...thanks

[STUDIO29K]

And my question was not about bit rates, but why do I get different sizes of the finished, rendered file, when it comes to software or hardware encoding...

software encoding...I get exactly what Pp calculated and I get the specified target bitrate of 1000 Mbps, which means I get in the finished file all the parameters that I set in Pp and a file size of 9652 Mb - (1000 Mbps), as in the picture...and that's ok, that's how it should be... (CBR)

hardware encoding...from the same parameters, I get a finished file of 1.02GB with a bit rate of 114 Mb/s... (CBR)

should the size of the output file be the same in both cases with the same parameters, and hardware encoding is there only to use the power of graphics cards....

please, explain to me this difference in the obtained data, before you completely throw it out of use software encoding...THANKS

[R Neil Haugen]

Software and Hardware encoding are two completely different processes. Period. Although the details can be a full-on rabbit hole discussion, I'll give the practical information about using them.

Software means the CPU looks at the instruction set in the export prest, and then uses whatever resources it is set to do for creating that result.

Hardware means the processing gets turned over to an automated chipset in either the internal iGPU or the discrete GPU, which does the encoding. Based on the internal commands of the chipset, when it sees certain parameters in the export preset.

So Software means you do get a full custom set of instructions followed pretty closely. There can still be some differences depending on a number of things, but it's normally decently close.

Hardware is controlled totally by the hardware chipset in use. It's outta Premiere's hands at that point, is perhaps one way to look at it. That's why there can be tremendous speed increases in Hardware long-GOP encoding: there's no computing involved at all. It's simply a data replacement automated operation.

Second, there are limitations on what can be Hardware encoded ... and two-pass encodes have always been entirely a Software encoding thing because of the above listed differences.

Does that help some?

Long-GOP stuff is nasty to edit with. Using it to encode to, it will induce macro-blocking and banding if you're not careful. Which is fatal to the file data, and unrecoverable.

However, it can provide incredible file-size reductions. Use it only when you know the risks, how to at least mostly avoid them, and how to set the controls for best results.

[MyerPj]

BTW: VBR 2 pass is software only. As Neil is saying, they are two distinct methods. The hardware (Nvidia/Amd/Ms) doesn't support 2 pass encoding. Check the link I gave, Adobe is actively moving to remove Software rending. 

The posts on these subjects from Neil really helped me up my game some years ago... 8, 9, 10ish... (ugh) 🙂 regard Long Gop, etc... so it's worth giving some thought to what he is saying.

Cheers. 🙂

[MyerPj]

And VBR allows the encoder to decide how much bit rate it needs for various scenes, a lot for a shot of the beach, waves and water, or leaves in the trees, and not as much for a still life in front of a white background, etc. (a good thing)

VFR induces all sorts of havoc, it's meant only to reduce the initial size of the recording, or the heat generated by the internals as it records. Most phones and screenshots are VFR, it's really bad to edit with. All legit cameras use CFR. 

Long GOP is murder on the computer, thus why we like ProRes to edit with, all the frames are compete within the file, so, a reasonably fast SSD allows an excellent editing experience, and is virutally lossless to boot.

[STUDIO29K]

Thank you all, you have helped me a lot...