[Bug 760590] New: query: recursive accept-caps query
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Wed Jan 13 10:28:45 PST 2016
https://bugzilla.gnome.org/show_bug.cgi?id=760590
Bug ID: 760590
Summary: query: recursive accept-caps query
Classification: Platform
Product: GStreamer
Version: git master
OS: All
Status: NEW
Severity: enhancement
Priority: Normal
Component: gstreamer (core)
Assignee: gstreamer-bugs at lists.freedesktop.org
Reporter: thiagossantos at gmail.com
QA Contact: gstreamer-bugs at lists.freedesktop.org
CC: christophevr at telenet.be, slomo at coaxion.net,
thiagossantos at gmail.com
Depends on: 760477
GNOME version: ---
+++ This bug was initially created as a clone of Bug #760477 +++
As we are replacing the current misused accept-caps queries we noticed that
there is a certain feature gap.
Before we were believing that using an accept-caps query would cause all the
pipeline downstream to verify if it would be able to accept a certain caps but
the accept-caps was created to be a pre-check of a caps event and only goes to
the next element.
Right now we have replaced accept-caps with a caps query +
gst_caps_can_intersect() or gst_caps_is_subset() but for some elements we need
to do a is_subset() while for others an intersect is enough.
Perhaps we should have a 'recursive' flag to a accept-caps query?
If we decide to do this in 1.x, we keep the current behavior and enable the
flag when needed. Every baseclass and lots of elements out there will need to
be updated so I'm not sure if this is a backwards compatible change.
Decided to open a bug so we can discuss and, if we defer it to 2.0, we can mark
it as so to discuss it again once the time arrives.
--
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