How to get 60 fps on OAK-1

vr2025

Hello,

I am looking for examples that can get the OAK-1 to output 60 fps as specified on the product webpage. I expected to see 60 fps when using the right hardware (USB gen 3.2, high quality cables, etc) but the fps seems to be capped to 30. The following code is what I have using depthai V3 to create the pipline that I use for previewing or recording video:
def create_pipeline():

pipeline = dai.Pipeline()

cam = pipeline.create(dai.node.Camera).build(dai.CameraBoardSocket.CAM_A)

cam_out = cam.requestOutput((FRAME_WIDTH, FRAME_HEIGHT), dai.ImgFrame.Type.NV12)

video_enc = pipeline.create(dai.node.VideoEncoder)

video_enc.setDefaultProfilePreset(FPS, dai.VideoEncoderProperties.Profile.MJPEG)

cam_out.link(video_enc.input)
control_in = cam.inputControl
return pipeline, cam_out, video_enc, control_in

If i do: cam_out = cam.requestOutput((FRAME_WIDTH, FRAME_HEIGHT), dai.ImgFrame.Type.NV12, fps=60),
I get the error: "RuntimeError: Camera(0) - Desired FPS 60 is higher than max FPS of the sensor config: 30.3"
Is there a way to modify the sensor config to enable 60 fps?
I saw some snippets about setting USB speed to SUPER PLUS somewhere but it was for V2 and I'm not sure how to do it for V3 or if it would even work.
Any help is much appreciated.

OskarSonc

Hey @vr2025 - You’re hitting the full-resolution sensor mode, which is limited to 30 FPS, so asking for 60 triggers that error. On OAK-1, 60 FPS is only available in the 1080p mode.
USB speed isn’t the limit here – it’s just the selected sensor mode.

Thanks,
Oskar

vr2025

Hi Oskar,

Thanks for the input. I'm trying to find a reference to do this, but no luck.

How does one set the sensor mode? I see some references related to depthaiV2 such as the following from luxonis/depthai-coreblob/main/V2V3PortinGuide.md :
camRgb.setBoardSocket(dai.CameraBoardSocket.CAM_A)
camRgb.setResolution(dai.ColorCameraProperties.SensorResolution.THE_1080_P)
camRgb.setVideoSize(1920, 1080)

Is this what you are referring to? If so, what is the equivalent for DepthaiV3?

As I understand, V3 uses 'Camera' instead of ColorCamera, but I am still at a loss as to how to set the camera mode to 1080p.

OskarSonc

Hey @vr2025 - In v3 the sensor mode is selected directly in the build() call. That replaces the old setResolutionapproach from v2. For 1080p60 you’d do:

cam = pipeline.create(dai.node.Camera)
cam.build(dai.CameraBoardSocket.CAM_A, (1920, 1080), 60)

cam_out = cam.requestOutput((1920, 1080), dai.ImgFrame.Type.NV12, fps=60)

The build(..., (1920,1080), 60) part is what puts the camera into the 1080p/60 sensor mode, and requestOutputjust defines the output stream size/FPS.

Hope this helps,
Oskar

vr2025

Hi @OskarSonc , thanks for your input.

Unfortunately, I see an error with the following updated code:
pipeline = dai.Pipeline()

cam = pipeline.create(dai.node.Camera)

cam.build(dai.CameraBoardSocket.CAM_A,(1920,1080),60)

cam_out = cam.requestOutput((1920, 1080), dai.ImgFrame.Type.NV12,fps=60)

video_enc = pipeline.create(dai.node.VideoEncoder)

video_enc.setDefaultProfilePreset(FPS, dai.VideoEncoderProperties.Profile.MJPEG)

cam_out.link(video_enc.input)

In: cam.build(dai.CameraBoardSocket.CAM_A,(1920,1080),60)

RuntimeError: Invalid sensor FPS specified, supported range is 0.735000 - 35.000000

OskarSonc

@vr2025 - hm this is weird. Which sensor is on your device? Also can you chechk you have latest DepthAiv3 installed?
You can run this short script to get all available resolutions/fps for your device:

import depthai as dai

with dai.Device() as dev:
    print("Sensors:", dev.getCameraSensorNames())
    for cf in dev.getConnectedCameraFeatures():
        if cf.socket == dai.CameraBoardSocket.CAM_A:
            print("CAM_A configs:")
            for cfg in cf.configs:
                print(cfg)

Let me know what you get.

Thanks,
Oskar

vr2025

Hi @OskarSonc ,

I am using the OAK-1 Lite, which has the IMX214. Here's the spec page of the product on the store page:

On the description tab, it says 60fps is possible with MJPEG:
RVC2 architecture on-board features:

