GNOME Bugzilla – Bug 577893
Playback slows down (damaged MPEG header?)
Last modified: 2011-08-19 23:36:38 UTC
Please describe the problem: watching a movie on Totem, if I fast fw a few minutes, the video will slow down, and never playback at correct speed. Steps to reproduce: 1. open a movie 2. fast fw 3. resume play Actual results: totem plays back at a slower speed Expected results: normal playback Does this happen every time? yes Other information:
linked to Launcpad https://bugs.launchpad.net/ubuntu/+source/totem/+bug/353444
Created attachment 132046 [details] $ GST_DEBUG_NO_COLOR=1 GST_DEBUG=*:2 totem 2> logtotem
Created attachment 132047 [details] $ GST_DEBUG_NO_COLOR=1 GST_DEBUG=*:2 totem-xine 2> logtotem-xine tried also with totem-xine and got a different bug: audio gets out of sinc, but video playback is ok,
xine's saying the MPEG header is damaged, but I'll pass this to the GStreamer people to see if they can do anything to improve GStreamer's behaviour in this situation. Could you provide a more detailed GStreamer log, with the following command? GST_DEBUG_NO_COLOR=1 GST_DEBUG=*:5 totem 2> totem.log Would you also be able to provide a movie file which displays this behaviour, or at least the first 50KiB of one (use the following command)? head -c 50kB file.mpg > header.mpg GStreamer plugin versions (from Launchpad report): gstreamer0.10-plugins-base 0.10.22-4 gstreamer0.10-plugins-good 0.10.14-1 Note also that there's a more detailed log from xine available on the Launchpad report: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/353444/comments/3
i'm having trouble reproducing this now. I got w64codecs upgrade, not sure if that changed something I'm attaching 2 new logs with the test solicited
ok I take it back... it generated a 270MiBs and one 720MiBs logs!!! those are not suitable to upload via 3G eheh Do you have any idea why this logs are so big? i ran: GST_DEBUG_NO_COLOR=1 GST_DEBUG=*:5 totem 2> totem.log
Can you make the file available? And is this still happening with the latest releases? It's normal that the logs are that large, you could compress them with bzip2. The logs are usually good to compress
BUGabundo, will you please provide the information requested in comment#7 ?
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!