Firefox Hello won't allow me to select which video and audio devices to use when I start a conversation instance.
As per the title. If I ACCEPT a call, or start a conversation I have no choice about which devices are used (video and audio), Firefox seems to just arbitraily decide which to use without asking me. If I make a call or join a conversation it's different, I get a dialog asking me which devices I want to use. Similarly, there's no options to edit the conversation settings to select the device.
I tried just entering the conversation URL into a browser tab, which does give me the dialog, but I cannot join the conversation as it says there are already two people in it.
How to fix this?
Cheers
Alle antwoorden (3)
Update: This just seems to be an oversight. Devs, You have to realize that conversation starters and call answerers still need the ability to select their devices. I know WebRTC and Hello is all still beta, but this seems to be something that should have been realized from the very start.
Are you also aware that the code examples on MDC don't actually work in Firefox, but do work in Chrome? Again, I know you say the API docs are in need of update, but for example source to actually nor work on the browser you develop and it working on a browser you do not seems a trifle ridiculous. If you want this technology to catch on, you've got to be more diligent.
mozRTCPeerConnection() seems to use a fixed pre-set STUN server, there's no way to make it use another. Again in Chrome with webkitRTCPeerConnection() you can do this, in Firefox you cannot.
I have a friend I'm testing with and he cannot even create a Peer Connection object in FireFox, it fails instantly when created with an "ICE Failed" in the JS console.
STUN servers should not be a requirement. The host candidates can be modified to traverse NATs without even having to bother with reflexive candidates, all the client has to know is its internet IP address which can be easily conveyed by the web server the page is on. We don't want to use TURN as we want a true peer to peer system, not a peer-server-peer solution like TURN
Don't force people into certain dead-ends and bloat the requirements. Keep it simple and think. Also, document your source as you go, there are plenty of IDEs that generate docs as you go, all you have to do is spend a few more seconds commenting each class/function.
Same here. Firefox just updated to 36.0 on my Mac and asked me to try Firefox Hello and ... first click and it's useless, because it's using the wrong camera.
And: Firefox hello grabs one camera (not the one I want), but when I then go to use skype, that cannot use _either_ camera. Which is even more annoying. I have to go and close the Firefox hello tab before I can use Skype video, even though Firefox refuses to use the camera I want to use with Skype.