GNOME Bugzilla – Bug 609520
[ffdemux_mpeg] freezes when demuxing a file
Last modified: 2010-06-17 12:01:35 UTC
This pipeline freezes: gst-launch-0.10 filesrc location=video ! ffdemux_mpeg ! ffdec_h264 ! xvimagesink I am not sure but probably the problem is with ffdemux_mpeg. I am using packages from Ubuntu 9.10 official repository. Problematic video: http://www.megaupload.com/?d=SBT0HFEP
Could you please just attach the file next time. megaupload is a PITA to use.
Works fine using regular (non-ffmpeg) demuxer. Why not use that one instead ?
I used megaupload because the file is bigger than 1MB. About the element mpegpsdemux i opened the bug report https://bugzilla.gnome.org/show_bug.cgi?id=609408. At the moment this bug is not fixed for me. The motivation behind fixing this bug is because there could be a bug in ffmpeg/gstreamer layer. So, it could affect other ffmpeg elements that doesn't have an alternate element.
(In reply to comment #3) > I used megaupload because the file is bigger than 1MB. Oh, I thought the limit was 10MB. Sure, but use a regular http hosting solution next time. Waiting a minute decreases the motivation to fix the bug even more :) > > About the element mpegpsdemux i opened the bug report > https://bugzilla.gnome.org/show_bug.cgi?id=609408. At the moment this bug is > not fixed for me. > > The motivation behind fixing this bug is because there could be a bug in > ffmpeg/gstreamer layer. So, it could affect other ffmpeg elements that doesn't > have an alternate element. It's exhibiting the same timestamp issues as the -bad mpegpsdemux, therefore it's not a 'gst-ffmpeg' issue but rather an issue with the actual ffmpeg mpegps demuxer implementation. Since we don't have control over the ffmpeg code, we can't really do much in that regards. I'll mark this as a duplicate of the mpegpsemux bug so that we can at least fix that behaviour in the -bad demuxer. *** This bug has been marked as a duplicate of bug 609408 ***
For what i can see mpegpsmux implementation (the one in bad) does not use ffmpeg internally. So i think that even though the issue is the same (bad timestamps) the bugs are different.
Your file is busted. It requires proper handling at much lower levels than what the *GSTREAMER* part of gst-ffmpeg controls => it requires fixing in libavformat. Since we don't control libavformat, you'll have to file a bug with them to have this fixed. Since we do control the whole of mpegpsdemux, we can (hopefully) fix it in -bad.