Nvidia Thor Jetson 7.0 misses SPS/PPS on later I-frames
A developer is reporting an issue with the Nvidia Thor Jetson 7.0 NvVideoEncoder API where the `setinsertspspps` function, intended to insert SPS/PPS/SSP (nal_type=32) at the start of each I-frame for H.265 streams, only works for the first I-frame. Subsequent I-frames are missing this critical header information, which can lead to decoding issues.
Key Takeaways
- The issue is reported on Nvidia Thor Jetson 7.0 using the NvVideoEncoder API.
- `setinsertspspps` is enabled, but only the first H.265 I-frame includes VPS/PPS/SSP information.
- The missing header data is described as `nal_type=32` in the post.
- Subsequent I-frames are reportedly sent without the critical SPS/PPS/SSP information, risking decode failures.
Why It Matters
If this report is accurate, H.265 streams encoded on Nvidia Thor Jetson 7.0 may be unreliable after the first I-frame because later keyframes do not carry the SPS/PPS/SSP headers many decoders need. For streaming workflows, that puts the NvVideoEncoder API itself in the hot seat, not the playback layer. The key signal to watch is whether NVIDIA confirms a fix or documents a workaround for setinsertspspps in Jetson 7.0, since that will determine whether integrators can trust keyframe header insertion across an entire encode session.
Read full article at forums.developer.nvidia.com
Enjoy our coverage?
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