4 TOPS of processing power (1.4 TOPS for AI - RVC2 NN Performance)
Run any AI model, even custom architectured/built ones (models need to be converted)
Encoding: H.264, H.265, MJPEG - 4K/30FPS, 1080P/60FPS

Using your code, I see the following:

Sensors: {<CameraBoardSocket.CAM_A: 0>: 'IMX214'}

CAM_A configs:

{width: 2104, height: 1560, minFps: 1.4, maxFps: 30.3, type: COLOR, fov: {x:0, y: 0, width: 4208, height: 3120}}

{width: 1920, height: 1080, minFps: 0.735, maxFps: 35, type: COLOR, fov: {x:184, y: 480, width: 3840, height: 2160}}

{width: 3840, height: 2160, minFps: 1.4, maxFps: 34.3, type: COLOR, fov: {x:184, y: 480, width: 3840, height: 2160}}

{width: 4056, height: 3040, minFps: 1.4, maxFps: 29.4, type: COLOR, fov: {x:76, y: 40, width: 4056, height: 3040}}

{width: 4208, height: 3120, minFps: 1.4, maxFps: 28.5, type: COLOR, fov: {x:0, y: 0, width: 4208, height: 3120}}

OskarSonc

Hey @vr2025 — that explains it. Since you’re using the OAK-1 Lite, the sensor is IMX214. IMX214 doesn’t have a 1080p60 mode, and its maximum full-resolution framerate is about 35 fps, which is why build(..., 60) fails.

The product page hadn’t been updated(we will update it right now), but the sensor spec page is correct:
https://docs.luxonis.com/hardware/sensors/IMX214

Sorry for the confusion - I hope this is not a big problem, your device is working normally, it just can’t do 60 fps at 1080p.
Thanks for letting us know!

Best,
Oskar

vr2025

I see, that is unfortunate as it is a big problem and will set me back quite a bit. I purchased the cameras based on this spec and was hoping to scale to large volumes. Is there a way to somehow enable 60fps through firmware? It looks like the sensor should be capable of 60 fps based on Sony's datasheet: https://www.mouser.com/datasheet/2/897/ProductBrief_IMX214_20150428-1289331.pdf

OskarSonc

@vr2025 - I totally get you... Hm I could ask our dev team, but so far there were no good answers...
Could you maybe switch to the non-lite version of OAK-1?
It's the same size, but it supports 60fps....

vr2025

I see, yes that could be a good solution moving forwards. Thanks for the suggestion. I have a follow up on that.

With my current code below, what is happening? Is it cropping to 4k then binning? or is it taking a full-res pic, then resizing to 1080p?

I am asking so that I have a realistic expectation of how the FOV would be for the non-lite version if I go with a config that does >=60fps. Wondering if I should go with the THE_1080P mode or THE_2024X1520 mode to retain the same FOV that I have been working with. OR would the same code below automatically give me 60fps if I set fps to 60?

cam = pipeline.create(dai.node.Camera).build(dai.CameraBoardSocket.CAM_A)

cam_out = cam.requestOutput((FRAME_WIDTH, FRAME_HEIGHT), dai.ImgFrame.Type.NV12)

OskarSonc

Hey @vr2025 In v3 your snippet lets the Camera auto-pick a sensor mode (default 30 fps), and the default resize mode is CROP. So if FRAME_WIDTH, FRAME_HEIGHT = 1920, 1080 it uses a 16:9 window on the sensor and scales to 1080p. it’s not reading the full 4:3 frame and then resizing.
On the non-lite OAK-1 with IMX378, 1080p60 is that 16:9 crop. If you want to keep a 4:3-like FOV at ≥60 fps, use the 2024×1520 sensor mode.
This are the available configs for the IMX378:
Sensors: {<CameraBoardSocket.CAM_A: 0>: 'IMX378'}
CAM_A configs:
{width: 1920, height: 1080, minFps: 2.03, maxFps: 60, type: COLOR, fov: {x:108, y: 440, width: 3840, height: 2160}}
{width: 3840, height: 2160, minFps: 1.42, maxFps: 42, type: COLOR, fov: {x:108, y: 440, width: 3840, height: 2160}}
{width: 4056, height: 3040, minFps: 1.42, maxFps: 30, type: COLOR, fov: {x:0, y: 0, width: 4056, height: 3040}}
{width: 1352, height: 1012, minFps: 1.25, maxFps: 52, type: COLOR, fov: {x:0, y: 0, width: 4056, height: 3036}}
{width: 2024, height: 1520, minFps: 2.03, maxFps: 85, type: COLOR, fov: {x:4, y: 0, width: 4048, height: 3040}}

If you need wider view we have W version available too...

vr2025

Hi Oskar,

Thanks for your support. I will try out this camera and reach out if I have any questions.

OskarSonc

vr2025 - happy to help 🙂