Edward Hervey f03443f90c concat: Handle single-pad use-cases ... When EOS reaches concat, it will switch to the next candidate as its activate pad. The problem arises when there is only one sinkpad, the "active" pad becomes NULL. This results in concat becoming unusable after it receives a *single* EOS on its single sinkpad. If we detect there is a single sinkpad and there is no current active pad: * If we are waiting (from selected sink event/buffer), become the current active pad. * If there is a seek request, send it upstream. We don't switch the active_sinkpad property at that point in time, since the seek could fail. If the seek succeeds, the following SEGMENT (or STREAM_START) will cause the pad_wait() to elect that pad as the new active one. * Flush events get forwarded https://bugzilla.gnome.org/show_bug.cgi?id=790167		2017-11-10 14:15:46 +01:00
..
elements	concat: Handle single-pad use-cases	2017-11-10 14:15:46 +01:00
tracers	latency tracer: add timestamp to tracer records	2017-11-04 13:51:00 -04:00
Makefile.am	tracer: initial prototype for the tracing subsystem	2015-10-05 20:59:39 +02:00
meson.build	meson: add option to disable tracer hooks	2017-07-05 13:27:48 +01:00