- Sep 19, 2024
-
-
It may be desirable for the frontend to receive ancillary information over the control channel. Such information includes but is not limited to time code metas, support for other metas (eg custom meta) might be implemented in the future, as well as downstream events. This patch implements a new info message, probes buffers that arrive at nicesink to look up timecode metas and potentially forwards them to the consumer when the `forward-metas` property is set appropriately. Internally, a "dye" meta is used to trace the media identifier the packet we are about to send over relates to, as rtpfunnel bundles all packets together. The example frontend code also gets a minor update and now logs info messages to the console. Part-of: <!1749>
-
We cannot do that by default as this is technically non-compliant, so we need to expose API to let the user opt into it. Part-of: <!1754>
-
- Aug 22, 2024
-
-
1c48d706 was mistakenly merged too early, and there were concerns about the implementation and API design: The fact that the frontend had to expose a text area specifically for sending over a mix matrix, and had to manually edit in floats into the stringified JSON was suboptimal. Said text area was always present even when remote control was not enabled. The sendControlRequest API was made more complex than needed by accepting an optional stringifier callback. This patch addresses all those concerns: The deserialization code in webrtcsink is now made more clever and robust by first having it pick a numerical type to coerce to when deserializing arrays with numbers, then making sure it doesn't allow mixed types in arrays (or arrays of arrays as those too must share the same inner value type). The frontend side simply sends over strings wrapped with a request message envelope to the backend. The request text area is only shown when remote control is enabled. Part-of: <!1725>
-
- Aug 15, 2024
-
-
This is one example of how a consumer might send over custom upstream event requests to the producer. As webrtcsink will deserialize numbers in priority as integers, we need a custom stringifying function to ensure members of the matrix array are indeed serialized with the floating point. An optional stringifier parameter is thus added to the sendControlRequest API. Part-of: <!1711>
-
- Aug 09, 2024
-
-
Mathieu Duponchelle authored
Support was added to the base class when the AWS KVS signaller was implemented, but the default signaller still only supported the case where the producer was creating the offer. Also extend the javascript API Part-of: <!1702>
-
- Jul 30, 2024
-
-
Instead simply use the desired address directly from the reference example, this makes it work out of the box without placing expectations on the web server. Part-of: <!1674>
-
- Feb 27, 2024
-
-
Part-of: <!1373>
-
- Apr 04, 2023
-
-
Loïc Le Page authored
This subproject adds a high-level web API compatible with GStreamer webrtcsrc and webrtcsink elements and the corresponding signaling server. It allows a perfect bidirectional communication between HTML5 WebRTC API and native GStreamer. Part-of: <!946>
-