The browser asks for permission to access the video camera and the microphone. Pushing on "Start" initiates the process. In narrower screens, they will probably rearrange vertically.ģ. Currently, both of them show the WebRTC logo. After loading, there are two video placeholders: the left one is for the local video, and the right one is for the remote video. The demo loads properly, while first requires to accept a security exception due to a misconfigured HTTPS certificate.Ģ. In order to establish what is the expected behavior, I'm going to write a detailed step-by-step description of what happens when you run either of these demos in Chrome, our reference WebRTC browser:ġ. We want to see what is the effect of this on Safari. > This is exactly the same demo as the previous one, but here the HTTPS certificate is misconfigured. > Here you'll find the Hello-World Kurento demo, which simply fetches the local video and brings it back in loopback. There are two demo sites that have been prepared for this: And for that, we'd like to ask the greater community for a bit of help, as the variety of Apple devices that we'll be able to reach is much higher. After locating all points where it seems that Kurento and its support libraries needed changes, we're now ready to test it. We at Kurento are working on all the necessary changes to bring compatibility with the WebRTC implementation of Safari in a robust and reliable form.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |