After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 770202 - GstStream, GstStreamCollection: what about global tags ?
GstStream, GstStreamCollection: what about global tags ?
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other All
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-08-21 14:55 UTC by Tim-Philipp Müller
Modified: 2018-11-03 12:35 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tim-Philipp Müller 2016-08-21 14:55:54 UTC
So GstStream stores the stream tags for a stream, which makes sense.

Question is whether we should also put the global tags somewhere. Perhaps they should be put into the collection? (and merged if there are multiple differing ones)

+++ This bug was initially created as a clone of Bug #770053 +++
Comment 1 Sebastian Dröge (slomo) 2017-01-21 11:14:09 UTC
I think storing it in the stream collection is not ideal, unless you store it in another "container" struct like GstStream that allows modifications. The stream collection is immutable, the streams are not (details can be added e.g.). And the (global) tags are similar in this regard, they could be updated along the way or even by the same element later.

However conceptually it seems to belong into the stream collection, so maybe we indeed need some kind of GstStreamGlobalTags that is reference counted, properly locked, and allows setting/getting taglists.
Comment 2 Sebastian Dröge (slomo) 2017-01-21 11:16:13 UTC
Or GstStreamCollectionDetails, to keep it more generic. One might want to add other things in there at a later time.
Comment 3 Sebastian Dröge (slomo) 2017-02-08 17:54:10 UTC
It could of course also just be a getter/setter for the taglist itself. While the streams array in the collection is supposed to be immutable (i.e. no new streams added/removed), the streams themselves can change. And allowing a taglist to be changed in the collection (in a thread-safe way) is not very different in that regard.

The important part about the immutability here is that streams don't appear or disappear.
Comment 4 GStreamer system administrator 2018-11-03 12:35:51 UTC
-- 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/gstreamer/issues/185.