On Sun, Dec 01, 2013 at 12:52:33AM +1300, Jehan Pagès wrote:
> Hi,
>
> On Sat, Nov 30, 2013 at 11:01 PM, Daniel P. Berrange <d...@berrange.com>
> wrote:
> > On Fri, Nov 29, 2013 at 04:46:50PM +1300, Jehan Pagès wrote:
> >> Hey,
> >>
> >> I saw these commits and focusing through entangle, which is an awesome
> >> addition.
> >> Unfortunately when I try any of [,.< >], I get a popup error:
> >> «
> >> Manual focus failed
> >>
> >> Manual focus control was not a range widget
> >> »
> >
> > Urgh, so looking the gphoto2 code the Canon cameras support manual
> > focus in a totally different way. Nikon cameras let you nudge the
> > focus point in arbitrary steps / granularity. Canon seems to be
> > limited to just 7 separate manual focus points which really sucks.
> > So I'll have to write some more code to deal with canon for this.
> >
>
> I see. Well indeed only 7 levels of granularity only does not look all
> that useful. :-/
Actually it is possible I mis-understood the way it works - I have a
feeling it might actually be 3 deltas in each direction - eg small
step change, medium step change, large step change.
> > Can you try to test in gphoto2 shell eg just set the autofocus config
> > parameter
> >
> > # gphoto --shell
>
> I assume you meant `gphoto2 --shell` because I can't see a command
> `gphoto` in any package.
>
> > > set-config-value /main/actions/autofocusdrive=1
> > ....
> > > set-config-value /main/actions/autofocusdrive=1
> > ....
> > > set-config-value /main/actions/autofocusdrive=1
> >
> > and see if the camera hangs in the same way.
>
> Just tested. It does. No error showing in the gphoto2 shell, but the
> camera shows busy forever. And same as in entangle, only the first
> call would actually focus something. Any subsequent call still shows
> no error, but no additional focus going on (of course, I moved the
> camera to be sure the focus point would be different).
>
> Interestingly if I quit gphoto2 shell and enter it again, then rerun
> the command, this time I get a "I/O in progress" error, which for once
> looks consistent with the "busy" camera.
>
> Below a copy-paste. Text after a '#' are obviously comments I added on
> the copy-paste, and were not written in the shell. :-)
>
> -------------------------------------------------------------------
> $ gphoto2 --shell
> gphoto2: {/mnt/dev/prog/crossroad} /> set-config-value
> /main/actions/autofocusdrive=1 # <- only here a focus happen!
> gphoto2: {/mnt/dev/prog/crossroad} /> set-config-value
> /main/actions/autofocusdrive=1 # <- no focus made!
> gphoto2: {/mnt/dev/prog/crossroad} />
> $ gphoto2 --shell # <- here I restart gphoto2 shell but I did not
> restart the camera after the previous commands.
> gphoto2: {/mnt/dev/prog/crossroad} /> set-config-value
> /main/actions/autofocusdrive=1
>
> *** Error ***
> Failed to set new configuration value 1 for configuration entry
> /main/actions/autofocusdrive.
> *** Error (-110: 'I/O in progress') ***
> gphoto2: {/mnt/dev/prog/crossroad} />
> -------------------------------------------------------------------
>
> Is that to say that the problem is upstream? Or is there more that you
> may have to understand to work with a Canon camera and gphoto2?
Ok, this is useful information. This is almost certainly a libgphoto2
bug. The best thing todo is to report this problem to the ligphoto2
mailing list directly. When reporting this, run the same 'gphoto2'
commands above, but adding the --debug when launching it. Then add
the debug logs as an attachment - that should give their devs enough
info to start debugging the problem.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
_______________________________________________
Entangle-devel mailing list
Entangle-devel@gna.org
https://mail.gna.org/listinfo/entangle-devel
