[gstreamer-bugs] [Bug 358040] New: Can't receive speex rtp in the middle of a stream

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=358040

GStreamer | gstreamer (core) | Ver: 0.10.10

           Summary: Can't receive speex rtp in the middle of a stream
           Product: GStreamer
           Version: 0.10.10
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: justin at affinix.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


We were talking about this problem in #farsight today.  I noticed that if I
started an rtp speex stream, I have to start the receiver before I start the
sender, otherwise the receiver quits with an error.

I'm not sure if this is a bug in the speex encoder, or the rtp payloader, or
wherever, so I'm reporting this bug to gstreamer itself and hopefully it'll get
routed right.

Here's the receiver's error output:

gst-launch-0.10 udpsrc port=60000 ! application/x-rtp,clock-rate=8000 !
rtpspeexdepay ! speexdec ! audioconvert ! audioresample ! osssink sync=false
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
warning: This doesn't look like a Speex file
ERROR: from element /pipeline0/speexdec0: Could not decode stream.
Additional debug info:
gstspeexdec.c(505): speex_dec_chain_parse_header (): /pipeline0/speexdec0:
couldn't read header
Execution ended after 4206000 ns.
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
FREEING pipeline ...


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.