Jack O'Quin

The exception text provided does not tell me what went wrong. What device are you using, and which Format7 mode? Please post the exact CameraInfo published by the driver, and...

That issue reported different information for some other camera, as best I can tell. I really need the exact CameraInfo for _this_ device, also the device's make, model and Format7...

@Lenskiy: please paste in one frame of your camera_info topic contents. You can use this command, or something similar depending on your actual topic name: ``` rostopic echo /camera/camera_info ```...

I suspect @ktossell is pointing us in the right direction. I don't see any [use cases in REP-0104](http://www.ros.org/reps/rep-0104.html#use-cases), that are exactly like this. In [cropped video mode](http://www.ros.org/reps/rep-0104.html#cropped-video-mode), the height and...

@Lenskiy: Any new information about this problem?

Thanks for the detailed report, @boblob. The driver [currently sets `do_rectify` automatically](https://github.com/ros-drivers/camera1394/blob/master/src/nodes/format7.cpp#L470) depending on whether it thinks the ROI matches the calibrated size. That `roiMatchesCalibration` logic looks incorrect for your...

I don't have any cameras that provide absolute parameters. I tried to write the code to support both, but have no doubt there could be problems. I suspect absolute parameters...

My initial DC1394 Features design coerced everything to floating point numbers in an effort to represent every possible value consistently. I had problems with implementing the absolute part of the...

What happens if you put integer values into the roslaunch file? How do dynamic reconfigure types interact with those in the ROS parameter server? I did not test that case....

> That's cool, but the proposal with +/- inf limits and an optional param to force 12-bit features instead of absolute features will definitely work and can be done in...