Assume the following setup:
* pipeline has two webrtcbin elements
* browser sends vp8 to one webrtcbin element
* video is decoded, tee'd, and one branch re-encodes (vp8enc) which feeds another webrtcbin element
* 2nd webrtcbin element sends video to second browser
If the resolution of the input video (first remote peer) changes, then the vp8enc element stops pushing buffers. The cause of the resolution change could be because of anything, such as the "qualityLimitationResolutionChanges" stat in chrome://webrtc-internals. When the resolution changes, and the element stops pushing buffers, there's nothing in the logs to explain why, This is a new behavior in 1.18.
So to get around this behavior I've added code to watch for resolution changes on the inbound video and to dynamically swap out the vp8enc element with another, and that seems to have addressed the problem.
Is this behavior intended?
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
Locked
