[Bug 761211] pad: blocking pull probe during pull_range doesn't work
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Thu Feb 18 09:47:58 UTC 2016
https://bugzilla.gnome.org/show_bug.cgi?id=761211
Sebastian Dröge (slomo) <slomo at coaxion.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
Target Milestone|1.7.2 |git master
--- Comment #19 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
Had to be reverted as it breaks various tests. The problem is that probes
without SCHEDULING or DATA flags will get all of them set in
gst_pad_add_probe().
So we would now always get probes with GST_PAD_PROBE_TYPE_EVENT_DOWNSTREAM
called whenever a pull happens.
Not sure how to handle this other than setting the BUFFER flag for the PULL
probes like you suggested... and hoping that nobody ever created a probe that
assumes there is a non-NULL buffer whenever the BUFFER flag is set. Opinions?
--
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