Skip to content
Snippets Groups Projects
  1. Sep 19, 2024
    • Mathieu Duponchelle's avatar
      webrtcsink: implement mechanism to forward metas over control channel · 6a23ae16
      Mathieu Duponchelle authored and GStreamer Marge Bot's avatar GStreamer Marge Bot committed
      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>
      6a23ae16
    • Mathieu Duponchelle's avatar
      gstwebrtc-api: expose API on consumer-session for munging stereo · db026ad5
      Mathieu Duponchelle authored and GStreamer Marge Bot's avatar GStreamer Marge Bot committed
      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>
      db026ad5
  2. Aug 22, 2024
    • Mathieu Duponchelle's avatar
      gstwebrtc-api: address issues raised by mix matrix support · 8ad882be
      Mathieu Duponchelle authored and GStreamer Marge Bot's avatar GStreamer Marge Bot committed
      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>
      8ad882be
  3. Aug 15, 2024
    • Mathieu Duponchelle's avatar
      gstwebrtc-api example: add support for requesting mix matrix · 1c48d706
      Mathieu Duponchelle authored and GStreamer Marge Bot's avatar GStreamer Marge Bot committed
      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>
      1c48d706
  4. Aug 09, 2024
  5. Jul 30, 2024
  6. Feb 27, 2024
  7. Apr 04, 2023
Loading