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 738575 - matroskamux: Empty TAGS section if no valid MKV Tags are present
matroskamux: Empty TAGS section if no valid MKV Tags are present
Status: RESOLVED DUPLICATE of bug 762349
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
1.4.3
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-10-15 13:38 UTC by clowd81
Modified: 2018-05-06 14:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description clowd81 2014-10-15 13:38:03 UTC
In the matroskamux plugin, upon receiving an EOS it closes out the file, writing various data, including a TAGS section.  The code to write this TAGS section will write the header for the section to the file even if there are no valid matroska tags in the tag list.  

This is because in matroska-mux.c, in the gst_matroska_mux_finish() function, it checks to make sure tags != NULL, then writes the headers, then iterates through the tag_list and attempts to write each tags to file.  However, the code to write the tags - gst_matroska_mux_write_simple_tag() - will only write 15 specific tags to this section.  If none of those tags exist, the result is an empty TAGS section with the headers indicating that there should be data available.  This causes errors to be reported in several matroska validators.

A workaround is to use the following:

GstTagSetter *tagsetter = GST_TAG_SETTER(mux);
gst_tag_setter_reset_tags(tagsetter);
Comment 1 Tim-Philipp Müller 2018-05-06 14:55:49 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed in the code repository.

*** This bug has been marked as a duplicate of bug 762349 ***