[gstreamer-bugs] [Bug 551580] problems with lame ! ffmux_mpeg

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=551580

  GStreamer | gst-ffmpeg | Ver: 0.10.x

Tim-Philipp Müller changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |t.i.m at zen.co.uk
             Status|UNCONFIRMED                 |NEW
          Component|don't know                  |gst-ffmpeg
     Ever Confirmed|0                           |1
            Summary|Internal GStreamer error:   |problems with lame !
                   |negotiation problem         |ffmux_mpeg




------- Comment #1 from Tim-Philipp Müller  2009-05-31 19:35 UTC -------
Looks like some element (lame presumably) doesn't set caps on the outgoing
buffers. I'm not aware of this being a problem otherwise, so maybe the bug is
elsewhere - I think we would have noticed before if this was in fact the
problem.

With git of things, I get for

 $ gst-launch-0.10 audiotestsrc ! lame ! mp3parse ! ffmux_mpeg ! fakesink

just an endless stream of error debug messages:
:00:00.304304059 12855       0x7e5bf0 ERROR               ffmpeg :0:: buffer
underflow i=0 bufi=339 size=418

Do you get those as well if you run gst-launch with

  $ GST_DEBUG=*:1 gst-launch-0.10 ...


Btw (unrelated, I think, but still):

 - the video framerate is set via the "framerate"
   field, not the "rate" field (re. the capsfilter
   after videorate)

 - you don't need the audio/mpeg capsfilter after
   lame, but you might need/want an mp3parse


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=551580.