AMD VCE / GPU Clock speed during encoding

[purduephotog]

AMD Radeon 56- during encoding only memory clock shows activity




Not a problem. During Hardware (AMD VCE / H.265 the memory clock ramps up to 800mhz, but the GPU clock sits idle at 38mhz.




1.2.2




Windows 10

It's really not a 'problem' I just don't know what's 'standard' for this software during encoding.


HandBrake Activity Log ***required*** (see How-to get an activity log)

Code: Select all

Please replace this text with the contents of your log file between the two code tags - OR -  provide a pastebin URL in place of these 3 lines.

[rollin_eng]

Could you please post your HB logs, instructions can be found here:

https://handbrake.fr/docs/en/latest/hel ... y-log.html

[BradleyS]

VCE is a separate ASIC chip on your graphics card. The GPU processor is not used directly.

[purduephotog]

VCE is a separate ASIC chip on your graphics card. The GPU processor is not used directly.

Oh. Sigh. So all that beautiful floating point isn't used. OK... explains why the heat load was low.

Thank you. I guess I've gotta go Intel

[BradleyS]

Intel QSV is also an ASIC.

[Rodeo]

Video encoding is not parallel enough to be worth encoding on the GPU itself. GPU encoders (implemented in CUDA etc. and running on the GPU itself) are a thing of the past, the tradeoffs they made to achieve the encoding speed people expected had a significant negative effect on compression efficiency (not to mention it would impact graphical performance of other apps while encoding).

Modern hardware-accelerated encoders may not be the most efficient out there (in terms of compression) but are still significantly better than the old generation.