Thread: [libdc] libdc1394 warning: packet ___ had error status 0 (64-bit Mac OS X 10.5.8)
Capture and control API for IIDC compliant cameras
Brought to you by:
ddouxchamps,
gordp
From: Mark J. <Mar...@ma...> - 2009-12-29 21:48:31
|
Hi everyone, On 64-bit Mac OS X 10.5.8 I am seeing the warning that others have seen and I am also seeing that every frame returned is reported as corrupt (dc1394_capture_is_frame_corrupt() returns true) though they seem to look fine visually. For an AVT Guppy GF 033C in 8-bit mono 640x480, I see that the frame is corrupt and the values asked about in a previous thread are: image_bytes 307200 packet_size 2560 packets_per_frame 120 The warning that appears is: libdc1394 warning: packet 119 had error status 0 It seems to be the same every time for that camera. However, using a PointGrey Dragonfly in 16-bit mono 640x480 I see: image_bytes 614400 packet_size 2560 packets_per_frame 240 with warning: libdc1394 warning: packet 239 had error status 0 This is on Mac OS X 10.5.8 using a 64-bit version of libdc1394 2.1.2 and a 64-bit application. Also, this same application code and libdc1394 2.1.2 works fine on 64-bit Debian 5 Linux. I don't think this is a benign warning since it renders dc1394_capture_is_frame_corrupt() unusable to find truly corrupt frames. Is there any additional information I can provide or any debugging steps that I can take that might be helpful? Thanks, Mark |
From: David C M. <dcm@MIT.EDU> - 2009-12-30 06:26:28
|
Hi Mark, Thanks for confirming the error. This is consistent with what others have reported -- it's always the final packet of the image that the status info does not seem to get written correctly. I would love for someone to find a workaround to this problem. This is definitely Mac OS specific, and started with either 10.4 or 10.5. The libdc1394 code is fairly complicated: Basically, a "DMA program" is constructed with a descriptor for each packet. This program is then submitted to the firewire driver. The DMA program asks for each packet's status info to be reported, but for some reason, the last packet's status info is not written. An easy workaround would be to just skip the check for the final packet's status. We may have to do this in order to prevent the warning. However, it might be that some simple and innocuous change to the construction of the DMA program will workaround this issue. I have seen that type of quirky behavior with the Mac OS firewire driver before. Any help is appreciated since I don't have a Mac OS box anymore. Thanks, David Quoting Mark Jones <Mar...@ma...>: > Hi everyone, > > On 64-bit Mac OS X 10.5.8 I am seeing the warning that others have > seen and I am also seeing that every frame returned is reported as > corrupt (dc1394_capture_is_frame_corrupt() returns true) though they > seem to look fine visually. > > For an AVT Guppy GF 033C in 8-bit mono 640x480, I see that the frame > is corrupt and the values asked about in a previous thread are: > > image_bytes 307200 packet_size 2560 packets_per_frame 120 > > The warning that appears is: > > libdc1394 warning: packet 119 had error status 0 > > It seems to be the same every time for that camera. > > However, using a PointGrey Dragonfly in 16-bit mono 640x480 I see: > > image_bytes 614400 packet_size 2560 packets_per_frame 240 > > with warning: > > libdc1394 warning: packet 239 had error status 0 > > This is on Mac OS X 10.5.8 using a 64-bit version of libdc1394 2.1.2 > and a 64-bit application. > > Also, this same application code and libdc1394 2.1.2 works fine on > 64-bit Debian 5 Linux. > > I don't think this is a benign warning since it renders > dc1394_capture_is_frame_corrupt() unusable to find truly corrupt > frames. > > Is there any additional information I can provide or any debugging > steps that I can take that might be helpful? > > Thanks, > Mark > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Mailing list for libdc1394-devel > lib...@li... > https://lists.sourceforge.net/lists/listinfo/libdc1394-devel > |