Poor performance with v4l backend about nokhwa HOT 8 CLOSED

Im working on a fix in a local 0.10 branch.

from nokhwa.

@D1plo1d You should be able to fix it by using Callback Camera. That runs the camera in another thread, allowing you to decode frames in a different thread from the camera.

from nokhwa.

Are you using the camera in a dark or bright environment?

from nokhwa.

Pretty bright, it's not due to auto-exposure (it performs better with LinuxVideo in the same environment)

from nokhwa.

@l1npengtul Did you have any success improving the v4l2 performance? I'm also seeing between 8 and 18 fps on a system that normally performs much faster.

Edit: I am also seeing a low fps when I use the v4l crate directly. Maybe a problem on their end?

Edit 2: Nm, that was comparing MJPEG nokhwa vs a much slower v4l mode, changing v4l to MJPEG resulting in 20fps so there is something slow happening in nokhwa specifically.

from nokhwa.

@l1npengtul Did you have any success improving the v4l2 performance? I'm also seeing between 8 and 18 fps on a system that normally performs much faster.

Edit: I am also seeing a low fps when I use the v4l crate directly. Maybe a problem on their end?

Edit 2: Nm, that was comparing MJPEG nokhwa vs a much slower v4l mode, changing v4l to MJPEG resulting in 20fps so there is something slow happening in nohawk specifically.

Maybe its frame decoding taking too long?

Instead of frame, try frame_raw to see if you get the same performance

from nokhwa.

Instead of frame, try frame_raw to see if you get the same performance

Yup, that was it. frame_raw gets the same fps as using v4l directly.

from nokhwa.

This issue is a non-nokhwa issue. Closing.

from nokhwa.