I’m working on video encoding on Jetson Thor running JetPack 7 (Jetson Linux r38.x) and want to confirm the expected state of hardware-accelerated encoding on this platform.
Background / observations
On Jetson Orin, NvVideoEncoder used /dev/v4l2-nvenc for NVENC hardware encode.
On Thor JP7:
/dev/v4l2-nvenc is present, but opening it fails during the capabilities query:
libv4l2: error getting capabilities: Inappropriate ioctl for device
Could not open device '/dev/v4l2-nvenc': Inappropriate ioctl for device
Follow-on failures like VIDIOC_REQBUFS ... Bad file descriptor occur because the fd is invalid after the initial error.
As a fallback, encoding via /dev/nvidia0 works, but I observe non-zero SM utilization alongside NVENC utilization using:
nvidia-smi dmon -s uet
Additionally, on our Thor JP7 image, /usr/lib/libv4l/plugins/libv4l2_nvvideocodec.so appears to be missing.
Questions
On Thor JP7, is “GPU-free” NVENC (encode without driving GPU SM utilization) still expected to be available via the V4L2 encoder device (/dev/v4l2-nvenc)?
Is libv4l2_nvvideocodec.so expected to be present on Thor JP7?
If yes: which package provides it / where should it be installed?
If not: what is the intended replacement for the libv4l2-based codec plugin path on Thor JP7?
Hi,
It is GPU-free NVENC on Jetpack 7 Thor. On Jetpack 6, the low-level software stacks are different from dGPU. On Jetpack 7, it is unified. Still the hardware engine is NVENC. Please refer to jetson_multimedia_api samples of r38.2.1 to use NVENC: