CODEWITHSUNDEEP
google-chromewebrtc
Adrian Ber
Adrian Ber

Reputation: 21370

getUserMedia results in TrackStartError in Chrome

I had a WebRTC application that was previously working and now I get the error TrackStartError while calling getuserMedia().

I'm using Chrome version 50.0.2661.75 m (64-bit).

Upvotes: 2

Views: 4468

Answers (3)

Icaro Martins
Icaro Martins

Reputation: 307

I had the same error, i was using this flags

"mandatory": {
    googTypingNoiseDetection: false,
    googEchoCancellation: false,
    googEchoCancellation2: false,
    googAutoGainControl: false,
    googAutoGainControl2: false,
    googNoiseSuppression: false,
    googNoiseSuppression2: false,
    googHighpassFilter: false,
}

now, I have to verify if chrome version is higher than 50, in that case only uses these flags

"mandatory": {
    googTypingNoiseDetection: false,
    googEchoCancellation: false,
    //googEchoCancellation2: false,
    googAutoGainControl: false,
    //googAutoGainControl2: false,
    googNoiseSuppression: false,
    //googNoiseSuppression2: false,
    googHighpassFilter: false,
}

Upvotes: 2

KaptenJansson
KaptenJansson

Reputation: 11

goog prefixed constraints are used on your own risk and they can stop working at any time. The proper way to disable audio processing in Chrome is to set echoCancellation to false.

Upvotes: 1

Adrian Ber
Adrian Ber

Reputation: 21370

It seems that Google discontinued the usage of the following audio constraints: googEchoCancellation2, googAutoGainControl, googAutoGainControl2, googNoiseSuppression2. Removing these constraints worked for me. googAutoGainControl could be the one mostly used.

Upvotes: 3

Related Questions