-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
navigator.getUserMedia AUDIO choppy/not useable in 0.8.0 #1270
Comments
I can confirm this issue on Mac 10.8 and 10.9, chromium-args specified above are not required to repro and this was also fine in 0.8-pre |
@tommoor does it work fine for you with 0.8.0-rc1? |
@rogerwang yes it works in that version, sorry I meant 0.8.0-rc1 - not 0.8-pre |
I can confirm that it works with 0.8.0-rc1 but not with 0.8.0 final (Linux 64bit). |
nice one @rogerwang looking forward to testing, as someone who doesn't know any C++ i'd be interested to know why this caused the issue if you have a second? :-D |
The code just enumerated the device twice, that's the reason why audio get choppy. |
With node-webkit 0.8.0 audio capture with getUserMedia / webrtc became unusable. Sounds like the audio is way too loud and gets clipped all the time or something.
Easy test is possible with https://apprtc.appspot.com/?debug=loopback which captures audio and video and subscribes itself again (loopback test).
{
"name": "test-webrtc-audiovideoloopback",
"main": "https://apprtc.appspot.com/?debug=loopback",
"window": {
"toolbar": true,
"frame": true
},
"nodejs": true,
"chromium-args": "--ignore-certificate-errors --enable-threaded-compositing"
}
The very same works nice with node-webkit 0.7.2.
I can reproduce with 0.8.0 on Linux 64bit and Windows. Did not try on the other platforms.
The text was updated successfully, but these errors were encountered: