Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

60 fps ps3 eye cam linux #15

Closed
runningman84 opened this issue Dec 12, 2013 · 14 comments
Closed

60 fps ps3 eye cam linux #15

runningman84 opened this issue Dec 12, 2013 · 14 comments

Comments

@runningman84
Copy link

My framerate does not go above 30 even if I select 60 fps in the point tracker settings. Are 60 fps not supported on Linux?

@sthalik
Copy link
Member

sthalik commented Dec 13, 2013

They are. Just checked, works for me. Do the settings persist, or is there a bug where the UI values reverts back to 30?

For diagnostics, try another trackers or the "qv4l2" utility.

@runningman84
Copy link
Author

Ok qv4l2 doesn't get above 30 fps in 640x480 too. I use ubuntu 1310 which doesn't seem to include a patched driver which supports 60 fps. How do you get 60fps?

Btw. insted of the two text fields for the resolution I would recommend a drop down box with resolutions like
640x480
320x240
...

Right now opentrack crashes if you enter invalid resolutions like 639x480... this is not very user friendly.

@sthalik
Copy link
Member

sthalik commented Dec 14, 2013

What's your kernel version? You can build your own kernel with make-kpkg and the like.

Care has been taken to avoid crashes when camera fails to become opened. It's probably an issue with Canonical-supplied libv4l but I'll double-check.

sthalik added a commit that referenced this issue Dec 14, 2013
Reported-by: runningman84
GitHub: issue #15
@sthalik
Copy link
Member

sthalik commented Dec 14, 2013

Thanks for the report! Merging hysteresis support broke changing resolution on the fly. Fixed in master.

@runningman84
Copy link
Author

This is my running kernel version:
3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

@sthalik
Copy link
Member

sthalik commented Dec 14, 2013

That's unusual. Worked for me back when 3.11 was git only...

@sthalik
Copy link
Member

sthalik commented Jan 14, 2014

closing cantfix/abandoned

@sthalik sthalik closed this as completed Jan 14, 2014
@edwin-v
Copy link

edwin-v commented Jul 5, 2015

Interesting to find this closed. I still can't get my ps3eye to do 60 fps at 640x480. It's not the driver or anything because linuxtrack does 60 fps just fine. Is there anything specific that causes this? Maybe it's specific to the point tracker?

@sthalik
Copy link
Member

sthalik commented Jul 5, 2015

In OpenCV in cmake/OpenCVFindLibsVideo.cmake, find this block:

# --- V4L ---
ocv_clear_vars(HAVE_LIBV4L HAVE_CAMV4L HAVE_CAMV4L2 HAVE_VIDEOIO)
if(WITH_V4L)
  if(WITH_LIBV4L)
    CHECK_MODULE(libv4l1 HAVE_LIBV4L1)
    CHECK_MODULE(libv4l2 HAVE_LIBV4L2)
    if(HAVE_LIBV4L1 AND HAVE_LIBV4L2)

change it to:

# --- V4L ---
ocv_clear_vars(HAVE_LIBV4L HAVE_CAMV4L HAVE_CAMV4L2 HAVE_VIDEOIO)
if(WITH_V4L)
  if(WITH_LIBV4L)
    CHECK_MODULE(libv4l1 HAVE_LIBV4L1)
    CHECK_MODULE(libv4l2 HAVE_LIBV4L2)
    if(HAVE_LIBV4L2)

Modern distros don't ship libv4l1 anymore and failing this check makes it use inferior opencv capture module.

@edwin-v
Copy link

edwin-v commented Jul 5, 2015

It doesn't appear to work.

I recompiled everything and I get the following error:

VIDEOIO ERROR: V4L: setting property #5 is not supported

Which is the FPS iirc.

@sthalik
Copy link
Member

sthalik commented Jul 5, 2015

Then you don't have libv4l2-dev installed.

@edwin-v
Copy link

edwin-v commented Jul 5, 2015

Good call, it works now.

A wiki page with a few of those build details would probably help a lot.

@sthalik
Copy link
Member

sthalik commented Jul 5, 2015

Linux users are assumed to be familiar with programming. The software runs on Linux to use Linux development tools, like Valgrind, also to increase code quality by using portable calls. We don't support Linux as an OS for end-users with fully-blown instructions or binaries.

@sthalik
Copy link
Member

sthalik commented Jul 8, 2015

Filed an issue at http://code.opencv.org/issues/4471

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants