baseparse: Fix upstream read caching
When running in pull mode (for e.g. mp3 reading), baseparse currently reads 64KB from upstream, then mp3parse consumes typically around 417/418 bytes of it. Then on the next loop, it will read a full fresh 64KB again, which is a big waste. Fix the read loop to use the available cache buffer first before going for more data, until the cache drops to < 1KB. Fixes #518
-
mentioned in issue #530 (closed)
-
mentioned in commit gdesmott/gst-plugins-rs@6c691707
-
mentioned in merge request gst-plugins-rs!331 (merged)
-
mentioned in issue #547 (moved)
-
mentioned in issue gst-plugins-bad#1287 (closed)
-
mentioned in commit neithanmo/gst-plugins-rs@0015809d
-
mentioned in merge request !518 (merged)
Please register or sign in to comment