It doesn't seem to work in Bowser for iOS about openwebrtc-examples

[superdump]

What version of Chrome? With current master of dependencies and openwebrtc itself, we believe the "Error processing ICE candidate" message is due to Chrome perhaps not supporting TCP nor IPv6 candidates but we have not yet investigated fully.

We are working hard on interoperability and have identified a couple of issues in apprtc code that are implemented incorrectly according to the WebRTC standards.

[kooler]

Yes, indeed, this error doesn't appear in Firefox, looks like something Chrome specific. Chrome version: 38.0.2125.101.

In conference with FF though it uses enormous amount of resources on iOS side (about 75% of CPU when own camera is shared) and freezes in couple of seconds. Tested on iPhone 5. Is it something OpenWebRTC related?

[superdump]

We currently have to do a lot of the really heavy media processing work in software because we are using the standard iOS UIWebView widget and adding in the WebRTC functionality from the outside.

The heaviest parts where it concerns processing are the video codecs and raw video processing.

Properly integrated WebRTC support in a web browser engine (like Blink for Chrome or Gecko for Firefox) is able to use more effective video rendering, such as using OpenGL or DirectX or so, while still retaining all the CSS transformation and WebGL support. To be able to do this from outside of the web browser engine, we have to send raw bitmap images for each video frame.

It is possible to use OpenGL for rendering into a native UI widget and that gives significant performance benefits. We will be publishing some tutorials soon that will make use of this approach and then it will be easier to see what could be expected with a proper integration of OpenWebRTC into a web browser engine.

As for video codecs, the only way to support video codecs efficiently without loading the CPU is to use GPU accelerated or hardware codecs. On mobile platforms, there are hardware codecs available on most devices for H.264 and some devices have hardware VP8 support as well.

Last week we added support for hardware decoding using the built-in Intel (I think) H.264 hardware codec on Macs when using Mac OS X. We intend to add more support for hardware codecs soon.

The summary is that we will do what we can to improve the performance and building OpenWebRTC on top of GStreamer allows us to do this with not too much work. Keep watching! 😄

[kooler]

Thank you for explanation! You're doing great job guys, sounds very interesting. 👍 Will keep watching for sure. Looking forward to see new tutorials. 😄

[stefanalund]

We landed a couple of interp fixes 2-3 days ago, please re-build OpenWebRTC and try again: https://github.com/EricssonResearch/openwebrtc/wiki/Building-OpenWebRTC#update-openwebrtc

[stefanalund]

Oh, with these fixes we have also confirmed that Bowser (and other OpenWebRTC apps) can talk to Firefox 33 and Chrome 38 using http://demo.openwebrtc.io

[stefanalund]

@kooler did you try with the latest changes in OpenWebRTC master?

[kooler]

@stefanalund, I've pulled latest versions of both OpenWebRTC and Bowser, but still getting the same issue with iPhone 5.

[superdump]

@kooler what version of Chrome? It has to be Chrome newer than stable because of an ICE-restart bug.

[abigdreamer]

I'm having the same problem on my 5S 8.1 IOS with Chrome latest version on Mac

[stefanalund]

Try Chrome Canary or FF, there is a bug in Chrome 38 that is fixed in later versions.

[stefanalund]

@abigdreamer did that help?

[stefanalund]

If you still have problem, please re-open. I'm closing this issue for now since it seems to work. Please file issues with Bowser here instead: https://github.com/EricssonResearch/bowser