Sebastian Dröge b9a4a2a952 basesink: Update start time when losing state only if we were in PLAYING ... If we were in PAUSED, the current clock time and base time don't have much to do with the running time anymore as the clock might have advanced while we were PAUSED. The system clock does that for example, audio clocks often don't. Updating the start time in PAUSED will cause a) the wrong position to be reported, b) step events to step not just the requested amount but the amount of time we spent in PAUSED. The start time should only ever be updated when going from PLAYING to PAUSED to remember the current running time (to be able to compensate later when going to PLAYING for the clock time advancing while PAUSED), not when we are already in PAUSED. Based on a patch by Kishore Arepalli <kishore.arepalli@gmail.com> The updating of the start time when the state is lost was added in commit ba943a82c0 to fix the position reporting when the state is lost. This still works correctly after this change. https://bugzilla.gnome.org/show_bug.cgi?id=739289		2016-06-13 20:20:44 +02:00
..
base	basesink: Update start time when losing state only if we were in PLAYING	2016-06-13 20:20:44 +02:00
check	g-i: pass compiler env to g-ir-scanner	2016-05-24 00:40:27 +01:00
controller	g-i: pass compiler env to g-ir-scanner	2016-05-24 00:40:27 +01:00
helpers	helpers: really fix install race	2015-12-04 16:44:39 +02:00
net	Use MAY_BE_LEAKED_FLAG	2016-06-02 23:14:15 +01:00
Makefile.am	Remove obsolete Android build cruft	2015-04-26 17:49:44 +01:00