[Bug 781673] aggregator: always handle synchronized events on output thread
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Sat May 20 14:26:47 UTC 2017
https://bugzilla.gnome.org/show_bug.cgi?id=781673
Olivier Crête <olivier.crete at ocrete.ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|git master |1.13.1
--- Comment #45 from Olivier Crête <olivier.crete at ocrete.ca> ---
Merged:
commit d2335bce9b96c95edeb4bafdabcf4ba39def8ade
Author: Olivier Crête <olivier.crete at collabora.com>
Date: Sat May 14 15:52:37 2016 +0200
aggregator: Always handle sync'ed events on output thread
Having all synchronized events always be handled on the output
thread should make synchronization easier.
https://bugzilla.gnome.org/show_bug.cgi?id=781673
commit 4cec1925e3768227150f82541b12ff61d4537e50
Author: Olivier Crête <olivier.crete at collabora.com>
Date: Wed Jul 6 16:39:17 2016 -0400
aggregator: Delay clipping to output thread
This is required because the synchronized events like caps or segments
may only be processed on the output thread.
https://bugzilla.gnome.org/show_bug.cgi?id=781673
commit a6710944e81016fdee3a2000c5d98ca06d5d3f24
Author: Olivier Crête <olivier.crete at collabora.com>
Date: Thu Jul 7 16:13:57 2016 -0400
aggregator: Make pad eos as soon as all buffers are processed, dont way for
events
https://bugzilla.gnome.org/show_bug.cgi?id=781673
commit 6e96bebd5bd20ceb8d426958715d539dde67770e
Author: Olivier Crête <olivier.crete at collabora.com>
Date: Thu Jul 7 11:47:40 2016 -0400
aggregator: Only count buffers when declaring queue full
https://bugzilla.gnome.org/show_bug.cgi?id=781673
commit c0849df4aca6b51cc8c79f502bfcdb2171a377f2
Author: Olivier Crête <olivier.crete at collabora.com>
Date: Wed Jul 6 17:28:11 2016 -0400
tests: Test caps using query
Sending an event can accepted event if the caps were rejected
because the event could be queued and processed later.
Also send a drain query in the caps test to make sure that the
event has been processed.
https://bugzilla.gnome.org/show_bug.cgi?id=781673
commit 4d408ea9205aedea1b51f571b89ee0cca339315a
Author: Olivier Crête <olivier.crete at collabora.com>
Date: Wed Jul 6 16:41:44 2016 -0400
aggregator: Simplify clip function
The return value was ignored anyway
https://bugzilla.gnome.org/show_bug.cgi?id=781673
commit 20aee5f5757e2b000d8e55bd1fb5386548526749
Author: Olivier Crête <olivier.crete at collabora.com>
Date: Sun May 15 16:04:58 2016 +0300
aggregator: Only declare first buffer on actual buffer
The function needs to be unlocked if any data is received, but only
end the first buffer processing on an actual buffer, synchronized events
don't matter on the first buffer processing.
https://bugzilla.gnome.org/show_bug.cgi?id=781673
commit 1ab33d78feb5d27adf229688ea56b92ce4c40222
Author: Olivier Crête <olivier.crete at collabora.com>
Date: Tue May 9 20:20:07 2017 -0400
aggregator: Set initial position on first buffer
Set the initial position on the first buffer, otherwise the queue
will grow without limits before the output thread is started.
https://bugzilla.gnome.org/show_bug.cgi?id=781673
commit 82f7b00ea38a6f83d3eb5d9405d25460dacf51e3
Author: Olivier Crête <olivier.crete at collabora.com>
Date: Tue May 9 20:06:29 2017 -0400
aggregator: Reset the pad's first buffer flag with the rest
There is not reason to have separate code to reset this one.
https://bugzilla.gnome.org/show_bug.cgi?id=781673
commit 05374aa22cf730cd876cfb3f127be71ea9271b48
Author: Olivier Crête <olivier.crete at collabora.com>
Date: Tue May 9 20:05:55 2017 -0400
aggregator: Reset pad on init
Factor out the pad reset code from the flushing and use it on init as well
https://bugzilla.gnome.org/show_bug.cgi?id=781673
commit d722e064fd1c3222eb34595ad535a8f9cee10792
Author: Olivier Crête <olivier.crete at collabora.com>
Date: Tue May 9 20:13:58 2017 -0400
aggregator: Fix indentation
https://bugzilla.gnome.org/show_bug.cgi?id=781673
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
More information about the gstreamer-bugs
mailing list