search

bytedeco / procamcalib

A User-Friendly Method to Calibrate Cameras and Projector-Camera Systems
GNU General Public License v2.0
73 stars 26 forks source link

RealSense F200 enable_stream error #13

Closed xsorifc28 closed 6 years ago

xsorifc28 commented 6 years ago

I receive the following error when running the calibrator with a RealSense F200 camera.

failed to fetch unpacker, most likely because enable_stream was not called

I've built the RealSense drivers for Ubuntu 14.04 using the provided instructions and the examples work fine.

I appreciate any insight you might have regarding this.

img_20171109_143810

saudet commented 6 years ago

@poqudrof any ideas?

poqudrof commented 6 years ago

Hello, I am not sure how well the librealsense works with procamcalib. Anyway, you don't really need the librealsense drivers to work with procamcalib.

  1. Plug the camera.
  2. Install the librealsense drivers (optionnal). You can get the color feed using the linux UVC drivers. You can check if it works with the program guvcview. With FFMEPG use /dev/video0 as device, OpenCV use 0.
  3. Use the FFMPEG or OpenCV drivers to load the realsense camera.
  4. Start the calibration.

If you need to calibrate with IR feeds, we can either try to patch the software, or you can calibrate with the color camera then use calibration from the device. The Realsense cameras provide extrinsic calibration for each camera (color - IR - IR2 - depth).

Please tell me if you have another use / request. Cheers, Jeremy.

xsorifc28 commented 6 years ago

I was able to fix the issue by referencing this pr. Seems like later in the development this fix was removed.

saudet commented 6 years ago

The last release of ProCamCalib was last year, so it doesn't contain that fix yet. Replacing modules/javacv.jar with the one from JavaCV 1.3.3 should work though. In any case, glad to hear it works! Thanks for the feedback.

saudet commented 6 years ago

Version 1.4 has been released and includes the fix. Enjoy!

saudet commented 6 years ago

So, this wasn't fixed in latest release of JavaCV? Could you send a PR to reapply the fix? Thanks!