GNOME Bugzilla – Bug 656345
[discoverer] Avoid decoding where possible
Last modified: 2018-11-03 11:19:07 UTC
Assuming tagreadbin as (give or take) in bug #564749 ever makes it into -base, some minor adjustments to discoverer allow using tagreadbin (in turn using a.o. uridecodebin) rather than uridecodebin directly. While in this mode not all features may be extracted (e.g. no stream topology), it brings some tagreadbin advantages, e.g. typically no decoders are involved. Patches available in http://cgit.collabora.com/git/user/manauw/gst-plugins-base.git/log/?h=tagreading
FTR, minor update has been done to aforementioned branch. Any chance for review/movement in this area (and related tagreading) ?
FTR, another update has been done on branch in question. That is, even when discoverer is using tagreadbin, topology info will now also be extracted/provided. Note, however, a side-effect of this is that the previous tentative API/flags/enum controlling whether or not to employ tagreadbin has been changed.
Now that we have parsers for most common formats, it would be as efficient to stop auto-plugging once we have a parser plugged in. Furthermore those parsers will only set caps and start outputting once they have all/most information. We would reach the same result (tags/metadata without decoding for formats that have parsers) and more (extract information for formats that don't have a parser). Furthermore it would concentrate all the information/logic into one single/reused location (the parsers).
*** Bug 770137 has been marked as a duplicate of this bug. ***
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-base/issues/50.