19 comments on “Guide to WebRTC with Safari in the Wild (Chad Phillips)

  1. Pingback: September 17th RealTimeWeekly #247

  2. Thanks for this Chad, currently struggling with this myself, where a portable ‘web’ app is being written..
    I’m hopeful it will creep into wkwebview soon!

  3. Thanks for detailing the issues.

    One suggestion for any future article would be including the iOS Safari limitation on simultaneous playing of multiple elements with audio present.

    This means refactoring so that multiple (remote) audio sources are rendered by a single element.

  4. The same issue I’m facing New getUserMedia() request kills existing stream track. Let’s see whether it helps me or not.

  5. iOS calling getUserMedia() again kills video display of first getUserMedia(). This is the issue I’m facing but I want to pass the stream from one peer to another peer.

  6. Thank you Chad for sharing this, I was struggling with the resolution issue on iOS and I was not sure why I was not getting the full hd streaming. Hope this will get supported soon.

  7. VP8 is a nightmare. I work on a platform where we publish user-generated content, including video, and the lack of support for VP8 forces us to do expensive transcoding on these videos. I wonder why won’t vendors just settle on a universal codec for mobile video.

  8. Great Post!
    Chad I am facing an issue with iOS Safari, The issue is listed below.
    I am using KMS lib for room server handling and calling, There wasn’t any support for Safari / iOS safari in it, I added adapter.js (shim) to make my application run on Safari and iOS (Safari). After adding it worked perfectly on Safari and iOS, but when more than 2 persons join the call, The last added remote stream works fine but the existing remote stream(s) get struck/disconnected which means only peer to peer call works fine but not multiple remote streams. Can you please guide how to handle multiple remote streams in iOS (Safari).
    Thanks

  9. No low/limited video resolutions: 1920×1080 not supported
    -> are you talking about IOS12 ?
    Because I’m doing 4K on IOS 12.3.1 with janus echo test with iphone XS Max (only one with 4K front cam)
    Of course if I run your script on my MBP it will say fullHD not supported -> because the cam is only 720p.

    • That may be a standard camera resolution on that particular iPhone. The larger issue has been that only resolutions natively supported by the camera have been available, leading to difficultly in reliably selecting resolutions in apps, especially lower resolutions like those used in thumbnails.

      Thankfully, this appears to be fully addressed in the latest beta of iOS 13.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.