Thanks Tsahi.

For that, you’ll need to approach the GStreamer people…

One question about WebRTC in Gstreamer, if WebRTC is just an output type, how does it cooperate with encoder on the pipeline? i.e. how does QoS work to dynamically change bitrate etc.?

Then the question becomes whether GStreamer's element based architecture is suitable for implement WebRTC's comprehensive QoS mechanism or not? Don't know if that's the reason for project webrtcsink to integrate all the things in a black box, https://mathieuduponchelle.github.io/2021-12-14-webrtcsink.html.

After practicing RTC for 8 years I can't help but think that the skill set required for developers is too specialized in order to have wide appeal. These experts are now spread between too many projects and organizations and the end result is not the robust marketplace that you wanted.

In my experience on the commercial side there is often a surplus of requests for software integrations and not enough person-hours in the day to perform them all. In the end substantial effort is left downstream as one-offs, but the engineers still gained experience for future projects. Unless business interests and engineering interests align it's easy to waste time or lose momentum in WebRTC.