[BUG] UVC demo app does not work with OAK-D-Lite #616
Comments
|
Thanks for the thorough details and sorry about the trouble here! I just reproduced the problem using a USB2 cable on an M1 Max Macbook Pro with my OAK-D-Lite. And then using a USB3 cable it actually worked fine: So this is something to do with using a USB2 cable and the device acting as a webcam (UVC). So the USB3(.1) cable you are getting should resolve this. I will need @alex-luxonis insight on UVC over USB2. I tried with Thanks and sorry again about the trouble. |
|
@Luxonis-Brandon I just enabled CLI arguments in apps and we can use CC @alex-luxonis on the screenshots below, I saw the same artifacts on Jetson, reproduceable using
|
|
I just want to quickly confirm that with a proper USB3 cable UVC works flawlessly. I don't think UVC not working over USB2 is necessarily a problem, it just should be advertised, or the UVC app should refuse to run with just USB2 (and explain why). But UVC over USB2 would certainly be nice. |
|
Thanks, all! And agreed we should just properly make a warning that says USB2 is not supported via webcam mode as of yet. |
|
Hi folks! Since this is open and I am not super familiar with what is going on (or the background of it). I am trying to run it as a webcam. I can see that I am able tolaunch
It gives me this in console
But when I try to access the app through any Camera app (or even OBS), I get this
|
|
Odd. So the system thinks it is connected to USB2 only here. To debug, when running the demo app gui could you do |
|
Hi @arafattehsin, If that's the case, what type-C cable are you using, are both ends type-C, or it's type-A to type-C? The console logs are fine for the first part, I'm observing the same on Windows, it doesn't advance to printing the status unless an UVC consumer (e.g. Camera app) is started. |
|
Unrelated to the above, adding a general note for the differentiation between an USB2 and USB3 cable, as many type-C cables on the market are USB2-only. If the other end is type-A, the color usually should be blue, or it can be checked if a row of 5 extra pins exists deep inside the connector: |
|
@alex-luxonis and @Luxonis-Brandon - thank you so much for these details and very helpful responses. I re-run again and saw this (I think I get your point here @alex-luxonis)
After noticing my cable, I think what I wrote is not correct and your explanation makes sense. The USB A connector is different than what you have posted here about USB 3. Now, the question becomes, is it because of USB 3 cable that my OAK D Lite is not working as a webcam or is there anything else I have to do as well? Just curious. I am happy to get a new cable (with USB 3 for sure) |
|
@arafattehsin replacing the cable with USB3 one should resolve this issue |
|
We'll also fix the USB2 issue (hopefully within 1..2 weeks), but the performance with USB3 will be better for uncompressed streaming. At the moment, the UVC configuration is 1920×1080 NV12 (1.5 bytes/pixel). The bandwidth required for 30fps is: |
|
@alex-luxonis - Please take your time but an option to choose the resolution (or launching it with the specific resolution option) will always be great, considering its 4K capabilities. 🙂 |
|
@alex-luxonis @Luxonis-Brandon - folks! USB C (3.0) arrived and works great. Woohoo! I will open up an enhancement soon which I think would add some values to the Oak D Lite as a product offering. |
|
Awesome thanks for confirming! And sounds great! |
|
Hi guys, There is even something strange when looking at the console. Calling
Turn out, I was unlucky enough so part of my issue was my software wasn't detecting the UVC in the first place. |
|
Do you use an actively powered USB-hub? USB2 versus USB3 is also about how much power could be provided to the end device. |
|
(If needed we may create a new issue specifically for me, especially for the log part). OAK-D-Lite. I tried two ways to power it (because It was also one of my concerns) using the "Y" splitter (dedicated power port). The data line is always on that cheap USB-2 computer. One using a USB 2 Type-A powered hub (Amazon Basic (yeah I know...)) using the dedicated "fast charge port" (1.5A) powered from an external power source. However, since OAK-D-Lite it is an USB-C I thought you may support USB PD only which lead me... To test using a USB-C 3.1 on a always on port from a laptop. (I also tried on the Type-A USB 3.1 port) In every case I didn't hear any USB disconnect from the host which could lead me to think the power going to the OAK-D-Lite was way too low. However, I know the OAK-D-Lite may get enough power to not disconnect from host but not enough to work properly :/ (If only wireshark USB could work on that damn Windows host!) Warning: Keep in mind, when I use a Type-A USB port I'm using a Type-A to Type-C wire which is likely to not be USB 3 compliant! |
|
Hey guys, We recently (Dec. 2022) purchased an OAK-D PRO W and we are having the same issue of not being able to run the camera as a webcam on Linux aarch 64 Ubuntu 20.04. The error when running v4l2-ctl --list-devices : and ls -lrt /dev/video returns: lsusb does not list the OAK either The only port on the camera is a USB-C and the cable we use is fairly new USB-C cable which we plug into USB-3 Type-A (Blue) adaptor on the PC side. We tested and this cable works perfectly with a Webcam. is there something else we should try? a 'patch' or some other solution or workaround? Note: perhaps related is the comment here: https://unix.stackexchange.com/questions/678358/logitech-c920e-v4l2-ctl-list-devices-cannot-open-device-dev-video0-exiti "Since the driver does not seem to detect your camera, it's possible the camera presents itself to the USB bus in some non-standard way that will need to be handled specially by the uvcvideo driver maintainers." and in the faq: https://www.ideasonboard.org/uvc/faq/#faq1 if our device is a uvc device. running the command: should see a number of lines like this: bFunctionClass 14 Video so is it missing the correct uvc drive ? |
|
yes, running *python3 depthai_demo.py --app uvc* we get:
*"This app is temporarily disabled on AARCH64 systems due to an issue with
stream preview. We are working on resolving this issue"*
…On Tue, Jan 31, 2023 at 5:14 AM Erol444 ***@***.***> wrote:
Hi @hg111 <https://github.com/hg111> , Have ran the UVC pipeline? Docs
here <https://docs.luxonis.com/en/latest/pages/oak_webcam/>.
—
Reply to this email directly, view it on GitHub
<#616 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZE7VXYJSHLIYHGKF7UOMDWVEF4JANCNFSM5MKFVWKQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@hg111 that would explain the issue; perhaps open a feature request on depthai-core to support uvc on aarch64 systems as well. |
|
Will do. Thanks!
…On Wed, Feb 1, 2023 at 7:20 AM Erol444 ***@***.***> wrote:
@hg111 <https://github.com/hg111> that would explain the issue; perhaps
open a feature request on depthai-core
<https://github.com/luxonis/depthai-core>
https://github.com/luxonis/[depthai-core](https://github.com/luxonis/depthai-core)
to support uvc on aarch64 systems as well.
Thanks, Erik
—
Reply to this email directly, view it on GitHub
<#616 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZE7VRBEKZM6RVDYIUUCALWVJ5LJANCNFSM5MKFVWKQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Raspberry Pi4B + Oak-D Pro Successfully uninstalled opencv-python-4.10.0.84 |
|
@Jai-GAY you'd want to use numpy 1.x. I'd suggest to use UVC example directly: |
|
tried this, and it seems okay after I ran this requirement. python3 cam_test.py |
Describe the bug
Running
python3 demo_script.py --app uvcwith OAK-D-Lite creates /dev/video* device(s) only for a few seconds, the camera then disconnects and reconnects again as a non-uvc device, the /dev/video* devices disappear.To Reproduce
(interlaced with console and dmesg outputs)
dmesg:v4l2-ctl --list-device:python3 depthai_demo.py --app uvcpython3 depthai_demo.py --app uvcconsole:dmesg:/dev/video*devices. Also, the app uses 100 % of one CPU core.v4l2-ctl --list-device:Sometimes, however it takes some time (on the order of seconds, or lower 10s of secods) during which the
/dev/video*devices are present:Sometimes I also get the following segfault from
depthai_demo.py(and in that case it does not use up 100 % of CPU, but does not exit either, I still have to Ctrl-C it):The two "sometimes" alternatives happen seemingly at random, I have not noticed any pattern.
Expected behavior
The UVC app should work, i.e. provide a working UVC device(s).
System log
Additional context
The OAK-D-Lite is connected via USB-C to USB-A cable, sadly only an USB 2 cable. I'm getting an USB 3.1 cable very soon.
The text was updated successfully, but these errors were encountered: