[gstreamer-bugs] [Bug 598147] New: mpegtsmux failing to mux an incoming RTP MP4V-ES stream in a TS file

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=598147
  GStreamer | gst-plugins-bad | 0.10.14

           Summary: mpegtsmux failing to mux an incoming RTP MP4V-ES
                    stream in a TS file
    Classification: Desktop
           Product: GStreamer
           Version: 0.10.14
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-bad
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: jordijp at gmail.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
      GNOME target: ---
     GNOME version: ---


Hi,

that's how you can reproduce the bug:

I am testing with a ubuntu 9.10 karmic koala beta with gst-plugins-bad updated
to the 0.10.14 version.

First issue a video stream and send it to one local port:

gst-launch-0.10 -v videotestsrc ! video/x-raw-yuv, width=640, height=480 !
videoscale ! ffmpegcolorspace ! ffenc_mpeg4 ! rtpmp4vpay send-config=true !
udpsink port=5000

Then receive and mux into the MPEG-TS file:

gst-launch-0.10 -v udpsrc port=5000 ! application/x-rtp, media=video,
clock-rate=90000, encoding-name=MP4V-ES, payload=96,
profile-level-id=\(string\)1 ! gstrtpjitterbuffer ! rtpmp4vdepay !
mpeg4videoparse ! mpegtsmux ! filesink location=pepet.ts

The file 'pepet.ts' created with this pipeline is not working whereas the
pipeline below is working:

gst-launch-0.10 -v udpsrc port=5000 ! application/x-rtp, media=video,
clock-rate=90000, encoding-name=MP4V-ES, payload=96,
profile-level-id=\(string\)1 ! gstrtpjitterbuffer ! rtpmp4vdepay !
mpeg4videoparse ! avimux ! filesink location=pepet.mp4

Please let me know any suggestions you may have to solve this issue and I will
try them ASAP.

Best regards,

Jordi

-- 
Configure bugmail: https://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.