Seeking in paused might be unreliable and lead to a sensible position offset
Submitted by Thibault Saunier @thiblahute
Link to original bug (#771122)
Description
When seeking on files containing mp3 stream (it seems to happen only in that case, but that might be wrong) position sometimes is not accurate and lead to the following error in validate:
==== Got criticals, Return value set to 18 ====
Critical error Reported position after accurate seek in PAUSED state should be exactly what the user asked for 0:00:00.250000000 != 0:00:00.200000000