Hi @Julian_Ridley, how many viewers are connected when you start to experience the choppy video? WebRTC through Wowza will only scale well for a certain number of viewers and isn’t meant for large audiences as Zoom is. You’ll typically start to see playback issues over 300 connections. For more than that, we suggest transcoding to HLS for playback.
If you had far less connections than that, well you may want to adjust the bitrate, frame rate from the encoder or by clicking on the settings gear icon in the webrtc playback page. (Upper right corner)
Since the webrtc > webrtc stream is not transcoded to provide an adaptive bitrate to support slower connection speeds, it’s worth testing with the lowest bitrate that provides you the quality of stream you are looking for.
Webrtc does not like B-frames and that is something that can be disabled in the encoder settings. If you encode with H.264 Main or High profile, the stream will contain B - frames .WebRTC protocol which is developed for low latency would not be able to handle B-frames which are dependent to other later frames and it will cause jittering.
WebRTC sacrifices B-frames from the GOP structure to enable real-time delivery, which can impact quality.
Lastly, keep in mind that In Cloud Webrtc playback, Cloud uses only TCP and Firefox requires UDP. So Firefox in Cloud is not possible.
Firefox can be used in Engine with WebRTC, where you can enable both TCP and UDP as Ice Candidate.