voxl-streamer client repetitive connect/disconnect
-
@wilkinsaf Thanks! I fixed the typo in the original post.
-
I am seeing that this failed for MJPEG
voxl:~$ voxl-uvc-server -d
Enabling debug messages
voxl-uvc-server starting
UVC initialized
Device found
Device opened
uvc_get_stream_ctrl_format_size failed for MJPEG
uvc_get_stream_ctrl_format_size failedIs there a config file for this that I can modify to change the format?
-
I am seeing that this failed for MJPEG
voxl:~$ voxl-uvc-server -d
Enabling debug messages
voxl-uvc-server starting
UVC initialized
Device found
Device opened
uvc_get_stream_ctrl_format_size failed for MJPEG
uvc_get_stream_ctrl_format_size failedIs there a config file for this that I can modify to change the format?
@wilkinsaf That shows a failure of the camera to support either MJPEG or YUV422. In order to support that camera you need to know what formats it supports. The best way to do that is to query it's capabilities on the command line. First of all use the
lsusbcommand to find out the device id and product id of the camera. For example:Ubuntu18$ lsusb Bus 001 Device 090: ID 046d:0825 Logitech, Inc. Webcam C270 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubThis shows you that the UVC webcam has device id and product id
046d:0825. You can use that to query it's capabilities withlsusb -v -d 046d:0825. This will dump all of the camera capabilities to the output. Can you respond with the output from your camera? -
@wilkinsaf That shows a failure of the camera to support either MJPEG or YUV422. In order to support that camera you need to know what formats it supports. The best way to do that is to query it's capabilities on the command line. First of all use the
lsusbcommand to find out the device id and product id of the camera. For example:Ubuntu18$ lsusb Bus 001 Device 090: ID 046d:0825 Logitech, Inc. Webcam C270 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubThis shows you that the UVC webcam has device id and product id
046d:0825. You can use that to query it's capabilities withlsusb -v -d 046d:0825. This will dump all of the camera capabilities to the output. Can you respond with the output from your camera?Apologies for the delay. Some other things came up.
I was able to pull down the camera information. We have 2 cameras we are trying to get up.Cam 1: https://pastebin.com/qHvHKXay
Cam 2: https://pastebin.com/7DgvP58kThey appear to be able to post in MJPEG
-
Not sure if voxl-uvc-server got removed.
I can not seem to find it in the public repo:
-
-
Apologies for the delay. Some other things came up.
I was able to pull down the camera information. We have 2 cameras we are trying to get up.Cam 1: https://pastebin.com/qHvHKXay
Cam 2: https://pastebin.com/7DgvP58kThey appear to be able to post in MJPEG
@wilkinsaf The current voxl-uvc-server capabilities only cover uncompressed frames, not mjpeg. The two cameras that you are looking at both have uncompressed formats but the guidFormat is slightly different than the cameras I have tested with. Let me look into this a little deeper.
-
Apologies for the delay. Some other things came up.
I was able to pull down the camera information. We have 2 cameras we are trying to get up.Cam 1: https://pastebin.com/qHvHKXay
Cam 2: https://pastebin.com/7DgvP58kThey appear to be able to post in MJPEG
@wilkinsaf The formats should be compatible. I'll have to dig into the libuvc code to see why they are not accepted.
-
@wilkinsaf Are either of these cameras cheap and easy to purchase?
-
I believe so. Let me find them online really quick. I was able to get the video's from the cameras streaming using the directions here: https://docs.modalai.com/uvc-streaming/
I moved over the ffmpeg ipk and executed
ffmpeg -i /dev/video2 -f mpegts udp://QCS_IP:4242So I know that they are working.
-
Apologies for the delay. Some other things came up.
I was able to pull down the camera information. We have 2 cameras we are trying to get up.Cam 1: https://pastebin.com/qHvHKXay
Cam 2: https://pastebin.com/7DgvP58kThey appear to be able to post in MJPEG
@wilkinsaf There are some clues here: https://github.com/gregkh/usbutils/issues/42. It seems like there are some endian issues with interpretation of the guidFormat field. For example, for my Logitech C270 test camera, lsusb reports the guidFormat as
32595559-0000-0010-8000-00aa00389b71but libuvc (which voxl-uvc-server uses) reports the guidFormat as59555932-0000-1000-8000-00aa00389b71. So, my guess is that since lsusb reports the guidFormat of your camera as59555932-0000-1000-8000-00aa00389b71, libuvc (and hence voxl-uvc-server) will see it as32595559-0000-0010-8000-00aa00389b71which doesn't match any valid formats. I think I can hack libuvc to add the extra guidFormat and then your cameras will work but I won't be able to test it without one of your cameras. But I will post it and you can try it. For reference this is where libuvc needs to be modified to add the extra guidFormat: https://github.com/libuvc/libuvc/blob/37f00abd32b083a3d748f2a25c1c794578b51c16/src/stream.c#L109 -
Apologies for the delay. Some other things came up.
I was able to pull down the camera information. We have 2 cameras we are trying to get up.Cam 1: https://pastebin.com/qHvHKXay
Cam 2: https://pastebin.com/7DgvP58kThey appear to be able to post in MJPEG
@wilkinsaf There is a new version of libuvc available at http://voxl-packages.modalai.com/dev/libuvc_1.0.2_202112182223.ipk with the changes. If you rebuild the dev branch of voxl-uvc-server and install build deps from dev you should pick up the new libuvc. Then you can rebuild and test with your camera.
-
@wilkinsaf There is a new version of libuvc available at http://voxl-packages.modalai.com/dev/libuvc_1.0.2_202112182223.ipk with the changes. If you rebuild the dev branch of voxl-uvc-server and install build deps from dev you should pick up the new libuvc. Then you can rebuild and test with your camera.
@Eric-Katzfey roger that. thank you for your support here Eric
-
@wilkinsaf There is a new version of libuvc available at http://voxl-packages.modalai.com/dev/libuvc_1.0.2_202112182223.ipk with the changes. If you rebuild the dev branch of voxl-uvc-server and install build deps from dev you should pick up the new libuvc. Then you can rebuild and test with your camera.
@Eric-Katzfey will post results after run
-
@Eric-Katzfey Sorry for being such a pain, but it seems like this repo keeps moving.
I went to https://gitlab.com/voxl-public/modal-pipe-architecture/voxl-uvc-server
but got this
I keep searching around for the repo, but can not find it
-
@Eric-Katzfey Sorry for being such a pain, but it seems like this repo keeps moving.
I went to https://gitlab.com/voxl-public/modal-pipe-architecture/voxl-uvc-server
but got this
I keep searching around for the repo, but can not find it
@wilkinsaf Sorry, it was setup as private. I changed it to public. Can you try again?
-
@wilkinsaf Sorry, it was setup as private. I changed it to public. Can you try again?
@Eric-Katzfey Got it, thank you!
Will download and play with
-
@wilkinsaf Sorry, it was setup as private. I changed it to public. Can you try again?
-
@Eric-Katzfey Will it remain public?
@wilkinsaf Yes, it will remain public. Did you get a chance to see if the changes worked?
-
@wilkinsaf Yes, it will remain public. Did you get a chance to see if the changes worked?
@Eric-Katzfey Testing out today
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login