After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 633906 - VLC breaks while playing mpeg2 ts stream generated by ffmux_mpegts
VLC breaks while playing mpeg2 ts stream generated by ffmux_mpegts
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-libav
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-11-03 13:10 UTC by kapil
Modified: 2011-12-22 04:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description kapil 2010-11-03 13:10:35 UTC
If we generate a ts stream with

gst-launch-0.10 videotestsrc ! ffenc_mpeg2video bitrate=2000000 rc-max-rate=2000000 rc-min-rate=2000000 rc-buffer-size=183500 ! queue ! ffmux_mpegts name=mux ! filesink location=/tmp/test-gst.ts -v audiotestsrc ! audio/x-raw-int, rate=48000, channels=2 ! audioconvert ! ffenc_mp2 ! queue ! mux.


the test-gst.ts stream breaks after sometime while playing back using vlc.

if you use vlc -vvv you can see the problem that the pts values are not properly assigned in ts packets by ffmux_mpegts.

Also if we generate a test-ffmpeg.ts using ffmpeg commandline 

./ffmpeg -i ~/test.flv -vcodec mpeg2video -bufsize 1835008 -b 2000000 -maxrate 2000000 -minrate 2000000 -acodec mp2 -f mpegts -muxrate 3000000 /tmp/test-ffmpeg.ts

it plays perfectly with vlc.


Suspected Issue:
  There is a difference in the way ffmpeg assigns pts values & the way gst-ffmpeg does. It seems gst-ffmpeg is doing something wrong.

Can someone please look in the issue.
Comment 1 David Schleef 2011-09-24 23:52:08 UTC
What happens if you use mpegtsmux instead?
Comment 2 Akhil Laddha 2011-11-10 05:17:14 UTC
kapil, can you please respond to comment#1 ?
Comment 3 Akhil Laddha 2011-12-22 04:40:31 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!