"v4l2-ctl" lists devices different to WebRTC Streamer interface devices about webrtc-streamer HOT 6 CLOSED

Hi @muhanad40

Please note v4l2:// urls are for H264 encoded stream, then it needs -o argument and H264 support from the v4l2 device. When enabled it should be discovered by /api/getMedialist.
videocap url used the iteration of video device detected with GetDeviceName see https://github.com/mpromonet/webrtc-streamer/blob/master/inc/CapturerFactory.h#L90 and openned in https://github.com/mpromonet/webrtc-streamer/blob/master/inc/VcmCapturer.h#L81, it is not the number in /dev/videoXX.

Best Regards,
Michel.

from webrtc-streamer.

Hi @mpromonet, thank you for your quick reply. I don't think the streams are H264 encoded. I just plug the devices in and they show up in the /dev directory. How can I connect to a device's webrtc stream using its device path? Is this even possible?

The reason why I ask is because I need a way that's predictable to connect to the webrtc stream. I have a web application that knows a device's /dev path so it can only use that to connect to its stream.

How can I do this?

from webrtc-streamer.

FYI, I can connect to a device using opencv using the device's /dev path videocap://dev/video2 and able to grab a screenshot. So I know that videocap://dev/video* pattern works. Not sure how I can do this with this.

from webrtc-streamer.

Another reason why I want to rely on the real /dev path is that it's predictable. Currently the devices are enumerated so I can't predict which device will be which index number. I plan to connect many more devices and it's very important that I use something fixed and not dynamic.

from webrtc-streamer.

Hi,
You may use device by path. In order to do this, you need to modify the code. Feel free to submit a PR.
Best Regards
Michel

from webrtc-streamer.

Hi, I wish I can submit a PR, but I'm not a C++ developer. Thanks anyways :)

from webrtc-streamer.