Developers report that the NVIDIA Jetson AGX Orin V4L2 encoder does not properly process or signal BT.2020 colorimetry metadata, defaulting to SMPTE170M and limited range. This limitation affects engineers relying on accurate full-range H.265 and AV1 encoding for streaming workflows on the platform.
Engineers building HDR or wide-gamut streaming pipelines on Jetson AGX Orin cannot rely on the V4L2 encoder to signal BT.2020 or full-range metadata correctly, forcing workarounds at the muxer or bitstream level — and only if the pixel data itself remains unmodified. NVIDIA has acknowledged the gap but has not committed to a timeline for a fix. The broader Jetson embedded encoding ecosystem has seen recurring colorimetry issues since at least August 2024, when a separate developer reported partial BT.709 signaling failures on the same platform. Watch for NVIDIA L4T release notes mentioning tegrav4l2 colorimetry fixes in upcoming JetPack updates.
NVIDIA's Jetson AGX Orin platform has faced persistent colorimetry signaling limitations in its V4L2 encoder stack. In the same developer forum thread, NVIDIA staff confirmed that no software stack exists for encoding BT.2020 on Orin and that only BT.2020 YUV420 10-bit H.265 encoding is being investigated internally, while noting that the successor AGX Thor platform does support BT.2020 encoding. This positions the Orin as a transitional platform for wide-gamut embedded encoding, with full BT.2020 support deferred to the next hardware generation.
NVIDIA's recommended remediation path for affected developers is a JetPack upgrade. In the forum response, NVIDIA engineers advised upgrading to JetPack 6.2.2 r36.5 or JetPack 7.2 r39.2 to resolve colorimetry issues, with a PSIRT security fix offered as a patch for those remaining on r36.4.7. The JetPack 6.2.x line corresponds to Linux for Tegra (L4T) r36.5, which NVIDIA released in early 2025 as part of its ongoing Orin platform maintenance cycle. Developers who cannot upgrade due to production constraints must apply the PSIRT patch manually, adding operational overhead for teams running locked-down embedded systems.
The technical workaround available to streaming engineers depends on whether the encoder modifies pixel data or only mislabels metadata. In the forum discussion, the developer asked whether the encoder performs any conversion, clamping, or range remapping based on colorimetry fields, or whether input sample values pass through unchanged with only VUI metadata being incorrect. If the issue is metadata-only, engineers can inject correct BT.2020 and full-range signaling at the bitstream or container level using tools like FFmpeg's h265_metadata or av1_metadata bitstream filters. NVIDIA also noted that BT.601 and BT.709 in both limited and full range are supported through the DMABUF path using the enable_extended_colorformat flag in the 01_video_encode sample, though MMAP-based pipelines may not expose the same controls.
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred source