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
switchVideoCameraCapture(streamId,deviceId,onEndedCallback){//stop the track because in some android devices need to close the current camera streamif(this.localStream&&this.localStream.getVideoTracks().length>0){varvideoTrack=this.localStream.getVideoTracks()[0];videoTrack.stop();}else{Logger.warn("There is no video track in local stream");}
If this is only happening on "some Android devices", it should only stop the existing track on those...
Why stop the stream for all other clients where the bug would not appear...
Now there is a black screen in between when switching cameras, which is not nice UX.
Also, if we wanted to call setVideoCameraSource manually, e.g. to choose facingMode or similar, why is the same logic not applied there? I'm guessing the same bug happens there if the existing track is not stopped first...
Expected behavior
Only close the existing track if needed.
Also handle this on setVideoCameraSource
Actual behavior
Always closes existing track (even when not needed)
It never closes existing track when using setVideoCameraSource
The text was updated successfully, but these errors were encountered:
Short description
media_manager.js
:If this is only happening on "some Android devices", it should only stop the existing track on those...
Why stop the stream for all other clients where the bug would not appear...
Now there is a black screen in between when switching cameras, which is not nice UX.
Also, if we wanted to call
setVideoCameraSource
manually, e.g. to choose facingMode or similar, why is the same logic not applied there? I'm guessing the same bug happens there if the existing track is not stopped first...Expected behavior
setVideoCameraSource
Actual behavior
setVideoCameraSource
The text was updated successfully, but these errors were encountered: