|
|
Kineme Video Tools with Point Grey FireFly MV (bumped to a new thread instead of just a comment on a previous topic...) I'm trying to get a Point Grey FireFly MV FFMV-03M2C firewire color camera working... Kineme Video Device Info is reporting the device is there and capable, using the CameraExplorer qtz shows the available settings, but no image ever is output. Looking at the console, I'm just seeing the camera failing to handshake due to some sort of color coding issue. Apr 12 12:48:41 *: [VTVideoInputPatch execute:time:arguments:] Waiting for transmission to begin... Apr 12 12:48:40 *: libdc1394 error: Format_7 Error_flag_1 is set: in _dc1394_v130_handshake (/Users/smokris/prj/qc/plugin/VideoTools/libdc1394/dc1394/format7.c, line 122): invalid image position, size, color coding or ISO speed Apr 12 12:48:40 *: libdc1394 error: Format_7 Error_flag_1 is set: in dc1394_format7_set_roi (/Users/smokris/prj/qc/plugin/VideoTools/libdc1394/dc1394/format7.c, line 803): Handshaking failed after setting color_coding Apr 12 12:48:41 *: libdc1394 error: Format_7 Error_flag_1 is set: in _dc1394_v130_handshake (/Users/smokris/prj/qc/plugin/VideoTools/libdc1394/dc1394/format7.c, line 122): invalid image position, size, color coding or ISO speed Apr 12 12:48:41 *: libdc1394 error: Format_7 Error_flag_1 is set: in dc1394_format7_set_roi (/Users/smokris/prj/qc/plugin/VideoTools/libdc1394/dc1394/format7.c, line 803): Handshaking failed after setting color_coding or similar errors: Apr 12 12:57:41 *: libdc1394 error: Format_7 Error_flag_1 is set: in _dc1394_v130_handshake (/Users/smokris/prj/qc/plugin/VideoTools/libdc1394/dc1394/format7.c, line 122): invalid image position, size, color coding or ISO speed Apr 12 12:57:41 *: libdc1394 error: Format_7 Error_flag_1 is set: in dc1394_format7_set_roi (/Users/smokris/prj/qc/plugin/VideoTools/libdc1394/dc1394/format7.c, line 803): Handshaking failed after setting color_coding Apr 12 12:57:48 *: libdc1394 error: Format_7 Error_flag_1 is set: in _dc1394_v130_handshake (/Users/smokris/prj/qc/plugin/VideoTools/libdc1394/dc1394/format7.c, line 122): invalid image position, size, color coding or ISO speed Apr 12 12:57:48 *: libdc1394 error: Format_7 Error_flag_1 is set: in dc1394_format7_set_roi (/Users/smokris/prj/qc/plugin/VideoTools/libdc1394/dc1394/format7.c, line 803): Handshaking failed after setting color_coding Apr 12 12:57:52 *: libdc1394 error: Format_7 Error_flag_1 is set: in _dc1394_v130_handshake (/Users/smokris/prj/qc/plugin/VideoTools/libdc1394/dc1394/format7.c, line 122): invalid image position, size, color coding or ISO speed Apr 12 12:57:52 *: libdc1394 error: Format_7 Error_flag_1 is set: in dc1394_format7_set_roi (/Users/smokris/prj/qc/plugin/VideoTools/libdc1394/dc1394/format7.c, line 803): Handshaking failed after setting color_coding This is after I've tried all possible resolutions and framerates, and thoroughly explored all color coding formats both manufacturer-documented and Kineme-suggested (MONO8, MONO16, RAW8, RAW16, YUV411, YUV422, YUV444, RGB8, Y8, Y16) and when I'm not getting "Invalid Color Coding" responses, I'm seeing "Waiting for transmission to begin..." and then nothing... I believe this camera only supports monochrome images in its standard non-Format 7 modes (with a QuickTime based video feed, I only see a monochrome image). Unfortunately, I need color output. The documentation for the camera suggests that color data is not retained when binning is used ("Color binning is not supported on the FMVU-03MTC or FFMV-03M2C. Color data is not maintained when operating these models in pixel binning mode."). So I guess that means if we use a Format 7 mode, we have to define the ROI but I'm not sure how? Kind of beyond my expertise by this stage. So no support yet using Kineme Video Input - any further suggestions?
|
Well, since the 10.6.3 update, I have been unable to locate the internal iSight but can locate the external iSight from the example composition Explorer. Are you on 10.6.3? Just wondered if it were related at all.
Yeah, just double checked, re-installed the tools plugin, fresh download od example composition, not even using a fresh set of patches works to find the internal iSight like the video input patch does at all.
I tried my FireFly camera on both 10.5.8/QC3 and 10.6.2/QC4 on two different Intel Macs, and there was no difference in behaviour so my problem seems to be platform independent.
I may be wrong, but isn't the internal iSight a USB camera anyway - unlike the original external iSight, so a libdc1394 solution (ie. Kineme's Video Tools) wouldn't work with it?
Thanks for the suggestion, anyhow. I wish video capture was simpler!
yep, you are right about the internal iSight. my mistake.
Yep... USB won't get recognized. I have a couple of Logitech cams that the patch won't recognize for sure. However, it's not exactly a big deal b/c I'm not going for high performance anyway. The Firewire solution is supposed to be for scenarios where every bit of performance counts, and latency is bad bad bad.
Here's a quick update for anyone who's interested:
It turns out that this monochrome image I was seeing (which is specified as "Y8" by the manufacturer, ie MONO8) was actually a half-resolution Bayer tiled image. That is, the individual monochrome pixels formed a 2x2 tile, with each pixel representing the GRGB intensities. I only found this out after trawling Point Grey's knowledge base.
After a bit of hacking around with Core Image kernels, and experimenting with the private CIDeBayer patch, I found I was able to reconstruct a 320x240 colour image. So it's nowhere near the 640x480 colour image I was expecting, and quite a lot of a disappointment. Messing with Point Grey's Windows utilities to adjust the camera's default settings didn't yeild any high resolution, so I can see this is going nowhere fast.
To bring this back on topic, it still wasn't ever possible to get an image via Kineme's Video Tools patch however. My lesson is learnt: stick with cheap and cheerful UVC class USB cameras - they may not be industrial quality but they're sure easier to get working!