FaSTTUBe/GST-Tensordecoder-ov_ep
37
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Explain step vs seek to change playback speed change

Browse Source
This commit is contained in:
Olivier Crête 2016-10-25 16:20:37 -04:00
parent 0239c097a7
commit 8be9a06c0c
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
sdk-basic-tutorial-playback-speed.md
View File

@ -34,11 +34,15 @@ In [](sdk-basic-tutorial-time-management.md) seek
events have already been shown, using a helper function to hide their events have already been shown, using a helper function to hide their
complexity. This tutorial explains a bit more how to use these events. complexity. This tutorial explains a bit more how to use these events.
Step Events are a more convenient way of changing the playback rate, due Step Events are a more convenient way of changing the playback rate,
to the reduced number of parameters needed to create them; however, due to the reduced number of parameters needed to create them;
their implementation in GStreamer still needs a bit more polishing however, they have some downsides, so Seek Events are used in this
so Seek Events are used in this tutorial instead. tutorial instead. Step events only affect the sink (at the end of the
**FIXME: Is that even true ???** pipeline), so they will only work if the rest of the pipeline can
support going at a different speed, Seek events go all the way through
the pipeline so every element can react to them. The upside of Step
events is that they are much faster to act. Step events are also
unable to change the playback direction.
To use these events, they are created and then passed onto the pipeline, To use these events, they are created and then passed onto the pipeline,
where they propagate upstream until they reach an element that can where they propagate upstream until they reach an element that can