You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Constraining the deviceId with exact on Track creation.
Expectation: internally getUserMedia is called with exact the first time, and should be called again on restart (e.g. unmute of camera).
What happens: internally getUserMedia is called with exact the first time, but on unmute the exact constraint is removed resulting in selecting a different video stream (from a different device) on unmute (tested in Chrome).
Why is the browser returning a different stream given it actually returned it correctly the first time: I don't know (this is where the whole getUserMedia madness starts).
Describe the bug
Constraining the
deviceId
withexact
on Track creation.Expectation: internally
getUserMedia
is called withexact
the first time, and should be called again on restart (e.g. unmute of camera).What happens: internally
getUserMedia
is called withexact
the first time, but on unmute theexact
constraint is removed resulting in selecting a different video stream (from a different device) on unmute (tested in Chrome).Where I think the issue is: https://github.com/livekit/client-sdk-js/pull/773/files
Why is the browser returning a different stream given it actually returned it correctly the first time: I don't know (this is where the whole getUserMedia madness starts).
Reproduction
localParticipat.setCameraEnabled(false)
exact
Note: it happens under specific circumstances (hard to reproduce on some clients, reproducible with others - e.g. with a different set of devices).
Logs
No response
System Info
Severity
annoyance
Additional Information
No response
The text was updated successfully, but these errors were encountered: