search

ystreet / gst-plugins-bad

gstreamer bad plugins hacking
GNU General Public License v2.0
9 stars 6 forks source link

outgoing RTP payload(s) configuration #4

Closed philn closed 5 years ago

philn commented 6 years ago

Currently the SDP generated depends on the payloaders linked to webrtcbin.

It would be great if webrtcbin can use the payloaders found in the registry during negotiation instead of depending on those linked to the bin. Then the bin could emit a signal, notifying application side which payloaders are required after the negotiation was completed.

Perhaps it would also be good to have a white-list of payloader formats supplied as in a property of the bin? Just some ideas anyway.

ystreet commented 6 years ago

Right, so this problem is semi-neatly solved by exposing transceivers and the associated codec preferences.

As for whether payloaders should be inside webrtcbin Im going to say no for now. It's entirely possible (and in-use) to pass pre-payloaded rtp streams into webrtcbin without encoding effectively creating a relay.

philn commented 6 years ago

Exposing transceivers and codec prefs would indeed be an interesting approach to try out!

I'm not suggesting payloaders should be inside the bin though. For now I suppose I'll try to connect some payloaders beforehand but I think I would still need some kind of notification about the selected outgoing format, if the transceivers are not exposed yet.