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 368420 - id3tag doesn't work behind xingmux
id3tag doesn't work behind xingmux
Status: RESOLVED DUPLICATE of bug 335515
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
0.10.4
Other All
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-31 17:53 UTC by Alexander Tschache
Modified: 2006-10-31 23:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Alexander Tschache 2006-10-31 17:53:06 UTC
Please describe the problem:
audio/x-raw-int,rate=44100,channels=2 ! lame name=enc quality=0 vbr=4 vbr-quality=3 ! id3mux
When using Sound Juicer this line produces the expected VRB mp3 with bogus duration and bitrate, however id3 tag info is a-ok.
audio/x-raw-int,rate=44100,channels=2 ! lame name=enc quality=0 vbr=4 vbr-quality=3 ! xingmux ! id3mux
This line produces the same VBR mp3 with the proper bitrate value, however the duration given by Nautilus' file dialog is still wrong and no id3 tag information was added.

Steps to reproduce:
1. Encode a VBR mp3 with the lame module, pipe it through id3tag, recieve a properly tagged file
2. Put xingmux between the lame module and id3mux, recieve a file with the proper bitrate but without tagging


Actual results:
No id3 tag is added while the bitrate is corrected.

Expected results:
The bitrate is corrected and id3 tag information added.

Does this happen every time?
Yes.

Other information:
Running gentoo unstable, gstreamer-0.10.10, gst-plugins-good-0.10.4, gst-plugins-bad-0.10.3
Comment 1 Tim-Philipp Müller 2006-10-31 19:22:05 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

(id3mux isn't really supported any longer, please use the id3v2mux element from -good instead, that one should work fine)


*** This bug has been marked as a duplicate of 335515 ***
Comment 2 Alexander Tschache 2006-10-31 21:21:45 UTC
Thank you for your response, yet
gst-inspect-0.10 | grep id3
only reports id3mux, but not id3v2mux. Is this a CVS-only change for the moment (running gst-plugins-good-0.10.4)?
Comment 3 Tim-Philipp Müller 2006-10-31 23:14:23 UTC
> Thank you for your response, yet
> gst-inspect-0.10 | grep id3
> only reports id3mux, but not id3v2mux. Is this a CVS-only change for the moment
> (running gst-plugins-good-0.10.4)?

The taglib plugin containing id3v2mux has been in -good for a while now IIRC (I think since 0.10.3). Possible that whatever package you're using isn't built containing the taglib plugin though.