GNOME Bugzilla – Bug 795290
gstplayer: not be able to set_seek_accurate() in playing state after API changing.
Last modified: 2018-11-03 14:21:29 UTC
Hi Slomo, I was doing the upgrade of GST1.12 to GST1.14 recently. And I noticed that gstplayer API gst_player_config_set_seek_accurate() is changed from gst_player_config_set_seek_accurate (GstPlayer * self, gboolean accurate) to gst_player_config_set_seek_accurate (GstStructure * config, gboolean accurate) on GST1.14 So in GST1.14, if we need to set accurate seek flag, we need to _get_config(), and after set_accurate_seek(), then _set_config() back. However, in _set_config(), it only allows config setting when app_state is STOPPED. But actually when we trying to seek to some point when playing, we prefer not stop playing first and then switch back to playing again, we just set_aacurate_seek flag and do seek. in previous GST1.12, we just need set_accurate_seek flag and then seek. Do you have any suggestion for this issue?
Should we just use previous api, (we can just set the config flag via * gstplayer )?
What's the use-case for sometimes doing accurate seeks and sometimes not in the same run?
in our command line app, we just let users choose seek mode each time before seek, fast seek or accurate seek. When users choose fast seek mode, will set accurate seek mode to FALSE otherwise will set accurate seek flag to TRUE, and then start seeking. So user will choose this flag when pipeline is in playing state before seeking.
-- 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-plugins-bad/issues/690.