mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2024-11-27 12:11:13 +00:00
c53989742b
Original commit message from CVS: * docs/random/ensonic/dynlink.txt: * docs/random/ensonic/interfaces.txt: * docs/random/ensonic/receipies.txt: Possible dynamic reconnection api, plus some type fixes the other two docs.
37 lines
840 B
Text
37 lines
840 B
Text
$Id$
|
|
|
|
= receipies =
|
|
|
|
The idea is to collect some recommendations for common, but not so trivial
|
|
tasks. docs/design/part-block.txt has something like that already. Ideally these
|
|
would go to the application developer manual and there would be sample code.
|
|
|
|
== initial seeking ==
|
|
=== question ===
|
|
How to I configure the initial playback segment?
|
|
|
|
=== idea ===
|
|
1) set pipeline to PAUSED
|
|
2) send seek event
|
|
3) set pipeline to PLAYING
|
|
|
|
=== problems ===
|
|
1) would preroll the pipeline only, to flush it when the seek comes
|
|
|
|
|
|
== async state changes ==
|
|
=== question ===
|
|
what to do when gst_element_set_state() returns ASYNC?
|
|
|
|
=== idea ===
|
|
1) listen to the STATE_CHANGED message on the bus
|
|
2) trigger next action
|
|
|
|
=== problems ===
|
|
This scatters logic over multiple functions (callbacks).
|
|
|
|
|
|
== topic ==
|
|
=== question ===
|
|
=== idea ===
|
|
=== problems ===
|