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
On Chrome I have several cameras, the Avermedia is a video card that broadcasts DTT channels on a computer instead of television.
There's Manycam, that's my test webcam device.
I have another camera, it's not plugged in, it's a real webcam.
I noticed that the Avermedia is always first, therefore it very often selects the Avermedia by default.
Here's how the conflict unfolds:
I turn on my camera (it selects the Manycam well)
If I want to turn the camera back on, this time it still selects Avermedia, but I would like it to select Manycam
As a result, customers cannot turn on their webcam if they have multiple devices
Do you have an idea to solve this?
Salutations
The text was updated successfully, but these errors were encountered:
I partially solved the problem. Here is what I did:
On Firefox everything is fine, but not on Chrome. I put a menu to choose the webcam device (but I haven't yet to choose the audio). Each time a client starts his webcam, then from time to time by default it offers him a popup with Sweetalert2 to choose the webcam. As soon as he ticks, he updates the "videoSelect" live and the camera starts with it.
You could use the local.storage to save you index -> deviceId you have selected, then reuse it, if it doesn't find it (device removed) use the default.
Hi
On Chrome I have several cameras, the Avermedia is a video card that broadcasts DTT channels on a computer instead of television.
There's Manycam, that's my test webcam device.
I have another camera, it's not plugged in, it's a real webcam.
I noticed that the Avermedia is always first, therefore it very often selects the Avermedia by default.
Here's how the conflict unfolds:
As a result, customers cannot turn on their webcam if they have multiple devices
Do you have an idea to solve this?
Salutations
The text was updated successfully, but these errors were encountered: