I just got my OAK-1 and in trying the demo app, I have a few questions: And yes, I am using the USB3 cable that came with the device and it is plugged into a USB3 port. I am on Windows 10 OS build # 19045.3086. The max FPS I can get in the demo app is 60fps when the OAK-1 OV9782 supports 120fps at three different resolutions. Is the demo app somehow limited or what am I missing? In the Camera tab, there is no THE_400_P Resolution option, is this an oversight? In the Misc. tab, when I Run UVC Mode (Webcam) the terminal output is [ColorCamera(0)] [error] Still capture ignored, as the output is not connected . In OBS, when I try to set a new Video Capture Device I see the now new option S_VIDEO_CONTROL_1 but it prints the aforementioned error indefinitely. Is this expected? In testing depthai-unity I noticed the examples don't use WebCamTexture , WebCamDevice , and WebCamTexture.devices like I expected. Is there a particular reason for this? Related to the previous question, when I apply step 3 (UVC Mode (Webcam)) I also see the S_VIDEO_CONTROL_1 option resulting from my WebcamTexture.devices query in a custom webcam selection list that works with other webcams. However when I select S_VIDEO_CONTROL_1 , I get the error: Could not connect pins - RenderStream() . I'll look into this more, but if you have any thoughts or insight, please share.

Hi luxd Depthai demo is processing multiple streams at once. You can try only using one camera at the time and set it to 120fps. It should work fine for all three resolutions. 400P resolution is afaik only available for mono cameras (set in the API ). For the rest I'm not sure. The UVC webcam mode runs fine on its own, but does crash when using it as capture inside OBS. cc @erik Thanks, Jaka

Thanks jakaskerl . The OAK-1 only has the Color sensor and no mono sensors so how do I "You can try only using one camera at the time and set it to 120fps". afaict this is what I already tried unless I'm misunderstanding you. If this is the case then the docs for the OAK-1 OV9782 variant may need updating as they suggest the "THE_400_P" is a supported resolution for 120fps.

OAK-1 FF OV9782 Demo Questions

luxd

I just got my OAK-1 and in trying the demo app, I have a few questions:

And yes, I am using the USB3 cable that came with the device and it is plugged into a USB3 port. I am on Windows 10 OS build # 19045.3086.

The max FPS I can get in the demo app is 60fps when the OAK-1 OV9782 supports 120fps at three different resolutions. Is the demo app somehow limited or what am I missing?
In the Camera tab, there is no THE_400_PResolution option, is this an oversight?
In the Misc. tab, when I Run UVC Mode (Webcam) the terminal output is [ColorCamera(0)] [error] Still capture ignored, as the output is not connected. In OBS, when I try to set a new Video Capture Device I see the now new option S_VIDEO_CONTROL_1 but it prints the aforementioned error indefinitely. Is this expected?
In testing depthai-unity I noticed the examples don't use WebCamTexture, WebCamDevice, and WebCamTexture.devices like I expected. Is there a particular reason for this?
Related to the previous question, when I apply step 3 (UVC Mode (Webcam)) I also see the S_VIDEO_CONTROL_1 option resulting from my WebcamTexture.devices query in a custom webcam selection list that works with other webcams. However when I select S_VIDEO_CONTROL_1, I get the error: Could not connect pins - RenderStream(). I'll look into this more, but if you have any thoughts or insight, please share.

jakaskerl

Hi luxd

Depthai demo is processing multiple streams at once. You can try only using one camera at the time and set it to 120fps. It should work fine for all three resolutions.
400P resolution is afaik only available for mono cameras (set in the API).

For the rest I'm not sure. The UVC webcam mode runs fine on its own, but does crash when using it as capture inside OBS. cc @erik

Thanks,
Jaka

luxd

Thanks jakaskerl.

The OAK-1 only has the Color sensor and no mono sensors so how do I "You can try only using one camera at the time and set it to 120fps". afaict this is what I already tried unless I'm misunderstanding you.
If this is the case then the docs for the OAK-1 OV9782 variant may need updating as they suggest the "THE_400_P" is a supported resolution for 120fps.

jakaskerl

Hi luxd
Sorry, I meant to say run only the camera without NN inferencing and such. Could you try this script?

#!/usr/bin/env python3

import cv2
import depthai as dai
import datetime

# Create pipeline
pipeline = dai.Pipeline()

# Define sources and outputs
camRgb = pipeline.create(dai.node.ColorCamera)

xoutRgb = pipeline.create(dai.node.XLinkOut)
xoutRgb.setStreamName('rgb')

camRgb.setResolution(dai.ColorCameraProperties.SensorResolution.THE_720_P)
camRgb.setFps(90)

camRgb.video.link(xoutRgb.input)

# Connect to device and start pipeline
with dai.Device(pipeline) as device:

    # Output queues will be used to get the grayscale frames from the outputs defined above
    prev_ts = datetime.timedelta(seconds=0)
    qRgb = device.getOutputQueue(name="rgb", maxSize=4, blocking=False)

    while True:
        # Instead of get (blocking), we use tryGet (non-blocking) which will return the available data or None otherwise
        inRgb = qRgb.tryGet()
        if inRgb is not None:
            # calculate fps
            fps = 1.0 / (inRgb.getTimestamp() - prev_ts).total_seconds()
            print("rgb camera fps: {:.1f}".format(fps))

            prev_ts = inRgb.getTimestamp()
            cv2.imshow("rgb", inRgb.getCvFrame())

        if cv2.waitKey(1) == ord('q'):
            break

Thanks,
Jaka

luxd

jakaskerl Yea, I had already unchecked AI Properties so the NN wasn't running. I'm in C++ land and will try the suggestion, but I guess my initial question still stands: can you (anyone) get 90fps+ or not in the demo app?

jakaskerl

Hi luxd
Oh, right, yes c++; you can try chatGPT for conversion.
I wasn't able to run it 60+ in the demo app, no. Due to how the demo is set up I cannot isolate a mono camera (I'm on OAK-D); max I can get is 45.

Thanks,
Jaka