GNOME Bugzilla – Bug 771122
Seeking in paused might be unreliable and lead to a sensible position offset
Last modified: 2018-11-03 12:53:23 UTC
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 https://ci.gstreamer.net/job/GStreamer-master-validate/3710/testReport/junit/ges.playback.scrub_forward_seeking.test_mixing/audio_only/mp3_h264_mp4/
The bug seems to be due to the fact that the seek from 0.2 end=0.25 on the audio track pushes EOS instantly and does not output any sample (leading to NLE building the next pipeline)
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-editing-services/issues/27.