Thanks for your answer, but the article just mentions “h.264” and no profile.
Video files with H.264, HEVC, MPEG-2, and VC-1 encoded video can take advantage of hardware-accelerated decoding.
I just looked through the logs and i found that the transcoder is checking for a profile
#example of a normal encoded file = h.264 high profile
Sep 02, 2021 13:19:56.045 [0x7f4dbbd48b38] DEBUG - [Transcode] Codecs: Testing with profile 'High'
followed by
Sep 02, 2021 13:19:56.077 [0x7f4dbbd48b38] DEBUG - [Transcode] TPU: hardware transcoding: using hardware decode accelerator nvdec
Sep 02, 2021 13:19:56.077 [0x7f4dbbd48b38] DEBUG - [Transcode] TPU: hardware transcoding: zero-copy support present
Sep 02, 2021 13:19:56.077 [0x7f4dbbd48b38] DEBUG - [Transcode] TPU: hardware transcoding: using zero-copy transcoding
Sep 02, 2021 13:19:56.077 [0x7f4dbbd48b38] DEBUG - [Transcode] TPU: hardware transcoding: final decoder: nvdec, final encoder: nvenc
=> working hw decoding
with the other file => h.264 constrained baseline, there is no
DEBUG - [Transcode] Codecs: Testing with profile ´xxx´
line. As a result these lines are printed
Sep 02, 2021 13:16:53.796 [0x7f4dbcc0eb38] DEBUG - [Transcode] TPU: hardware transcoding: enabled, but no hardware decode accelerator found
Sep 02, 2021 13:16:53.796 [0x7f4dbcc0eb38] DEBUG - [Transcode] TPU: hardware transcoding: final decoder: , final encoder: nvenc
=> cpu decode.
So it´s not implemented that there could be a “constrained baseline” profile that could be decoded in hardware.
The hardware is more than capable…
vdpauinfo
Decoder capabilities:
name level macbs width height
----------------------------------------------------
****************many other codecs*****************
H264_CONSTRAINED_BASELINE 51 65536 4096 4096