GNOME Bugzilla – Bug 330623
[avidemux] only the beginning of big avi files gets played
Last modified: 2006-06-23 07:10:28 UTC
I have captured a big avi file with mencoder. When I use totem to watch it playback works fine but seeking doesn't. It just stops playing. size: 1.1GB duration: 4min 40sec video: MJPEG, 720x576, 25fps audio: PCM, 32kHz With mplayer, xine and vlc seekings works.
Can you please confirm if you still have this problem with gst-plugins-good 0.10.3 released yesterday?
Current version of plugins-good is 0.10.2, plugins-base is at 0.10.3!
oh, bleh - sorry :) this could be a dup of bug #154744
I did some tests and it seems to be a bug in gst-ffmpeg (mjpeg decoder). Nevertheless avidemux HAS some problems with big files. I converted the file mentioned above with ffmpeg: $ ffmpeg -i mjpeg.avi -vcodec rawvideo -acodec copy uncompressed.avi The resulting file size is 4.1GB. When I try to play this file, totem displays a duration of 1min 8sec (should be 4min 40sec) and only plays it this far. Other players (mplayer, xine, vlc) have no problems. You can use ffmpeg or mencoder to produce your own samples as I think it would not be such a good idea to upload huge files like this. :)
seems like an opendml file (for > 2gb files), I thought there was support for that in avidemux though.
On the one hand, it does look like typical behaviour of an avi file (demuxer) of which only the first RIFF chunk is being recognized as having a (traditional) index. On the other hand, I also did some tests on this but was not able to reproduce the problem using: gst-plugins-good 0.10.3 and 3h MPEG4 avi (up to 7GB) or 10 min rawvideo 3.7GB avi (avi produced by ffmpeg build4718, transcode or gstreamer). Though it was not tested using totem (need to upgrade my system :) ), a gst-launch pipeline processes the whole avi file, can handle a seek (even to the end of the file) and the progressreport element shows the full duration of the file, and the latter should get this info from the same place as totem does.
Peter, anything new here? Could you try again with -good CVS by any chance? (There have been quite a few fixes for MJPEG stuff IIRC).
It works now (MJPEG and big AVI files).
Closing now the reporter of the bug confirmed it works for him.