From: Rogier W. <R.E.Wolff@BitWizard.nl> - 2011-05-29 13:30:15
|
On Sun, May 29, 2011 at 02:43:47PM +0200, Marcus Meissner wrote: > On Sat, May 28, 2011 at 02:36:53PM -0400, Santiago Andres Triana wrote: > > Hi, > > > > I am getting very slow capture and download times (approx. 18 secs) from a > > canon s400. I'm using the CLI. Is this a reasonable time? I wonder if it > > could be a worn/old/slow CF card issue or just that the camera itself is > > slow. Has anybody experienced this issue? Comments or help very much > > appreciated! > > If there are lots of pictures on the camera, there will be an > initial startup delay before the camera captures. (there should be > progress displayed during this). If not, it is something else ... > A debuglogfile (add --debug --debug-logfile=xx.log to the cmdline) > would help. Marcus, Isn't now the time to modify the code to postpone the "gather the info about all files on the device" step to whenever any of that info is required? All things that do something with the file info need to be wrapped in something that triggers gathering of the info if it hasn't been done before. Or is the library interface so badly designed that this is impossible? (it would be impossible if users of libgphoto are able to simply dereference the should-have-been-opague handles that refer to the camera.) At a later time, we can start thinking about gathering only the information required. For example, to GET a file whose filename is competely given, it should eventually not be neccesary to download all info about all files.... Roger. -- ** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 ** ** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 ** *-- BitWizard writes Linux device drivers for any device you may have! --* Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement. Does it sit on the couch all day? Is it unemployed? Please be specific! Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ |