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 345365 - [id3mux] pushes buffers that don't match src caps
[id3mux] pushes buffers that don't match src caps
Status: RESOLVED DUPLICATE of bug 323658
Product: GStreamer
Classification: Platform
Component: gst-plugins-ugly
git master
Other Linux
: Normal normal
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Reported: 2006-06-20 02:09 UTC by Nguyen Thai Ngoc Duy
Modified: 2006-06-30 17:07 UTC
See Also:
GNOME target: ---
GNOME version: ---

GST_DEBUG=*:4 GST_DEBUG_NO_COLOR=1 rhythmbox >rb.log 2>&1 (282.18 KB, application/octet-stream)
2006-06-20 02:11 UTC, Nguyen Thai Ngoc Duy

Description Nguyen Thai Ngoc Duy 2006-06-20 02:09:54 UTC
I can no longer edit tags with rhythmbox. It seems to refuse to modify
any file with message "File corrupted during write". In terminal I
(rhythmbox-metadata:19102): GStreamer-CRITICAL **:
gst_pad_activate_pull: assertion `old == GST_ACTIVATE_NONE' failed
I'm using gstreamer-0.10.8,  gst-plugins-{good,bad,ugly}-0.10.3.
Comment 1 Nguyen Thai Ngoc Duy 2006-06-20 02:11:10 UTC
Created attachment 67663 [details]
GST_DEBUG=*:4 GST_DEBUG_NO_COLOR=1 rhythmbox >rb.log 2>&1
Comment 2 Michael Gorbach 2006-06-20 15:11:53 UTC
Identical problem here ... same symptoms.
Same error on console.
Comment 3 Jonathan Matthew 2006-06-25 00:38:49 UTC
The log shows you're using id3mux instead of the preferred id3v2mux.  Installing id3v2mux (from gst-plugins-good) will most likely fix this for you.

Every time id3mux receives a buffer, this happens:

      id3demux( 9675) gstid3demux.c(518):gst_id3demux_chain:<id3demux0> Pushing buffer 0x81294f8
      GST_PADS( 9675) gstpad.c(3343):gst_pad_push:<id3tag0:src> caps changed to audio/mpeg, mpegversion=(int)1, layer=(int)3
      GST_CAPS( 9675) gstpad.c(2124):gst_pad_accept_caps: pad accept caps of id3tag0:src (0x80fee10)
      GST_CAPS( 9675) gstpad.c(1928):gst_pad_get_caps: get pad caps of id3tag0:src (0x80fee10)
      GST_CAPS( 9675) gstpad.c(1833):gst_pad_get_caps_unlocked: get pad caps of id3tag0:src (0x80fee10)
      GST_CAPS( 9675) gstpad.c(1836):gst_pad_get_caps_unlocked: dispatching to pad getcaps function
      GST_CAPS( 9675) gstpad.c(1850):gst_pad_get_caps_unlocked: pad getcaps id3tag0:src returned application/x-id3
      GST_CAPS( 9675) gstpad.c(2323):gst_pad_configure_src: caps audio/mpeg, mpegversion=(int)1, layer=(int)3 not accepted
GST_SCHEDULING( 9675) gstpad.c(3381):gst_pad_push:<id3tag0:src> element pushed buffer then refused to accept the caps

which looks like id3mux is not setting caps on its buffers and/or pads correctly.
Comment 4 Tim-Philipp Müller 2006-06-25 08:52:03 UTC
> which looks like id3mux is not setting caps on its buffers and/or pads
> correctly.

Indeed. It's fixed in CVS AFAIK.

*** This bug has been marked as a duplicate of 323658 ***
Comment 5 Nguyen Thai Ngoc Duy 2006-06-26 03:01:27 UTC
Should we only use id3mux > 0.10.3 then?
Comment 6 Tim-Philipp Müller 2006-06-30 17:07:56 UTC
> Should we only use id3mux > 0.10.3 then?

You should preferably use the taglib-based id3v2mux element from gst-plugins-good :)

If you insist on id3mux, you should bump the requirement to 0.10.4 once gst-plugins-ugly 0.10.4 is released (don't know when that will be).