Sebastian Dröge 3172bcd095 fmp4mux: Crank clock for the first fragment in more tests ... Due to how aggregator works, it depends on how buffers are pulled whether aggregate() is called again or it is waiting for a timeout or EOS: works: - pad 1: 4 buffers, pad 2: 4 buffers - aggregate ready: take all 4/4 buffers - pad 1: 1 buffers, pad 2: 1 buffer - aggregate ready: take all 1/1 buffers waits: - pad 1: 5 buffers, pad 2: 4 buffers - aggregate ready: take all 5/4 buffers - pad 1: 0 buffers, pad 2: 1 buffer - aggregate not ready: waiting for timeout or EOS Also don't manually set the clock time as that's unnecessary. Fixes https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/issues/274 Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-rs/-/merge_requests/998>		2022-12-03 18:21:19 +00:00
..
examples	fmp4mux: examples: Avoid unnecessary caps copies	2022-11-22 10:39:47 +02:00
src	mux/{mp4, fmp4}: Hard depend on feature v1_18	2022-11-29 21:06:12 +02:00
tests	fmp4mux: Crank clock for the first fragment in more tests	2022-12-03 18:21:19 +00:00
build.rs	Add new mux subdirectory for container formats	2022-10-23 20:25:08 +03:00
Cargo.toml	mux/{mp4, fmp4}: Hard depend on feature v1_18	2022-11-29 21:06:12 +02:00
LICENSE	Add new mux subdirectory for container formats	2022-10-23 20:25:08 +03:00