You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While implementing v4l2 h264 encoding I have stumbled upon an issue of H264 encoder dropping frames when bitrate overshots intended values. According to Stateful-M2M-Encoder docs I expected to receive CAPTURE buffer with V4L2_BUF_FLAG_ERROR set, but looking at the bcm2385-codec it seems like it silently returns a buffer to the VPU without notifying user space.
Describe the bug
While implementing v4l2 h264 encoding I have stumbled upon an issue of H264 encoder dropping frames when bitrate overshots intended values. According to Stateful-M2M-Encoder docs I expected to receive CAPTURE buffer with V4L2_BUF_FLAG_ERROR set, but looking at the bcm2385-codec it seems like it silently returns a buffer to the VPU without notifying user space.
Steps to reproduce the behaviour
Device (s)
Raspberry Pi Zero 2 W
System
Copyright (c) 2012 Broadcom
version 2ae30f53898ae2f1ba77ff570a92991bedfb0398 (clean) (release) (start)
Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: