GNOME Bugzilla – Bug 598147
mpegtsmux failing to mux an incoming RTP MP4V-ES stream in a TS file
Last modified: 2011-05-23 12:56:26 UTC
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
I tried the following workaround: Changed the video format to MPEG2 Video. Following changes: * using mpegtsmux gives the same problem * using flutsmux instead of mpegtsmux with the MPV gives a segmentation fault: <snip> 0:00:17.342385536 30022 0x232d7a0 WARN rtpjitterbuffer rtpjitterbuffer.c:198:calculate_skew: Clock rate changed from 4294967295 to 90000 0:00:17.577505007 30022 0x232d7a0 WARN basesrc gstbasesrc.c:2378:gst_base_src_loop:<trans_v_udpsrc_1000> error: Internal data flow error. 0:00:17.577544187 30022 0x232d7a0 WARN basesrc gstbasesrc.c:2378:gst_base_src_loop:<trans_v_udpsrc_1000> error: streaming task paused, reason not-linked (-1) [DEBUG] Stream (nil) error: Internal data flow error. Segmentation fault (core dumped) </snip> Regards
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 576524 ***