On 06/16/2010 12:48 PM, Jack O'Quin wrote: > On Wed, Jun 16, 2010 at 12:13 PM, Patrick Beeson wrote: >> >>> The camera's tech manual says it supports *both* "absolute" (float) >>> and "relative" (unsigned int) values for shutter. I assumed (naively) >>> that when absolute is available that would be better to use. >>> >>> Still not sure why set_absolute_value() is not working. There don't >>> seem to be many absolute camera features around, yet. Does anyone have >>> a camera other than the Sony XCD series with an absolute feature >>> value? >>> >> >> Jack, it seems that shutter is the only feature that uses absolute on our >> the Sony XCD models. I looked atthe coriander source, and it NEVER uses the >> 'absolute' calls, it relys purely on the non-absolute calls. >> Can we simply change the code to not use absolute settings for now? If a >> camera works in Coriander, then we'd like it to work in camera1394 as well, >> which means, not using float values, but uints. >> >> > > Coriander does call dc1394_feature_set_absolute_value() in tools.c > SetAbsValue(), called from on_abs_entry_activate() in callbacks.c. I got the coriander source, and ran it with print statements, then immediate returns from functions like SetAbsValue(), and these functions are never actually called. > > If there are not any other absolute value features of interest, your > workaround may be our best option for this release. > > Would you send me your patch, please? My "patch" does not work (a bug was making it appear to work). You are correct is stating that set_absolute_value() succeeds despite the fact that it really doesn't.