[Bug 746373] New fundamental type for caps - GstFlagSet
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Thu Mar 19 13:30:50 PDT 2015
https://bugzilla.gnome.org/show_bug.cgi?id=746373
--- Comment #28 from Olivier CrĂȘte <olivier.crete at ocrete.ca> ---
The problem is that writing the binary form in the pad templates is not
trivial, and it's quite easy to get it wrong. The serialized form is mostly for
humans, to write caps by hand and such, wasting a bit of CPU time parsing it
seems like no problem at all Having the information duplicated means that it's
almost guaranteed to get out of sync. If you start with 011:010:myflag, it's
way to end up with something like 011:110:+myflag,/myflag2, which looks ok to
human readers, but actually is parsed to something else. Not being usable from
gst-launch would be a big regression. Possibly they should just be registered
in the core.
How many of these flags do you have? Is the overhead from using a couple of
G_TYPE_BOOLEAN so much?
--
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