[gstreamer-bugs] [Bug 328531] New: matroskamuxer goes Streamer-CRITICAL **: gst_segment_set_newsegment

[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=328531
 GStreamer | gst-plugins-good | Ver: 0.10.2

           Summary: matroskamuxer goes Streamer-CRITICAL **:
                    gst_segment_set_newsegment
           Product: GStreamer
           Version: 0.10.2
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: critical
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: nopa90 at gmail.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Please describe the problem:
(gst-launch-0.10:740): GStreamer-CRITICAL **: gst_segment_set_newsegment:
assert
ion `segment->format == format' failed

Steps to reproduce:
1. gst-launch filesrc location=ccc.ogg ! decodebin name=decoder decoder. !
queue! audioconvert ! vorbisenc ! matroskamux ! filesink location=rip.mkv
2. gst-launch filesrc location=ccc.ogg ! decodebin name=decoder decoder. !
ffmpegcolorspace ! xvidenc ! matroskamux ! filesink location=rip.mkv
3. 


Actual results:
(gst-launch-0.10:740): GStreamer-CRITICAL **: gst_segment_set_newsegment:
assert
ion `segment->format == format' failed

Expected results:


Does this happen every time?
yes

Other information:
recompiled matroskamux with -g flag

in ebml-write.c (line 390) 
seek = gst_event_new_new_segment (FALSE, 1.0, GST_FORMAT_BYTES, pos, -1, 0);
  peer_pad = GST_PAD_PEER (ebml->srcpad);
  if (peer_pad) {
    gst_pad_send_event (peer_pad, seek); <--- problem is from here
  } else {
    GST_WARNING_OBJECT (ebml, "Can not seek: no peer pad");


-- 
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.