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 110544 - plugin/app metadata handling
plugin/app metadata handling
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins
0.6.1
Other All
: Normal enhancement
: 0.7.x
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 104345 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-04-11 11:48 UTC by Benjamin Otte (Company)
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Attachments
untested patch (no vorbis here) (1.46 KB, patch)
2003-04-11 11:49 UTC, Benjamin Otte (Company)
none Details | Review

Description Benjamin Otte (Company) 2003-04-11 11:48:47 UTC
Vorbis tag names are defined somewhere and there is no support for
arbitrary comments. Each tag must be in the form A=b.
See attached patch.
Comment 1 Benjamin Otte (Company) 2003-04-11 11:49:24 UTC
Created attachment 15639 [details] [review]
untested patch (no vorbis here)
Comment 2 Ronald Bultje 2003-04-12 14:41:31 UTC
This patch (the A=b part) actually works around the issue. For
GStreamer, the application is not supposed to know what specific type
of metadata the plugin/file expects. So an app can just set a=b as
metadata, and if the format is supposed to care, then it should set
caps itself.

So the upper part of the patch would have to be removed, and the
bottom part would have to be changed to set the name to capitals and
move that over to vorbis' lib.

do others agree here?
Comment 3 Ronald Bultje 2003-04-12 15:21:54 UTC
After discussion, only the second part has been applied. I'll leave
this one open for further discussion on who should do
metadata-formatting: app or plugin (plugin imho) and what fields of
metadata we actually support (that needs to be documented).
Comment 4 Ronald Bultje 2003-06-30 22:11:01 UTC
*** Bug 104345 has been marked as a duplicate of this bug. ***
Comment 5 David Schleef 2003-12-02 01:58:58 UTC
Can this be closed now that we have tags?
Comment 6 Benjamin Otte (Company) 2003-12-02 11:53:18 UTC
Yes, it can.
As lonmg as it doesn't need to be fixed in 0.6, but I don't think we will.