This commit is contained in:
Mathieu Duponchelle 2021-12-21 00:32:51 +01:00
parent a4df10b112
commit 114fd3c5f6

View file

@ -24,6 +24,9 @@ useful alternative.
`Signallable` interface as defined [here](plugins/src/webrtcsink/mod.rs). The `Signallable` interface as defined [here](plugins/src/webrtcsink/mod.rs). The
[default signaller](plugins/src/signaller/mod.rs) can be used as an example. [default signaller](plugins/src/signaller/mod.rs) can be used as an example.
An [example project] is also available to use as a boilerplate for implementing
and using a custom signaller.
* Sandboxed consumers: when a consumer is added, its encoder / payloader / webrtcbin * Sandboxed consumers: when a consumer is added, its encoder / payloader / webrtcbin
elements run in a separately managed pipeline. This provides a certain level of elements run in a separately managed pipeline. This provides a certain level of
sandboxing, as opposed to having those elements running inside the element itself. sandboxing, as opposed to having those elements running inside the element itself.
@ -53,6 +56,8 @@ If more granular control is required, applications should use `webrtcbin` direct
`webrtcsink` will focus on trying to just do the right thing, although it might `webrtcsink` will focus on trying to just do the right thing, although it might
expose interfaces to guide and tune the heuristics it employs. expose interfaces to guide and tune the heuristics it employs.
[example project]: https://github.com/centricular/webrtcsink-custom-signaller
## Building ## Building
### Prerequisites ### Prerequisites