mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2025-01-31 11:32:38 +00:00
docs: flesh out typefindelement docs some more
Mention that have-type signal may be emitted from streaming thread or application thread, and fix a typo.
This commit is contained in:
parent
eed2a350cb
commit
af0642b6e8
1 changed files with 5 additions and 3 deletions
|
@ -26,7 +26,9 @@
|
|||
* to the found media type.
|
||||
*
|
||||
* Whenever a type is found the #GstTypeFindElement::have-type signal is
|
||||
* emitted.
|
||||
* emitted, either from the streaming thread or the application thread
|
||||
* (the latter may happen when typefinding is done pull-based from the
|
||||
* state change function).
|
||||
*
|
||||
* Plugins can register custom typefinders by using #GstTypeFindFactory.
|
||||
*/
|
||||
|
@ -53,8 +55,8 @@
|
|||
* is assumed that the peer element is happy with whatever format we
|
||||
* eventually read.
|
||||
*
|
||||
* By default it tries to do pull based typefinding (this avoid joining received
|
||||
* buffers and holding them back in store.)
|
||||
* By default it tries to do pull based typefinding (this avoids joining
|
||||
* received buffers and holding them back in store.)
|
||||
*
|
||||
* When the element has no connected srcpad, and the sinkpad can operate in
|
||||
* getrange based mode, the element starts its own task to figure out the
|
||||
|
|
Loading…
Reference in a new issue