GStreamer multimedia framework
Find a file
Sebastian Dröge 6d6c693254 audiomixer: Remove weird and wrong segment handling
There's no reason why audiomixer should override the segment
base of upstream with whatever value it got from a SEEK event,
or even worse... with 0 if there was no SEEK event yet. This
broke synchronization if upstream provided a segment base other
than 0, e.g. when using pad offsets.
Also that this code did things conditional on the element's state
should've been a big warning already that something is just wrong.
If this breaks anything else now, let's fix it properly :)

Also don't do fancy segment position trickery when receiving a
segment event. It's just not correct.
2015-02-05 16:02:54 +01:00
gst/audiomixer audiomixer: Remove weird and wrong segment handling 2015-02-05 16:02:54 +01:00
tests/check/elements audiomixer: Make flush start/stop test non-racy 2015-01-29 10:24:18 +01:00