WebRTCSink issue with Apple Safari - More Data
GST Developer via gstreamer-devel <[email protected]>
| Newsgroups | gmane.comp.video.gstreamer.devel |
|---|---|
| Message-ID | <[email protected]> |
Supplementary Information: - Using the browser based camera send via WebRTC (excluding GStreamer itself), Safari can SEND a camera stream which is viewable on Chrome - Safari will NOT view a WebRTC Camera feed from Chrome, but it WILL view a WebRTC Camera Feed from another Safari Browser. This suggests that Safari has a particular WebRTC receiving compatibility metric which is not compatible with Chrome, or GStreamer based WebRTC source. > Hi Folks. > > I am investigating an issue with webrtcsink and Apple Safari > > Using the guidelines detailed at : https://gstreamer.freedesktop.org/documentation/rswebrtc/index.html?gi-language=c#usage > > - My Ubuntu 22.04 LTS server is *wide open* - in Google Cloud Platform, zero firewalls or restrictions. > - I am launching the example GStreamer pipeline : > - I am running the gstwebrtc-api example with npm/webpack > - I am launching the example GStreamer pipeline : > gst-launch-1.0 webrtcsink name=ws meta="meta,name=testsource" videotestsrc ! ws. audiotestsrc ! ws. > > Expected Result: > - index.html at port 9090 should present WebRTC video stream on all WebRTC compatible browsers > > Observed Result: > - Windows 10 - WebRTC stream works FINE in Chrome and Edge > - iOS 16.6 - WebRTC Stream Fails with all browsers (since all browsers in iOS must use underlying Safari engine) > - macOS 13.4.1 - WebRTC stream works FINE in Chrome, Firefox, Edge and Opera. Stream Fails with Apple Safari. > > Communications with the WebPack server is supplying the stream discovery , but the WebRTC connection fails at the point where the video element is put into play(). > I have made sure that this is not simply the browser security blocking autoplay. > > I wonder if anyone is able to replicate these tests, or provide any insight into the cause. > > Many thanks ! >