[Bug 572973] [API] buffer size query or indication from audio encoders to upstream how many samples to produce per buffer

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=572973

--- Comment #23 from Nicolas Dufresne (stormer) <nicolas at ndufresne.ca> ---
(In reply to Olivier Crête from comment #22)
> I think the size here is not what you want. For audio encoder, you want an
> exact multiple of "size", forcing each buffer to be exactly "size" may
> explode the number of buffers and kill performance. Also, for my RTP ptime
> use-case, this use of the size in the allocation doesn't really work as
> payloader normally operate on encoded data which case be varying size in
> bytes. We may want to add an allocation meta with a duration in time instead
> of bytes.

That's why I said it's best effort, a  recommendation. Element won't start
buffering just because the size is bigger. Obviously, as size which is not a
valid multiple of frame is not valid. It should be rounded up in general.

It's not going to explode the number of buffers, because no one will break
GstBuffer in smaller one if downstream suggest a smaller size.

Can you better describe your ptime use-case please ?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.