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 343009 - movie jumps forward when unpausing
movie jumps forward when unpausing
Status: RESOLVED DUPLICATE of bug 417992
Product: totem
Classification: Core
Component: GStreamer backend
2.16.x
Other All
: Normal normal
: ---
Assigned To: Maintainer alias for GStreamer component of Totem
Maintainer alias for GStreamer component of Totem
Depends on:
Blocks:
 
 
Reported: 2006-05-26 10:41 UTC by Teppo Turtiainen
Modified: 2007-06-11 13:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Teppo Turtiainen 2006-05-26 10:41:47 UTC
Please describe the problem:
When I pause a movie and then "unpause" it, the movie jumps slightly forward.

Steps to reproduce:
1. Pause a movie (the problem is easy to see if you pause when there is fast
movement on the movie).
2. Unpause/resume playback.


Actual results:
The movie jumps forward about half a second.

Expected results:
Playback resumes exactly where it left off.

Does this happen every time?
Yes.

Other information:
Using Totem 1.4.1 and GStreamer 0.10.6 on an up-to-date Ubuntu Dapper. Bug
315900 is similar to this one.
Comment 1 Teppo Turtiainen 2006-12-04 18:06:10 UTC
Still here with Totem 2.16.2 and GStreamer 0.10.10 on Ubuntu Edgy. The jump isn't really half a second, it is more like a couple of frames, but the issue is quite noticeable when there is fast movement in the movie.
Comment 2 Philip Withnall 2007-06-10 13:09:09 UTC
What's the codec and container of the videos with which this happens (or does it happen with every format of video)?
Comment 3 Tim-Philipp Müller 2007-06-11 13:44:59 UTC
I think this is a duplicate of or related to bug #417992, which has been fixed in the latest release. Please re-open if you still have this issue with core/-base 0.10.13 or newer.


*** This bug has been marked as a duplicate of 417992 ***