On Wed Feb 12 21:24:38 2025 +0000, Brendan McGrath wrote:
re: how `h264parse` splits; if you run `gst-inspect-1.0 h264parse`, you'll see one of the caps is `alignment`, which has two options:
- `au`; and
- `nal`
So it can split the buffers in one of two ways:
- at the `au` boundary (which stands for 'Access Unit', and represents
a frame (or a field for interlaced); or 2. at the 'nal' boundary. These are smaller than access units and represent a logical bundle of data (which can be metadata or image data). An AU may have several NALs, but a NAL will never overlap two AUs.
so, turns out pushing a large buffer through just the parser is enough to cause stutters. it's way better than having it go through the whole decoding pipeline, but it's still noticeable.