Call failure when no video device available

[dudash]

Describe the bug
When making an outgoing call on linux (probably all platforms), if the clivrt cannot open the /dev/video0 then call won't be made.

To Reproduce
Steps to reproduce the behavior:

1. open the app
2. 'login' to the signaling server
3. connect another user to the signaling server (using the test website)
4. 'call' the other user from clivrt
5. see error occurs in logs with unclear feedback to user (possibly putting us in a bad state?)

Expected behavior
Call is still placed with your video off -OR- an error message is displayed providing you more information and apologizing.

Additional context
This might be challenging to fix in the ideal way. I'd think being able to call someone with your video off should be possible. However, creating the video-offer cannot proceed without the device. It'd be nice to be able to request they call you, or to just join them and receive their video.

[andykrohg]

Video-offer doesn't necessarily need a device; all it needs is a track (video/audio). In the event that device access fails for some reason, we could use the aortic library to create a backup track (like send the red hat logo or something) and just send it at 30fps. See example here: https://github.com/aiortc/aiortc/blob/main/examples/videostream-cli/cli.py#L20

[dudash]

💯

…

On Fri, Feb 18, 2022 at 3:58 PM Andy Krohg ***@***.***> wrote: Video-offer doesn't necessarily need a device; all it needs is a track (video/audio). In the event that device access fails for some reason, we could use the aortic library to create a backup track (like send the red hat logo or something) and just send it at 30fps. See example here: https://github.com/aiortc/aiortc/blob/main/examples/videostream-cli/cli.py#L20 — Reply to this email directly, view it on GitHub <#12 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA4Q2H7NHMM5DVAOYAFVCTU32XI3ANCNFSM5OYRLTFQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>