Firefox WebRTC doesnt work with intel imaging signal processor 2400
Hello, I've been using Firefox with WebRTC. On both 32 and 64 bit DELL Venue platforms, there was no issue. Firefox works with WebRTC code without issue. On a Toshiba Encore 2 with windows and ATOM processor, Firefox says 'no media' on a window.navigator.mozGetUserMedia.bind(navigator) call. What I notice that is different on Toshiba platform is that there is under 'imaging' the Intel imaging signal processor 2400. The two cameras front/back on the Toshiba Encore 2 platform drivers are found under 'system devices'. I'm not used to seeing that, on DELL the imaging devices are in the imaging device list. I can run Chrome on the same Toshiba platform and no issue, camera works. With Firefox, I can select front or back video and I see nothing. If I select 'no video' and 'audio only', that is enabling only the audio, then WebRTC works, the call succeeds (although there was a crash later). I'd like to stick with Firefox platform for WebRTC so I hope there is a fix sometime in the future. I downloaded Beta firefox, same issue. It's just a hunch but I think it is related to the imaging device being the 'intel imaging signal processor 2400" and the cameras as system devices. I will try with an external USB camera and see if the problem goes away. Obviosly for a tablet I would like to use firefox peer to peer WEBRTC with the built in cameras.
Thanks. Kris Jay
Všechny odpovědi (2)
Hey Kris, So there are some more troubleshooting we can do to make a bug to get that started>
If you download a NightyDebug build from
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2014-10-03-mozilla-central-debug/, install it and the run with env vars set: NSPR_LOG_MODULES=mediamanager:5,getusermedia:5 and NSPR_LOG_FILE= (some file) that will tell us more (in the logs)
There are a lot of cameras/webcams out there... sometimes they return data in unexpected formats
Our next steps will be to file a bug at bugzilla.mozilla.org (https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=WebRTC) and attach the logfile as an attachment
OK, I will try that. I temporarily switched to chrome on that platform, which of course does not help the community.