Nabble - gphoto-user

Re: changed behaviour for "camera_wait_for_event"

2009-12-18T09:15:43Z

Hello, Marcus!

I digged even deeper into this problem by some hacking. Here is what I
found out so far:

1. The difference in behaviour appeared in libgphoto2 2.4.5, when
large NIKON-oriented section appeared in camera_wait_for_event
function:

if ( (params->deviceinfo.VendorExtensionID == PTP_VENDOR_NIKON) &&
ptp_operation_issupported(params, PTP_OC_NIKON_CheckEvent)
) {.....}

So D80 is processed as NIKON with supported operation and D3000 is
processed as default camera. Condition above is evaluated as false for
it so the old behavoiur with two events per capture (FileAdded and
Unknown) is in place.

2. This section seems to perceive all events at a time in a strange
manner. I looked into PTPContainer on each call.

When I press capture button on camera one time before calling this
function, container has 3 items:
code 0x4006 (object added)
PTP_HANDLER_SPECIAL
code 0x400c (storage info changed)

When I press capture button on camera two times before calling this
function, container has 5 items:
code 0x4006 (object added)
PTP_HANDLER_SPECIAL
code 0x400c (storage info changed)
PTP_HANDLER_SPECIAL
code 0x400c (storage info changed)

For three shots there is 7 items:
code 0x4006 (object added)
PTP_HANDLER_SPECIAL
code 0x400c (storage info changed)
PTP_HANDLER_SPECIAL
code 0x400c (storage info changed)
PTP_HANDLER_SPECIAL
code 0x400c (storage info changed)

And so on. Each press adds a special handler and 0x400c event in
container. Since only 0x4006 code event is considered a file adding,
container of any size is always interpreted as one file and the rest
is ignored and not stored anywhere. The second wait command always
brings empty PTPContainer no matter how long the timeout is. So there
is no more queue of events and added files.

Sincerely,
Sergey Kruk
==================================
On Thu, Dec 10, 2009 at 12:18 PM, Marcus Meissner <marcus@...> wrote:

> On Mon, Dec 07, 2009 at 08:39:39PM +0300, Sergey Kruk wrote:
>> I use libgphoto2 to manage Nikon D80, D90 and D3000 cameras. Recently
>> I tried to move my project from libgphoto2-2.4.2 to 2.4.6 or 2.4.7 and
>> I noticed behaviour change, that was not mentioned in changelogs.
>> Since everything happens to one camera instace inside C program this
>> is better demostrated inside gphoto2 --shell (this cannot be seen in
>> command line version, only inside shell):
>>
>> 1. In 2.4.7 when I run inside shell "capture-image" followed by
>> "wait-event", the second one reports that a file was added -- the
>> captured one. And sometimes it gives error saying that file already
>> exists. That is not the case with 2.4.2, where capture command
>> followed by wait command could only give timeout.
>
> capture-image already reads until it gets 1 object added event
> itself.
>
> Only if you are shooting NEF+JPEG dual mode, wait-event should
> return new images.
>
> That it returned the image that capture-image already reported
> would have been a bug in 2.4.2.
>
>> 2. In 2.4.2 I could manually press camera's release button several
>> times while in the shell, and than run same number of times
>> "wait-event". Each time I would get next file name in FILEADDED event.
>> Now with 2.4.7 after i press camera's release button several times I
>> only get one "FILEADDED" event followed by timeouts. And files list is
>> never updated until I do somethig like "capture-image"
>
> If you are the gphoto2 shell prompt, gphoto is not polling the
> interrupt queue... So interrupts might get lost.
>
> The reliable way is to do:
> gphoto2 --wait-event 100s # 100 seconds
>
> (just 100 without s would be 100 events)
>
> and then do the shutter pressing actions.
>
> Or if you want to download FILEADDED files immediately, do
> gphoto2 --wait-event-and-download 100s
>
>> While first case is arguably a bug, the second one in my opinion clearly is.
>> Is "wait"-functionality supported or is it more of experimental
>> feature aside from main functionality? Should it be reported?
>
> Well, you have reported it by your mail. :)
>
> It is functionality that is developing, so it might have flaws. But for above
> purposes it should work, with the corner condition that wait-event runs for
> polling.
>
> Ciao, Marcus
>

------------------------------------------------------------------------------
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
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: Canon A1100 Capture problem

2009-12-16T00:24:04Z

On Tue, Dec 15, 2009 at 05:41:11PM -0800, Juan Martinez Osuna wrote:

>
> Hi to all.
>
> I have a Canon PowerShot A1100 IS camera. Gphoto detects the camera and
> I can download the files from the camera also, but I can't capture
> image or movie.
>
> The Error:
>
> lp-svsmith05@lp-svsmith05-laptop:~$ gphoto2 --capture-image
>
> *** Error ***
> An error occurred in the io-library ('Bad parameters'): No error
> description available
> ERROR: Could not capture.
> *** Error (-2: 'Bad parameters') ***
>
> I have search for information and I have found that certain Canon cameras
> have this problem due to SDK. But this camera model is listed in the
> gphoto2 list of compatible digital cameras also.
>
> Have any one solved this problem? is there a way to configure a mode in
> the camera to be controlled to remote capture?
>
> I have libgphoto and Gphoto2 both v2.4.7 and I am using Ubuntu.
> Thank you in advance for your help.
> Best Regards.

No, the PowerShot A1100 IS itself does not support remote capture.
http://www.usa.canon.com/consumer/controller?act=SDKHomePageAct&keycode=Sdk_Lic&fcategoryid=314&modelid=7474&id=3464

Has "NC NC NC" (non conforming) to any SDK version.

(The error is probably something else, it should report "capture not supported".)

Ciao, Marcus

------------------------------------------------------------------------------
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
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Canon A1100 Capture problem

2009-12-15T17:41:11Z

Hi to all.

I have a Canon PowerShot A1100 IS camera. Gphoto detects the camera and
I can download the files from the camera also, but I can't capture
image or movie.

The Error:

lp-svsmith05@lp-svsmith05-laptop:~$ gphoto2 --capture-image

*** Error ***
An error occurred in the io-library ('Bad parameters'): No error
description available
ERROR: Could not capture.
*** Error (-2: 'Bad parameters') ***

I have search for information and I have found that certain Canon cameras
have this problem due to SDK. But this camera model is listed in the
gphoto2 list of compatible digital cameras also.

Have any one solved this problem? is there a way to configure a mode in
the camera to be controlled to remote capture?

I have libgphoto and Gphoto2 both v2.4.7 and I am using Ubuntu.
Thank you in advance for your help.
Best Regards.

Juan F. Martinez Osuna
Electronic Design Engineer.

------------------------------------------------------------------------------
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
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: D300s

2009-12-14T10:13:31Z

Hi again,

Sorry for the delay, was a bit in a hurry. It does not seem for me that
nautilus is grabbing it:
andi@windlepoons:~$ gvfs-mount -l
Drive(0): 320 GB Hard Disk
Type: GProxyDrive (GProxyVolumeMonitorGdu)
Volume(0): Volume
Type: GProxyVolume (GProxyVolumeMonitorGdu)
Mount(0): Volume -> file:///media/Volume
Type: GProxyMount (GProxyVolumeMonitorGdu)
Drive(1): CD/DVD Drive
Type: GProxyDrive (GProxyVolumeMonitorGdu)
Drive(2): 251 GB Hard Disk
Type: GProxyDrive (GProxyVolumeMonitorGdu)
Volume(0): 74 MB Filesystem
Type: GProxyVolume (GProxyVolumeMonitorGdu)
Mount(0): 74 MB Filesystem -> file:///media/disk
Type: GProxyMount (GProxyVolumeMonitorGdu)
Volume(1): 20 GB Filesystem
Type: GProxyVolume (GProxyVolumeMonitorGdu)
Mount(0): 20 GB Filesystem -> file:///media/disk-2
Type: GProxyMount (GProxyVolumeMonitorGdu)
Volume(2): data_1
Type: GProxyVolume (GProxyVolumeMonitorGdu)
Mount(0): data_1 -> file:///media/data_1
Type: GProxyMount (GProxyVolumeMonitorGdu)
Mount(1): Music -> file:///home/andi/Music
Type: GProxyMount (GProxyVolumeMonitorGdu)
Mount(2): Pictures -> file:///home/andi/Pictures
Type: GProxyMount (GProxyVolumeMonitorGdu)
Mount(3): nas -> file:///home/andi/nas
Type: GProxyMount (GProxyVolumeMonitorGdu)
Mount(4): Stuff -> file:///home/andi/Stuff
Type: GProxyMount (GProxyVolumeMonitorGdu)
Mount(8): Movies -> file:///home/andi/Movies
Type: GProxyMount (GProxyVolumeMonitorGdu)

I saw that you added the D300s into the svn. The actual tarball didn't
compile for me, so i added the two lines to my library.c and compiled
them (this should be the output of libgphoto 2.4.7 now with D300s). It
worked once to get the listing of the camera with gphoto2 -L, but after
it never did again. I have attached a log file for the gphoto2 -L
command. Seems gphoto detects the camera, but still has a sequence
number mismatch.

Best Regards,
Andi

0.000009 main(2): ALWAYS INCLUDE THE FOLLOWING LINES WHEN SENDING DEBUG MESSAGES TO THE MAILING LIST:
0.000162 main(2): gphoto2 2.4.7
0.000212 main(2): gphoto2 has been compiled with the following options:
0.000257 main(2): + gcc (C compiler used)
0.000307 main(2): + popt (mandatory, for handling command-line parameters)
0.000362 main(2): + exif (for displaying EXIF information)
0.000414 main(2): + no cdk (for accessing configuration options)
0.000460 main(2): + no aa (for displaying live previews)
0.000511 main(2): + jpeg (for displaying live previews in JPEG format)
0.000562 main(2): + no readline (for easy navigation in the shell)
0.000618 main(2): libgphoto2 2.4.7
0.000675 main(2): libgphoto2 has been compiled with the following options:
0.000726 main(2): + gcc (C compiler used)
0.000775 main(2): + ltdl (for portable loading of camlibs)
0.000826 main(2): + EXIF (for special handling of EXIF files)
0.000877 main(2): libgphoto2_port 0.8.0
0.000929 main(2): libgphoto2_port has been compiled with the following options:
0.000982 main(2): + gcc (C compiler used)
0.001032 main(2): + ltdl (for portable loading of camlibs)
0.001082 main(2): + USB (libusb, for USB cameras)
0.001128 main(2): + serial (for serial cameras)
0.001184 main(2): + no resmgr (serial port access and locking)
0.001234 main(2): + no baudboy (serial port locking)
0.001284 main(2): + no ttylock (serial port locking)
0.001343 main(2): + no lockdev (serial port locking)
0.001398 main(2): CAMLIBS env var not set, using compile-time default instead
0.001452 main(2): IOLIBS env var not set, using compile-time default instead
0.001551 setting/gphoto2-setting.c(2): Creating $HOME/.gphoto
0.001705 setting/gphoto2-setting.c(2): Loading settings from file "/home/andi/.gphoto/settings"
0.002106 main(2): The user has not specified both a model and a port. Try to figure them out.
0.002187 gphoto2-port-info-list(2): Using ltdl to load io-drivers from '/usr/local/lib/libgphoto2_port/0.8.0'...
0.002402 gphoto2-port-info-list(2): Called for filename '/usr/local/lib/libgphoto2_port/0.8.0/disk'.
0.009810 gphoto2-port/disk(2): found 7 volumes
0.016604 gphoto2-port-info-list(2): Loaded 'Media 'Volume'' ('disk:/media/Volume') from '/usr/local/lib/libgphoto2_port/0.8.0/disk'.
0.016635 gphoto2-port-info-list(2): Loaded 'Media 'data_1'' ('disk:/media/data_1') from '/usr/local/lib/libgphoto2_port/0.8.0/disk'.
0.016648 gphoto2-port-info-list(2): Loaded 'Media 'Volume (ntfs)'' ('disk:/media/disk-2') from '/usr/local/lib/libgphoto2_port/0.8.0/disk'.
0.016660 gphoto2-port-info-list(2): Loaded 'Media 'Volume (ext3)'' ('disk:/') from '/usr/local/lib/libgphoto2_port/0.8.0/disk'.
0.016672 gphoto2-port-info-list(2): Loaded 'Media 'Volume (ext2)'' ('disk:/media/disk') from '/usr/local/lib/libgphoto2_port/0.8.0/disk'.
0.016687 gphoto2-port-info-list(2): Loaded '' ('^disk:') from '/usr/local/lib/libgphoto2_port/0.8.0/disk'.
0.016701 gphoto2-port-info-list(2): Called for filename '/usr/local/lib/libgphoto2_port/0.8.0/ptpip'.
0.016809 gphoto2-port-info-list(2): Loaded 'PTP/IP Connection' ('ptpip:') from '/usr/local/lib/libgphoto2_port/0.8.0/ptpip'.
0.016827 gphoto2-port-info-list(2): Loaded '' ('^ptpip') from '/usr/local/lib/libgphoto2_port/0.8.0/ptpip'.
0.016843 gphoto2-port-info-list(2): Called for filename '/usr/local/lib/libgphoto2_port/0.8.0/serial'.
0.016979 gphoto2-port-info-list(2): Loaded 'Serial Port 0' ('serial:/dev/ttyS0') from '/usr/local/lib/libgphoto2_port/0.8.0/serial'.
0.016998 gphoto2-port-info-list(2): Loaded 'Serial Port 1' ('serial:/dev/ttyS1') from '/usr/local/lib/libgphoto2_port/0.8.0/serial'.
0.017012 gphoto2-port-info-list(2): Loaded 'Serial Port 2' ('serial:/dev/ttyS2') from '/usr/local/lib/libgphoto2_port/0.8.0/serial'.
0.017026 gphoto2-port-info-list(2): Loaded 'Serial Port 3' ('serial:/dev/ttyS3') from '/usr/local/lib/libgphoto2_port/0.8.0/serial'.
0.017039 gphoto2-port-info-list(2): Loaded '' ('^serial') from '/usr/local/lib/libgphoto2_port/0.8.0/serial'.
0.017052 gphoto2-port-info-list(2): Called for filename '/usr/local/lib/libgphoto2_port/0.8.0/usb'.
0.492558 gphoto2-port-info-list(2): Loaded 'Universal Serial Bus' ('usb:') from '/usr/local/lib/libgphoto2_port/0.8.0/usb'.
0.492661 gphoto2-port-info-list(2): Loaded '' ('^usb:') from '/usr/local/lib/libgphoto2_port/0.8.0/usb'.
0.492727 gphoto2-port-info-list(2): Counting entries (15 available)...
0.492776 gphoto2-port-info-list(2): 11 regular entries available.
0.493338 gphoto2-abilities-list(2): Using ltdl to load camera libraries from '/usr/local/lib/libgphoto2/2.4.7'...
0.494918 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/adc65'.
0.494985 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/agfa_cl20'.
0.495032 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/aox'.
0.495077 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/barbie'.
0.495190 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/canon'.
0.495237 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/casio_qv'.
0.495283 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/clicksmart310'.
0.495329 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/digigr8'.
0.495375 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/digita'.
0.495421 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/dimagev'.
0.495466 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/dimera3500'.
0.495512 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/directory'.
0.495558 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/enigma13'.
0.495604 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/fuji'.
0.495650 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/gsmart300'.
0.495696 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/hp215'.
0.495742 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/iclick'.
0.495788 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/jamcam'.
0.495834 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/jd11'.
0.495879 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/jl2005a'.
0.495925 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/kodak_dc120'.
0.495971 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/kodak_dc210'.
0.496016 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/kodak_dc240'.
0.496062 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/kodak_dc3200'.
0.496107 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/kodak_ez200'.
0.496153 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/konica'.
0.496202 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/konica_qm150'.
0.496249 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/largan'.
0.496295 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/lg_gsm'.
0.496340 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/mars'.
0.496386 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/mustek'.
0.496432 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/panasonic_coolshot'.
0.496477 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/panasonic_dc1000'.
0.496523 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/panasonic_dc1580'.
0.496569 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/panasonic_l859'.
0.496615 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/pccam300'.
0.496660 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/pccam600'.
0.496706 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/polaroid_pdc320'.
0.496752 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/polaroid_pdc640'.
0.496797 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/polaroid_pdc700'.
0.496843 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/ptp2'.
0.496888 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/ricoh'.
0.496962 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/ricoh_g3'.
0.497008 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/samsung'.
0.497054 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/sierra'.
0.497100 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/sipix_blink2'.
0.497146 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/sipix_web2'.
0.497192 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/smal'.
0.497238 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/sonix'.
0.497284 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/sony_dscf1'.
0.497330 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/sony_dscf55'.
0.497376 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/soundvision'.
0.497421 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/spca50x'.
0.497467 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/sq905'.
0.497513 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/stv0674'.
0.497558 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/stv0680'.
0.497604 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/sx330z'.
0.497650 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/topfield'.
0.497695 gphoto2-abilities-list(2): Found '/usr/local/lib/libgphoto2/2.4.7/toshiba_pdrm11'.
0.497753 gp-abilities-list(2): Found 59 camera drivers.
0.519023 gphoto2-port-info-list(2): Counting entries (15 available)...
0.519063 gphoto2-port-info-list(2): 11 regular entries available.
0.519075 gphoto2-port(2): Creating new device...
0.519089 gphoto2-port-info-list(2): Getting info of entry 0 (15 available)...
0.519286 gphoto2-port(2): Setting settings...
0.519304 gphoto2-port(0): The operation 'update' is not supported by this device
0.519385 gphoto2-port-info-list(2): Getting info of entry 1 (15 available)...
0.519551 gphoto2-port(2): Setting settings...
0.519567 gphoto2-port(0): The operation 'update' is not supported by this device
0.519627 gphoto2-port-info-list(2): Getting info of entry 2 (15 available)...
0.519784 gphoto2-port(2): Setting settings...
0.519799 gphoto2-port(0): The operation 'update' is not supported by this device
0.519855 gphoto2-port-info-list(2): Getting info of entry 3 (15 available)...
0.520009 gphoto2-port(2): Setting settings...
0.520024 gphoto2-port(0): The operation 'update' is not supported by this device
0.520039 gphoto2-port-info-list(2): Getting info of entry 4 (15 available)...
0.520184 gphoto2-port(2): Setting settings...
0.520199 gphoto2-port(0): The operation 'update' is not supported by this device
0.520216 gphoto2-port-info-list(2): Getting info of entry 5 (15 available)...
0.520296 gphoto2-port(2): Setting settings...
0.520311 gphoto2-port-info-list(2): Getting info of entry 6 (15 available)...
0.520384 gphoto2-port(2): Setting timeout to 500 millisecond(s)...
0.520398 gphoto2-port(2): Setting settings...
0.520411 gphoto2-port-info-list(2): Getting info of entry 7 (15 available)...
0.520478 gphoto2-port(2): Setting timeout to 500 millisecond(s)...
0.520492 gphoto2-port(2): Setting settings...
0.520504 gphoto2-port-info-list(2): Getting info of entry 8 (15 available)...
0.520569 gphoto2-port(2): Setting timeout to 500 millisecond(s)...
0.520583 gphoto2-port(2): Setting settings...
0.520595 gphoto2-port-info-list(2): Getting info of entry 9 (15 available)...
0.520659 gphoto2-port(2): Setting timeout to 500 millisecond(s)...
0.520674 gphoto2-port(2): Setting settings...
0.520686 gphoto2-port-info-list(2): Getting info of entry 10 (15 available)...
0.520937 gphoto2-port(2): Setting timeout to 5000 millisecond(s)...
0.520957 gphoto2-port(2): Setting settings...
0.520970 libusb(2): gp_port_usb_update(old int=0, conf=-1, alt=-1), (new int=0, conf=-1, alt=-1)
0.520983 gphoto2-abilities-list.c(1): Auto-detecting USB cameras...
0.521474 gphoto2-port-usb(1): Looking for USB device (vendor 0x4b0, product 0x425)... found.
0.521617 gphoto2-port-usb(2): inep to look for is 81
0.521670 gphoto2-port-usb(1): Detected defaults: config 1, interface 0, altsetting 0, inep 81, outep 02, intep 83, class 06, subclass 01
0.521724 gphoto2-abilities-list.c(2): Found 'Nikon DSC D300s (PTP mode)' (0x4b0,0x425)
0.521788 gphoto2-port(2): Freeing port...
0.521851 gphoto2-port(2): Closing port...
0.522069 gphoto2-camera(2): Setting abilities ('Nikon DSC D300s (PTP mode)')...
0.522143 gphoto2-setting(2): Setting key 'model' to value 'Nikon DSC D300s (PTP mode)' (gphoto2)
0.522205 gphoto2-setting(2): Saving 2 setting(s) to file "/home/andi/.gphoto/settings"
0.522468 gphoto2-port-info-list(2): Looking for path 'usb:' (15 entries available)...
0.522578 gphoto2-port-info-list(2): Getting info of entry 10 (15 available)...
0.522639 gphoto2-camera(2): Setting port info for port 'Universal Serial Bus' at 'usb:'...
0.523503 gphoto2-port(2): Setting timeout to 5000 millisecond(s)...
0.523593 gphoto2-port(2): Setting settings...
0.523644 libusb(2): gp_port_usb_update(old int=0, conf=-1, alt=-1), (new int=0, conf=-1, alt=-1)
0.523703 gphoto2-setting(2): Setting key 'port' to value 'usb:' (gphoto2)
0.523757 gphoto2-setting(2): Saving 2 setting(s) to file "/home/andi/.gphoto/settings"
0.524063 foreach(2): Executing action 'List Files' for folder '/'.
0.524396 gphoto2-camera(2): Listing files in '/'...
0.524457 gphoto2-camera(2): Initializing camera...
0.524522 gphoto2-port-usb(1): Looking for USB device (vendor 0x4b0, product 0x425)... found.
0.524577 gphoto2-port-usb(2): inep to look for is 81
0.524627 gphoto2-port-usb(1): Detected defaults: config 1, interface 0, altsetting 0, inep 81, outep 02, intep 83, class 06, subclass 01
0.524680 gphoto2-camera(2): Loading '/usr/local/lib/libgphoto2/2.4.7/ptp2'...
0.525207 gphoto2-port(2): Opening USB port...
0.525274 libusb(2): gp_port_usb_open()
0.525366 libusb(2): claiming interface 0
0.525453 ptp2(2): maxpacketsize 512
0.525604 gphoto2-port(2): Setting timeout to 8000 millisecond(s)...
0.525671 ptp(2): PTP: Opening session
0.525732 gphoto2-port(2): Writing 16=0x10 byte(s) to port...
0.525789 gphoto2-port(3): Hexdump of 16 = 0x10 bytes follows:
0000 10 00 00 00 01 00 02 10-00 00 00 00 01 00 00 00 ................

0.526308 ptp2/ptp_usb_getresp(2): reading response
0.526371 ptp2/ptp_usb_getpacket(2): getting next ptp packet
0.526426 gphoto2-port(2): Reading 512=0x200 bytes from port...
0.526675 gphoto2-port(2): Could only read 12 out of 512 byte(s)
0.526738 gphoto2-port(3): Hexdump of 12 = 0xc bytes follows:
0000 0c 00 00 00 03 00 1e 20-00 00 00 00 ....... ....

0.526786 ptp2/usb_getresp(0): request code 0x1002 getting resp error 0x201e
0.526835 gphoto2-port(2): Setting timeout to 20000 millisecond(s)...
0.526889 gphoto2-port(2): Writing 12=0xc byte(s) to port...
0.526938 gphoto2-port(3): Hexdump of 12 = 0xc bytes follows:
0000 0c 00 00 00 01 00 01 10-01 00 00 00 ............

0.527039 ptp2/ptp_usb_getdata(2): reading data
0.527088 ptp2/ptp_usb_getpacket(2): getting next ptp packet
0.527135 gphoto2-port(2): Reading 512=0x200 bytes from port...
0.527290 gphoto2-port(2): Could only read 337 out of 512 byte(s)
0.527349 gphoto2-port(3): Hexdump of 337 = 0x151 bytes follows:
0000 51 01 00 00 02 00 01 10-01 00 00 00 64 00 06 00 Q...........d...
0010 00 00 64 00 13 6d 00 69-00 63 00 72 00 6f 00 73 ..d..m.i.c.r.o.s
0020 00 6f 00 66 00 74 00 2e-00 63 00 6f 00 6d 00 3a .o.f.t...c.o.m.:
0030 00 20 00 31 00 2e 00 30-00 00 00 00 00 2c 00 00 . .1...0.....,..
0040 00 01 10 02 10 03 10 04-10 05 10 06 10 07 10 08 ................
0050 10 09 10 0a 10 0b 10 0c-10 0d 10 0e 10 0f 10 14 ................
0060 10 15 10 16 10 1b 10 c0-90 c1 90 c2 90 c3 90 c4 ................
0070 90 c7 90 c8 90 c9 90 ca-90 cb 90 cc 90 cd 90 ce ................
0080 90 cf 90 00 92 01 92 02-92 03 92 04 92 05 92 06 ................
0090 92 01 98 02 98 03 98 05-98 0d 00 00 00 01 40 02 ..............@.
00a0 40 04 40 05 40 06 40 09-40 0a 40 0c 40 0d 40 08 @.@.@.@.@.@.@.@.
00b0 40 01 c1 02 c1 04 c1 15-00 00 00 01 50 03 50 04 @...........P.P.
00c0 50 05 50 07 50 08 50 0a-50 0b 50 0c 50 0d 50 0e P.P.P.P.P.P.P.P.
00d0 50 0f 50 10 50 11 50 13-50 18 50 1c 50 1e 50 1f P.P.P.P.P.P.P.P.
00e0 50 06 d4 07 d4 03 00 00-00 01 38 00 30 0d 38 07 P.........8.0.8.
00f0 00 00 00 01 38 00 30 01-30 0a 30 0d 38 06 30 02 ....8.0.0.0.8.0.
0100 30 12 4e 00 69 00 6b 00-6f 00 6e 00 20 00 43 00 0.N.i.k.o.n. .C.
0110 6f 00 72 00 70 00 6f 00-72 00 61 00 74 00 69 00 o.r.p.o.r.a.t.i.
0120 6f 00 6e 00 00 00 06 44-00 33 00 30 00 30 00 53 o.n....D.3.0.0.S
0130 00 00 00 06 56 00 31 00-2e 00 30 00 30 00 00 00 ....V.1...0.0...
0140 08 36 00 30 00 32 00 31-00 35 00 33 00 33 00 00 .6.0.2.1.5.3.3..
0150 00 - .

0.527439 ptp2/ptp_usb_getresp(2): reading response
0.527489 ptp2/ptp_usb_getpacket(2): getting next ptp packet
0.527538 gphoto2-port(2): Reading 512=0x200 bytes from port...
0.527861 gphoto2-port(2): Could only read 11 out of 512 byte(s)
0.527927 gphoto2-port(3): Hexdump of 11 = 0xb bytes follows:
0000 0c 00 00 00 03 00 01 20-00 00 00 ....... ...

0.527997 context(0): PTP: Sequence number mismatch 0 vs expected 1.
0.528089 context(0): PTP Error: bad parameter
0.528166 gphoto2-port(2): Closing port...
0.528336 context(0): An error occurred in the io-library ('Bad parameters'): No error description available
0.529220 gp-camera(2): Freeing camera...
0.529285 gphoto2-port(2): Freeing port...
0.529335 gphoto2-port(2): Closing port...
0.529446 gphoto2-filesystem(2): resetting filesystem
0.529502 libgphoto2/gphoto2-filesys.c(2): Clearing fscache LRU list...
0.529553 libgphoto2/gphoto2-filesys.c(2): fscache LRU list already empty
0.529603 gphoto2-filesystem(2): Internally deleting all folders from '/'...
0.529657 gphoto2-filesystem(2): Lookup folder '/'...
0.529708 gphoto2-filesystem(2): Found! / is 0x1c06430
0.529768 gphoto2-filesystem(2): Recurse delete folder 0x1c06430//

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev

_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: D300s

2009-12-12T12:31:50Z

On Sat, Dec 12, 2009 at 09:16:13PM +0100, Andreas Dielacher wrote:
> Marcus Meissner wrote:
> > On Sat, Dec 12, 2009 at 08:26:21PM +0100, Andreas Dielacher wrote:
> > Does "gphoto2 -L" work?
>
> Did not work, so i added the --debug switch:

> 0000 0c 00 00 00 03 00 03 20-04 00 00 ....... ...
>
> 0.624176 ptp2/usb_getresp(0): request code 0x1002 getting resp error 0x2003
> 0.624183 ptp2/camera_init(0): ptp_opensession returns 2003
> 0.624188 ptp(2): PTP: Opening session
> 0.624194 gphoto2-port(2): Writing 16=0x10 byte(s) to port...
> 0.624200 gphoto2-port(3): Hexdump of 16 = 0x10 bytes follows:
> 0000 10 00 00 00 01 00 02 10-00 00 00 00 01 00 00 00 ................
>
> 0.625159 ptp2/ptp_usb_getresp(2): reading response
> 0.625171 ptp2/ptp_usb_getpacket(2): getting next ptp packet
> 0.625181 gphoto2-port(2): Reading 512=0x200 bytes from port...
> 0.625428 gphoto2-port(2): Could only read 12 out of 512 byte(s)
> 0.625461 gphoto2-port(3): Hexdump of 12 = 0xc bytes follows:
> 0000 0c 00 00 00 03 00 01 20-00 00 00 00 ....... ....
>
> 0.625485 gphoto2-port(2): Setting timeout to 20000 millisecond(s)...
> 0.625512 gphoto2-port(2): Writing 12=0xc byte(s) to port...
> 0.625528 gphoto2-port(3): Hexdump of 12 = 0xc bytes follows:
> 0000 0c 00 00 00 01 00 01 10-01 00 00 00 ............
>
> 0.625753 ptp2/ptp_usb_getdata(2): reading data
> 0.625761 ptp2/ptp_usb_getpacket(2): getting next ptp packet
> 0.625768 gphoto2-port(2): Reading 512=0x200 bytes from port...
> 0.625959 gphoto2-port(2): Could only read 12 out of 512 byte(s)
> 0.625967 gphoto2-port(3): Hexdump of 12 = 0xc bytes follows:
> 0000 0c 00 00 00 03 00 1e 20-00 00 00 00 ....... ....
>
> 0.625978 ptp2/ptp_usb_getresp(2): reading response
> 0.625982 ptp2/ptp_usb_getpacket(2): getting next ptp packet
> 0.625986 ptp2/ptp_usb_getpacket(2): queuing buffered response packet
> 0.625992 ptp2/usb_getresp(0): request code 0x1001 getting resp error 0x201e
> 0.626007 context(0): PTP Session Already Opened

The communication is not in synch.

This could be the result of gvfs-gphoto2 , the Nautilus gphoto2 slave running
and grabbing the camera.

run:
gvfs-mount -l

to see if it is the case and
gvfs-mount -s gphoto2
to umount the camera from GVFS.

Ciao, Marcus

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: D300s

2009-12-12T12:16:13Z

Marcus Meissner wrote:
> On Sat, Dec 12, 2009 at 08:26:21PM +0100, Andreas Dielacher wrote:
> Does "gphoto2 -L" work?

Did not work, so i added the --debug switch:
0.615326 gphoto2-port-usb(1): Looking for USB device (class 0x6,
subclass, 0x1, protocol 0x1)... found.

0.615341 gphoto2-port-usb(2): inep to look for is 81

0.615355 gphoto2-port-usb(1): Detected defaults: config 1, interface 0,
altsetting 0, idVendor ID 04b0, idProduct 0425, inep 81, outep 02, intep
83
0.615374 gphoto2-abilities-list.c(2): Found 'USB PTP Class Camera'
(0x6,0x1,0x1)

0.615400 gphoto2-port(2): Freeing port...

0.615416 gphoto2-port(2): Closing port...

0.615692 gphoto2-camera(2): Setting abilities ('USB PTP Class
Camera')...

0.615714 gphoto2-setting(2): Setting key 'model' to value 'USB PTP Class
Camera' (gphoto2)

0.615732 gphoto2-setting(2): Saving 6 setting(s) to file
"/home/andi/.gphoto/settings"

0.615985 gphoto2-port-info-list(2): Looking for path 'usb:' (10 entries
available)...

0.616015 gphoto2-port-info-list(2): Getting info of entry 5 (10
available)...

0.616033 gphoto2-camera(2): Setting port info for port 'Universal Serial
Bus' at 'usb:'...

0.617274 gphoto2-port(2): Setting timeout to 5000 millisecond(s)...

0.617301 gphoto2-port(2): Setting settings...

0.617315 libusb(2): gp_port_usb_update(old int=0, conf=-1, alt=-1), (new
int=0, conf=-1, alt=-1)

0.617331 gphoto2-setting(2): Setting key 'port' to value 'usb:'
(gphoto2)

0.617346 gphoto2-setting(2): Saving 6 setting(s) to file
"/home/andi/.gphoto/settings"

0.618366 foreach(2): Executing action 'List Files' for folder '/'.

0.622143 gphoto2-camera(2): Listing files in '/'...

0.622166 gphoto2-camera(2): Initializing camera...

0.622216 gphoto2-port(0): The supplied vendor or product id (0x0,0x0) is
not valid.

0.622233 gphoto2-port-usb(1): Looking for USB device (class 0x6,
subclass, 0x1, protocol 0x1)... found.

0.622246 gphoto2-port-usb(2): inep to look for is 81

0.622257 gphoto2-port-usb(1): Detected defaults: config 1, interface 0,
altsetting 0, idVendor ID 04b0, idProduct 0425, inep 81, outep 02, intep
83
0.622272 gphoto2-camera(2): Loading '/usr/lib/libgphoto2/2.4.6/ptp2'...

0.622887 gphoto2-port(2): Opening USB port...

0.622908 libusb(2): gp_port_usb_open()

0.622972 libusb(2): claiming interface 0

0.623021 ptp2(2): maxpacketsize 512

0.623088 gphoto2-port(2): Setting timeout to 8000 millisecond(s)...

0.623109 ptp(2): PTP: Opening session

0.623131 gphoto2-port(2): Writing 16=0x10 byte(s) to port...

0.623149 gphoto2-port(3): Hexdump of 16 = 0x10 bytes follows:

0000 10 00 00 00 01 00 02 10-00 00 00 00 01 00 00 00 ................

0.623706 ptp2/ptp_usb_getresp(2): reading response
0.623731 ptp2/ptp_usb_getpacket(2): getting next ptp packet
0.623747 gphoto2-port(2): Reading 512=0x200 bytes from port...
0.624157 gphoto2-port(2): Could only read 11 out of 512 byte(s)
0.624169 gphoto2-port(3): Hexdump of 11 = 0xb bytes follows:
0000 0c 00 00 00 03 00 03 20-04 00 00 ....... ...

0.624176 ptp2/usb_getresp(0): request code 0x1002 getting resp error 0x2003
0.624183 ptp2/camera_init(0): ptp_opensession returns 2003
0.624188 ptp(2): PTP: Opening session
0.624194 gphoto2-port(2): Writing 16=0x10 byte(s) to port...
0.624200 gphoto2-port(3): Hexdump of 16 = 0x10 bytes follows:
0000 10 00 00 00 01 00 02 10-00 00 00 00 01 00 00 00 ................

0.625159 ptp2/ptp_usb_getresp(2): reading response
0.625171 ptp2/ptp_usb_getpacket(2): getting next ptp packet
0.625181 gphoto2-port(2): Reading 512=0x200 bytes from port...
0.625428 gphoto2-port(2): Could only read 12 out of 512 byte(s)
0.625461 gphoto2-port(3): Hexdump of 12 = 0xc bytes follows:
0000 0c 00 00 00 03 00 01 20-00 00 00 00 ....... ....

0.625485 gphoto2-port(2): Setting timeout to 20000 millisecond(s)...
0.625512 gphoto2-port(2): Writing 12=0xc byte(s) to port...
0.625528 gphoto2-port(3): Hexdump of 12 = 0xc bytes follows:
0000 0c 00 00 00 01 00 01 10-01 00 00 00 ............

0.625753 ptp2/ptp_usb_getdata(2): reading data
0.625761 ptp2/ptp_usb_getpacket(2): getting next ptp packet
0.625768 gphoto2-port(2): Reading 512=0x200 bytes from port...
0.625959 gphoto2-port(2): Could only read 12 out of 512 byte(s)
0.625967 gphoto2-port(3): Hexdump of 12 = 0xc bytes follows:
0000 0c 00 00 00 03 00 1e 20-00 00 00 00 ....... ....

0.625978 ptp2/ptp_usb_getresp(2): reading response
0.625982 ptp2/ptp_usb_getpacket(2): getting next ptp packet
0.625986 ptp2/ptp_usb_getpacket(2): queuing buffered response packet
0.625992 ptp2/usb_getresp(0): request code 0x1001 getting resp error 0x201e
0.626007 context(0): PTP Session Already Opened

*** Error ***
PTP Session Already Opened
0.626025 gphoto2-port(2): Closing port...
0.626097 context(0): An error occurred in the io-library ('Unspecified
error'): The supplied vendor or product id (0x0,0x0) is not valid.

*** Error ***
An error occurred in the io-library ('Unspecified error'): The supplied
vendor or product id (0x0,0x0) is not valid.
*** Error (-1: 'Unspecified error') ***

For debugging messages, please use the --debug option.
Debugging messages may help finding a solution to your problem.
If you intend to send any error or debug messages to the gphoto
developer mailing list <gphoto-devel@...>, please run
gphoto2 as follows:

env LANG=C gphoto2 --debug --debug-logfile=my-logfile.txt -L --debug

Please make sure there is sufficient quoting around the arguments.

0.626501 gp-camera(2): Freeing camera...
0.626509 gphoto2-port(2): Freeing port...
0.626515 gphoto2-port(2): Closing port...
0.626556 gphoto2-filesystem(2): resetting filesystem
0.626561 libgphoto2/gphoto2-filesys.c(2): Clearing fscache LRU list...
0.626565 libgphoto2/gphoto2-filesys.c(2): fscache LRU list already empty
0.626569 gphoto2-filesystem(2): Internally deleting all folders from '/'...
0.626575 gphoto2-filesystem(2): Lookup folder '/'...
0.626579 gphoto2-filesystem(2): Found! / is 0x22d4440
0.626583 gphoto2-filesystem(2): Recurse delete folder 0x22d4440

Andi

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: D300s

2009-12-12T11:46:19Z

On Sat, Dec 12, 2009 at 08:26:21PM +0100, Andreas Dielacher wrote:

> Hello,
>
> I recently got a D300s and tried to connect it under Kubuntu 9.10.
> digiKam (which uses libgphoto) is unable to connect. I tried with gtkam,
> digikam, command line and had no success. In command line i tried:
> gphoto2 --auto-detect --debug
> Here is the output:
> 0.000418 main(2): ALWAYS INCLUDE THE FOLLOWING LINES WHEN SENDING DEBUG
> MESSAGES TO THE MAILING LIST:
>
> 0.000495 main(2): gphoto2 2.4.5
>
>
> 0.000512 main(2): gphoto2 has been compiled with the following options:
>
>
> 0.000523 main(2): + gcc (C compiler used)
>
>
> 0.000534 main(2): + popt (mandatory, for handling command-line
> parameters)
>
> 0.000544 main(2): + exif (for displaying EXIF information)
>
>
> 0.000554 main(2): + cdk (for accessing configuration options)
>
>
> 0.000565 main(2): + aa (for displaying live previews)
>
>
> 0.000575 main(2): + jpeg (for displaying live previews in JPEG format)
>
>
> 0.000585 main(2): + readline (for easy navigation in the shell)
>
>
> 0.000600 main(2): libgphoto2 2.4.6
>
>
> 0.000618 main(2): libgphoto2 has been compiled with the following
> options:
>
> 0.000628 main(2): + gcc (C compiler used)
>
>
> 0.000641 main(2): + ltdl (for portable loading of camlibs)
>
>
> 0.000651 main(2): + EXIF (for special handling of EXIF files)
>
>
> 0.000664 main(2): libgphoto2_port 0.8.0
>
>
> 0.000677 main(2): libgphoto2_port has been compiled with the following
> options:
>
> 0.000688 main(2): + gcc (C compiler used)
>
>
> 0.000698 main(2): + ltdl (for portable loading of camlibs)
>
>
> 0.000708 main(2): + USB (libusb, for USB cameras)
>
>
> 0.000718 main(2): + serial (for serial cameras)
>
>
> 0.000728 main(2): + no resmgr (serial port access and locking)
>
>
> 0.000738 main(2): + no baudboy (serial port locking)
>
>
> 0.000748 main(2): + no ttylock (serial port locking)
>
>
> 0.000758 main(2): + no lockdev (serial port locking)
>
>
> 0.000769 main(2): CAMLIBS env var not set, using compile-time default
> instead
>
> 0.000779 main(2): IOLIBS env var not set, using compile-time default
> instead
>
> 0.000821 setting/gphoto2-setting.c(2): Creating $HOME/.gphoto
>
>
> 0.000928 setting/gphoto2-setting.c(2): Loading settings from file
> "/home/andi/.gphoto/settings"
>
> 0.001231 gphoto2-port-info-list(2): Using ltdl to load io-drivers from
> '/usr/lib/libgphoto2_port/0.8.0'...
>
> 0.001417 gphoto2-port-info-list(2): Called for filename
> '/usr/lib/libgphoto2_port/0.8.0/disk'.
>
> <snip>
>
> 0.010597 gphoto2-port-info-list(2): Could not load port driver list:
> 'Unspecified error'.
>
> 0.010618 gphoto2-port-info-list(2): Called for filename
> '/usr/lib/libgphoto2_port/0.8.0/ptpip'.
>
> 0.011039 gphoto2-port-info-list(2): Loaded 'PTP/IP Connection'
> ('ptpip:') from '/usr/lib/libgphoto2_port/0.8.0/ptpip'.
>
> 0.011067 gphoto2-port-info-list(2): Loaded '' ('^ptpip') from
> '/usr/lib/libgphoto2_port/0.8.0/ptpip'.
>
> 0.011084 gphoto2-port-info-list(2): Called for filename
> '/usr/lib/libgphoto2_port/0.8.0/serial'.
>
> 0.011643 gphoto2-port-info-list(2): Loaded 'Serial Port 0'
> ('serial:/dev/ttyS0') from '/usr/lib/libgphoto2_port/0.8.0/serial'.
>
> 0.011666 gphoto2-port-info-list(2): Loaded 'Serial Port 1'
> ('serial:/dev/ttyS1') from '/usr/lib/libgphoto2_port/0.8.0/serial'.
>
> 0.011682 gphoto2-port-info-list(2): Loaded 'Serial Port 2'
> ('serial:/dev/ttyS2') from '/usr/lib/libgphoto2_port/0.8.0/serial'.
>
> 0.011698 gphoto2-port-info-list(2): Loaded 'Serial Port 3'
> ('serial:/dev/ttyS3') from '/usr/lib/libgphoto2_port/0.8.0/serial'.
>
> 0.011714 gphoto2-port-info-list(2): Loaded '' ('^serial') from
> '/usr/lib/libgphoto2_port/0.8.0/serial'.
>
> 0.011729 gphoto2-port-info-list(2): Called for filename
> '/usr/lib/libgphoto2_port/0.8.0/usb'.
>
> 0.486913 gphoto2-port-info-list(2): Loaded 'Universal Serial Bus'
> ('usb:') from '/usr/lib/libgphoto2_port/0.8.0/usb'.
>
> 0.486951 gphoto2-port-info-list(2): Loaded '' ('^usb:') from
> '/usr/lib/libgphoto2_port/0.8.0/usb'.
>
> 0.486988 gphoto2-port-info-list(2): Counting entries (10 available)...
>
>
> 0.487005 gphoto2-port-info-list(2): 6 regular entries available.
>
>
> 0.487019 gphoto2-port-info-list(2): Counting entries (10 available)...
>
>
> 0.487034 gphoto2-port-info-list(2): 6 regular entries available.
>
>
> <snip>
> 0.578252 gphoto2-port-usb(1): Looking for USB device (class 0x6,
> subclass, 0x1, protocol 0x1)... found.
> 0.578268 gphoto2-port-usb(2): inep to look for is 81
> 0.578279 gphoto2-port-usb(1): Detected defaults: config 1, interface 0,
> altsetting 0, idVendor ID 04b0, idProduct 0425, inep 81, outep 02, intep 83
> 0.578297 gphoto2-abilities-list.c(2): Found 'USB PTP Class Camera'
> (0x6,0x1,0x1)
> 0.578326 gphoto2-port(2): Freeing port...
> 0.578344 gphoto2-port(2): Closing port...
> Model Port
> ----------------------------------------------------------
> USB PTP Class Camera usb:
> 0.579846 gp-camera(2): Freeing camera...
> 0.579879 gphoto2-port(2): Freeing port...
> 0.579900 gphoto2-filesystem(2): resetting filesystem
> 0.579911 libgphoto2/gphoto2-filesys.c(2): Clearing fscache LRU list...
> 0.579922 libgphoto2/gphoto2-filesys.c(2): fscache LRU list already empty
> 0.579932 gphoto2-filesystem(2): Internally deleting all folders from '/'...
> 0.579946 gphoto2-filesystem(2): Lookup folder '/'...
> 0.579957 gphoto2-filesystem(2): Found! / is 0x2060440
> 0.579968 gphoto2-filesystem(2): Recurse delete folder 0x2060440
>
> Any idea whats going wrong?

This looks totally fine, just that it is detected as generic PTP camera.

Does "gphoto2 -L" work?

Ciao, Marcus

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

D300s

2009-12-12T11:26:21Z

Hello,

I recently got a D300s and tried to connect it under Kubuntu 9.10.
digiKam (which uses libgphoto) is unable to connect. I tried with gtkam,
digikam, command line and had no success. In command line i tried:
gphoto2 --auto-detect --debug
Here is the output:
0.000418 main(2): ALWAYS INCLUDE THE FOLLOWING LINES WHEN SENDING DEBUG
MESSAGES TO THE MAILING LIST:

0.000495 main(2): gphoto2 2.4.5

0.000512 main(2): gphoto2 has been compiled with the following options:

0.000523 main(2): + gcc (C compiler used)

0.000534 main(2): + popt (mandatory, for handling command-line
parameters)

0.000544 main(2): + exif (for displaying EXIF information)

0.000554 main(2): + cdk (for accessing configuration options)

0.000565 main(2): + aa (for displaying live previews)

0.000575 main(2): + jpeg (for displaying live previews in JPEG format)

0.000585 main(2): + readline (for easy navigation in the shell)

0.000600 main(2): libgphoto2 2.4.6

0.000618 main(2): libgphoto2 has been compiled with the following
options:

0.000628 main(2): + gcc (C compiler used)

0.000641 main(2): + ltdl (for portable loading of camlibs)

0.000651 main(2): + EXIF (for special handling of EXIF files)

0.000664 main(2): libgphoto2_port 0.8.0

0.000677 main(2): libgphoto2_port has been compiled with the following
options:

0.000688 main(2): + gcc (C compiler used)

0.000698 main(2): + ltdl (for portable loading of camlibs)

0.000708 main(2): + USB (libusb, for USB cameras)

0.000718 main(2): + serial (for serial cameras)

0.000728 main(2): + no resmgr (serial port access and locking)

0.000738 main(2): + no baudboy (serial port locking)

0.000748 main(2): + no ttylock (serial port locking)

0.000758 main(2): + no lockdev (serial port locking)

0.000769 main(2): CAMLIBS env var not set, using compile-time default
instead

0.000779 main(2): IOLIBS env var not set, using compile-time default
instead

0.000821 setting/gphoto2-setting.c(2): Creating $HOME/.gphoto

0.000928 setting/gphoto2-setting.c(2): Loading settings from file
"/home/andi/.gphoto/settings"

0.001231 gphoto2-port-info-list(2): Using ltdl to load io-drivers from
'/usr/lib/libgphoto2_port/0.8.0'...

0.001417 gphoto2-port-info-list(2): Called for filename
'/usr/lib/libgphoto2_port/0.8.0/disk'.

<snip>

0.010597 gphoto2-port-info-list(2): Could not load port driver list:
'Unspecified error'.

0.010618 gphoto2-port-info-list(2): Called for filename
'/usr/lib/libgphoto2_port/0.8.0/ptpip'.

0.011039 gphoto2-port-info-list(2): Loaded 'PTP/IP Connection'
('ptpip:') from '/usr/lib/libgphoto2_port/0.8.0/ptpip'.

0.011067 gphoto2-port-info-list(2): Loaded '' ('^ptpip') from
'/usr/lib/libgphoto2_port/0.8.0/ptpip'.

0.011084 gphoto2-port-info-list(2): Called for filename
'/usr/lib/libgphoto2_port/0.8.0/serial'.

0.011643 gphoto2-port-info-list(2): Loaded 'Serial Port 0'
('serial:/dev/ttyS0') from '/usr/lib/libgphoto2_port/0.8.0/serial'.

0.011666 gphoto2-port-info-list(2): Loaded 'Serial Port 1'
('serial:/dev/ttyS1') from '/usr/lib/libgphoto2_port/0.8.0/serial'.

0.011682 gphoto2-port-info-list(2): Loaded 'Serial Port 2'
('serial:/dev/ttyS2') from '/usr/lib/libgphoto2_port/0.8.0/serial'.

0.011698 gphoto2-port-info-list(2): Loaded 'Serial Port 3'
('serial:/dev/ttyS3') from '/usr/lib/libgphoto2_port/0.8.0/serial'.

0.011714 gphoto2-port-info-list(2): Loaded '' ('^serial') from
'/usr/lib/libgphoto2_port/0.8.0/serial'.

0.011729 gphoto2-port-info-list(2): Called for filename
'/usr/lib/libgphoto2_port/0.8.0/usb'.

0.486913 gphoto2-port-info-list(2): Loaded 'Universal Serial Bus'
('usb:') from '/usr/lib/libgphoto2_port/0.8.0/usb'.

0.486951 gphoto2-port-info-list(2): Loaded '' ('^usb:') from
'/usr/lib/libgphoto2_port/0.8.0/usb'.

0.486988 gphoto2-port-info-list(2): Counting entries (10 available)...

0.487005 gphoto2-port-info-list(2): 6 regular entries available.

0.487019 gphoto2-port-info-list(2): Counting entries (10 available)...

0.487034 gphoto2-port-info-list(2): 6 regular entries available.

<snip>
0.578252 gphoto2-port-usb(1): Looking for USB device (class 0x6,
subclass, 0x1, protocol 0x1)... found.
0.578268 gphoto2-port-usb(2): inep to look for is 81
0.578279 gphoto2-port-usb(1): Detected defaults: config 1, interface 0,
altsetting 0, idVendor ID 04b0, idProduct 0425, inep 81, outep 02, intep 83
0.578297 gphoto2-abilities-list.c(2): Found 'USB PTP Class Camera'
(0x6,0x1,0x1)
0.578326 gphoto2-port(2): Freeing port...
0.578344 gphoto2-port(2): Closing port...
Model Port
----------------------------------------------------------
USB PTP Class Camera usb:
0.579846 gp-camera(2): Freeing camera...
0.579879 gphoto2-port(2): Freeing port...
0.579900 gphoto2-filesystem(2): resetting filesystem
0.579911 libgphoto2/gphoto2-filesys.c(2): Clearing fscache LRU list...
0.579922 libgphoto2/gphoto2-filesys.c(2): fscache LRU list already empty
0.579932 gphoto2-filesystem(2): Internally deleting all folders from '/'...
0.579946 gphoto2-filesystem(2): Lookup folder '/'...
0.579957 gphoto2-filesystem(2): Found! / is 0x2060440
0.579968 gphoto2-filesystem(2): Recurse delete folder 0x2060440

Any idea whats going wrong?

Best regards,
Andi

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

changed behaviour for "camera_wait_for_event"

2009-12-10T06:02:47Z

Hello, Marcus!

I looked into it more attentively. The difference in process between
Nikon D3000 and Nikon D80.

For D3000 in the shell:

gphoto2:> cd store_00010001/DCIM/100D3000
Remote directory now '/store_00010001/DCIM/100D3000'.
gphoto2:> ls
DSC_0001.JPG DSC_0002.JPG DSC_0003.JPG DSC_0004.JPG
DSC_0005.JPG DSC_0006.JPG DSC_0007.JPG
gphoto2:> wait-event

Here no output. Because it's timeout. After I see prompt, i press
release button on camera three times. And then

gphoto2:> wait-event
FILEADDED DSC_0008.JPG /store_00010001/DCIM/100D3000
gphoto2:> wait-event
UNKNOWN PTP Event 400c, Param1 00010001
gphoto2:> wait-event
FILEADDED DSC_0009.JPG /store_00010001/DCIM/100D3000
gphoto2:> wait-event
UNKNOWN PTP Event 400c, Param1 00010001
gphoto2:> wait-event
FILEADDED DSC_0010.JPG /store_00010001/DCIM/100D3000
gphoto2:> wait-event
UNKNOWN PTP Event 400c, Param1 00010001
gphoto2:> wait-event

Again, no output. Timeout. It's totally ok.

gphoto2:> ls
DSC_0001.JPG DSC_0002.JPG DSC_0003.JPG DSC_0004.JPG
DSC_0005.JPG DSC_0006.JPG DSC_0007.JPG DSC_0008.JPG
DSC_0009.JPG DSC_0010.JPG
gphoto2:> capture-image
New file is in location /store_00010001/DCIM/100D3000/DSC_0011.JPG on the camera
gphoto2:> wait-event
gphoto2:> ls
DSC_0001.JPG DSC_0002.JPG DSC_0003.JPG DSC_0004.JPG
DSC_0005.JPG DSC_0006.JPG DSC_0007.JPG DSC_0008.JPG
DSC_0009.JPG DSC_0010.JPG DSC_0011.JPG
gphoto2:> q

Hurray! Everything is ok!
This is considered a correct behaviour. Now with D80 in the shell:

gphoto2:> cd store_00010001/DCIM/100NCD80
Remote directory now '/store_00010001/DCIM/100NCD80'.
gphoto2:> ls
DSC_0001.JPG DSC_0002.JPG DSC_0003.JPG DSC_0004.JPG
DSC_0005.JPG DSC_0006.JPG DSC_0007.JPG DSC_0008.JPG
DSC_0009.JPG DSC_0010.JPG
gphoto2:> wait-event

No output. Timeout. Ok. Press button three times

gphoto2:> wait-event
FILEADDED DSC_0011.JPG /store_00010001/DCIM/100NCD80
gphoto2:> wait-event
gphoto2:> wait-event

Two timeouts! What happened?

gphoto2:> ls
DSC_0001.JPG DSC_0002.JPG DSC_0003.JPG DSC_0004.JPG
DSC_0005.JPG DSC_0006.JPG DSC_0007.JPG DSC_0008.JPG
DSC_0009.JPG DSC_0010.JPG DSC_0011.JPG
gphoto2:> capture-image
New file is in location /store_00010001/DCIM/100NCD80/DSC_0014.JPG on the camera
gphoto2:> wait-event

*** Error ***
Could not append 'DSC_0014.JPG' to folder
'/store_00010001/DCIM/100NCD80' because this file already exists.
*** Error (-103: 'File exists') ***
gphoto2:> ls
DSC_0001.JPG DSC_0002.JPG DSC_0003.JPG DSC_0004.JPG
DSC_0005.JPG DSC_0006.JPG DSC_0007.JPG DSC_0008.JPG
DSC_0009.JPG DSC_0010.JPG DSC_0011.JPG DSC_0014.JPG
gphoto2:> q

I have to quit to reset filesystem. Now entering again:

gphoto2:> cd store_00010001/DCIM/100NCD80
Remote directory now '/store_00010001/DCIM/100NCD80'.
gphoto2:> ls
DSC_0001.JPG DSC_0002.JPG DSC_0003.JPG DSC_0004.JPG
DSC_0005.JPG DSC_0006.JPG DSC_0007.JPG DSC_0008.JPG
DSC_0009.JPG DSC_0010.JPG DSC_0011.JPG DSC_0012.JPG
DSC_0013.JPG DSC_0014.JPG
gphoto2:> q

Now all files are in place but it costed me. :)
The problem is, that i had the same correct behaviour with 2.4.2 and
D80 as I have now with 2.4.7 and D3000. I'm not afraid of UNKNOWN
events so that is the best I can get.

How this applies to my rubygem (gphoto4ruby). The problem is: when
compiled against different versions of libgphoto it behaves
differently with the same camera (D80). And behaviour for newer
version of library is incorrect (unusable).

I saw there was a great change made to
camlibs/ptp2/library.c/camera_wait_for_event function (which is used
in this case I guess) since 2.4.2. But the question is, can this
changes be done without breaking behaviour for older cameras?

Here attached non edited scripts from above for D80 and D3000 with
libgphoto2 2.4.7

Sincerely,
Sergey Kruk
================================================
On Thu, Dec 10, 2009 at 12:18 PM, Marcus Meissner <marcus@...> wrote:

gphoto2: {gphoto2: {...folder} /> } /> cd store_00010001/DCIM/100NCD80
Remote directory now '/store_00010001/DCIM/100NCD80'.
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100NCD80> } /store_00010001/DCIM/100NCD80> ls
DSC_0001.JPG DSC_0002.JPG DSC_0003.JPG DSC_0004.JPG
DSC_0005.JPG DSC_0006.JPG DSC_0007.JPG DSC_0008.JPG
DSC_0009.JPG DSC_0010.JPG
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100NCD80> } /store_00010001/DCIM/100NCD80> wait-event
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100NCD80> } /store_00010001/DCIM/100NCD80> wait-event # press release buttom 3 times
FILEADDED DSC_0011.JPG /store_00010001/DCIM/100NCD80
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100NCD80> } /store_00010001/DCIM/100NCD80> wait-event
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100NCD80> } /store_00010001/DCIM/100NCD80> wait-event
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100NCD80> } /store_00010001/DCIM/100NCD80> ls
DSC_0001.JPG DSC_0002.JPG DSC_0003.JPG DSC_0004.JPG
DSC_0005.JPG DSC_0006.JPG DSC_0007.JPG DSC_0008.JPG
DSC_0009.JPG DSC_0010.JPG DSC_0011.JPG
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100NCD80> } /store_00010001/DCIM/100NCD80> capture-image
New file is in location /store_00010001/DCIM/100NCD80/DSC_0014.JPG on the camera
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100NCD80> } /store_00010001/DCIM/100NCD80> wait-event

*** Error ***
Could not append 'DSC_0014.JPG' to folder '/store_00010001/DCIM/100NCD80' because this file already exists.
*** Error (-103: 'File exists') ***
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100NCD80> } /store_00010001/DCIM/100NCD80> ls
DSC_0001.JPG DSC_0002.JPG DSC_0003.JPG DSC_0004.JPG
DSC_0005.JPG DSC_0006.JPG DSC_0007.JPG DSC_0008.JPG
DSC_0009.JPG DSC_0010.JPG DSC_0011.JPG DSC_0014.JPG
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100NCD80> } /store_00010001/DCIM/100NCD80> q

gphoto2: {gphoto2: {...folder} /> } /> cd store_00010001/DCIM/100NCD80
Remote directory now '/store_00010001/DCIM/100NCD80'.
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100NCD80> } /store_00010001/DCIM/100NCD80> ls
DSC_0001.JPG DSC_0002.JPG DSC_0003.JPG DSC_0004.JPG
DSC_0005.JPG DSC_0006.JPG DSC_0007.JPG DSC_0008.JPG
DSC_0009.JPG DSC_0010.JPG DSC_0011.JPG DSC_0012.JPG
DSC_0013.JPG DSC_0014.JPG
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100NCD80> } /store_00010001/DCIM/100NCD80> q

gphoto2: {gphoto2: {...folder} /> } /> cd store_00010001/DCIM/100D3000
Remote directory now '/store_00010001/DCIM/100D3000'.
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100D3000> } /store_00010001/DCIM/100D3000> ls
DSC_0001.JPG DSC_0002.JPG DSC_0003.JPG DSC_0004.JPG
DSC_0005.JPG DSC_0006.JPG DSC_0007.JPG
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100D3000> } /store_00010001/DCIM/100D3000> wait-event
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100D3000> } /store_00010001/DCIM/100D3000> wait-event
FILEADDED DSC_0008.JPG /store_00010001/DCIM/100D3000
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100D3000> } /store_00010001/DCIM/100D3000> wait-event
UNKNOWN PTP Event 400c, Param1 00010001
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100D3000> } /store_00010001/DCIM/100D3000> wait-event
FILEADDED DSC_0009.JPG /store_00010001/DCIM/100D3000
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100D3000> } /store_00010001/DCIM/100D3000> wait-event
UNKNOWN PTP Event 400c, Param1 00010001
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100D3000> } /store_00010001/DCIM/100D3000> wait-event
FILEADDED DSC_0010.JPG /store_00010001/DCIM/100D3000
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100D3000> } /store_00010001/DCIM/100D3000> wait-event
UNKNOWN PTP Event 400c, Param1 00010001
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100D3000> } /store_00010001/DCIM/100D3000> wait-event
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100D3000> } /store_00010001/DCIM/100D3000> ls
DSC_0001.JPG DSC_0002.JPG DSC_0003.JPG DSC_0004.JPG
DSC_0005.JPG DSC_0006.JPG DSC_0007.JPG DSC_0008.JPG
DSC_0009.JPG DSC_0010.JPG
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100D3000> } /store_00010001/DCIM/100D3000> capture-image
New file is in location /store_00010001/DCIM/100D3000/DSC_0011.JPG on the camera
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100D3000> } /store_00010001/DCIM/100D3000> wait-event
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100D3000> } /store_00010001/DCIM/100D3000> ls
DSC_0001.JPG DSC_0002.JPG DSC_0003.JPG DSC_0004.JPG
DSC_0005.JPG DSC_0006.JPG DSC_0007.JPG DSC_0008.JPG
DSC_0009.JPG DSC_0010.JPG DSC_0011.JPG
gphoto2: {gphoto2: {...folder} /store_00010001/DCIM/100D3000> } /store_00010001/DCIM/100D3000> q

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev

_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: changed behaviour for "camera_wait_for_event"

2009-12-10T03:59:56Z

On Thu, Dec 10, 2009 at 10:18:02AM +0100, Marcus Meissner wrote:
> Or if you want to download FILEADDED files immediately, do
> gphoto2 --wait-event-and-download 100s

Hi Marcus,

I've beein interested in tethered capturing for a while, but didn't know
if gpoto and/or my camera would be able to do it.

Anyway, now that you mentioned how to do it, that removed one hurdle,
so I got and compiled 2.4.7 and tried it.

On my D80, it seems to wait for the second image to be taken before
starting to download images. It then downloads two images, and then
waits for two more. This is more or less what happens if I take a shot
every 5 seconds. If I press the shutter less regularly, it sometimes
waits longer and downloads more images at once....

- Is this a bug in the D80 that gphoto2 cannot do anything about?
- I seem to rember you have access to a D80 and/or D90, do you want
me to send debug logs?

Roger.

--
** R.E.Wolff@... ** 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

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: changed behaviour for "camera_wait_for_event"

2009-12-10T01:18:02Z

On Mon, Dec 07, 2009 at 08:39:39PM +0300, Sergey Kruk wrote:

> I use libgphoto2 to manage Nikon D80, D90 and D3000 cameras. Recently
> I tried to move my project from libgphoto2-2.4.2 to 2.4.6 or 2.4.7 and
> I noticed behaviour change, that was not mentioned in changelogs.
> Since everything happens to one camera instace inside C program this
> is better demostrated inside gphoto2 --shell (this cannot be seen in
> command line version, only inside shell):
>
> 1. In 2.4.7 when I run inside shell "capture-image" followed by
> "wait-event", the second one reports that a file was added -- the
> captured one. And sometimes it gives error saying that file already
> exists. That is not the case with 2.4.2, where capture command
> followed by wait command could only give timeout.

capture-image already reads until it gets 1 object added event
itself.

Only if you are shooting NEF+JPEG dual mode, wait-event should
return new images.

That it returned the image that capture-image already reported
would have been a bug in 2.4.2.

> 2. In 2.4.2 I could manually press camera's release button several
> times while in the shell, and than run same number of times
> "wait-event". Each time I would get next file name in FILEADDED event.
> Now with 2.4.7 after i press camera's release button several times I
> only get one "FILEADDED" event followed by timeouts. And files list is
> never updated until I do somethig like "capture-image"

If you are the gphoto2 shell prompt, gphoto is not polling the
interrupt queue... So interrupts might get lost.

The reliable way is to do:
gphoto2 --wait-event 100s # 100 seconds

(just 100 without s would be 100 events)

and then do the shutter pressing actions.

Or if you want to download FILEADDED files immediately, do
gphoto2 --wait-event-and-download 100s

> While first case is arguably a bug, the second one in my opinion clearly is.
> Is "wait"-functionality supported or is it more of experimental
> feature aside from main functionality? Should it be reported?

Well, you have reported it by your mail. :)

It is functionality that is developing, so it might have flaws. But for above
purposes it should work, with the corner condition that wait-event runs for
polling.

Ciao, Marcus

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: PTP Camera Forensics: Unallocated Clusters

2009-12-10T00:58:11Z

On Thu, Dec 10, 2009 at 09:50:30AM +0100, Marcus Meissner wrote:
> On Thu, Dec 10, 2009 at 12:41:44AM -0800, Bridgey wrote:
> > I'm very familiar with dd-ing memory cards but I was just wondering
> > if any options were open to the actual internal memory of the camera
> > (as opposed to any memory cards). I'm assuming if the camera only
> > uses PTP/MTP (i.e. doesn't provide a "disk" mode) then it would be
> > impossible unless one resorted to physically removing the chip from
> > the camera!

> > Oh well.
>
> No, its not possible.

> (There are special vendor commands for some cameras, but I know most
> of them and they can never access raw memory.)

If a camera vendor was implementing their firmware for the first time,
they would have bugs relating to storing the files and directories on
the storage media. To debug those, making an image is useful. So if
they did not start from something that already worked perfectly in
that respect, I would suspect that they had such code in the firmware.

However, deeply hidden, and undocumented, so difficult to find.

Roger.

--
** R.E.Wolff@... ** 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

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: PTP Camera Forensics: Unallocated Clusters

2009-12-10T00:50:30Z

On Thu, Dec 10, 2009 at 12:41:44AM -0800, Bridgey wrote:
> Thanks very much for the speedy reply Marcus.
>
> I'm very familiar with dd-ing memory cards but I was just wondering if any options were open to the actual internal memory of the camera (as opposed to any memory cards). I'm assuming if the camera only uses PTP/MTP (i.e. doesn't provide a "disk" mode) then it would be impossible unless one resorted to physically removing the chip from the camera!
>
> Oh well.

No, its not possible.

(There are special vendor commands for some cameras, but I know most of them
and they can never access raw memory.)

Ciao, Marcus

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: PTP Camera Forensics: Unallocated Clusters

2009-12-10T00:41:44Z

Thanks very much for the speedy reply Marcus.

I'm very familiar with dd-ing memory cards but I was just wondering if any options were open to the actual internal memory of the camera (as opposed to any memory cards). I'm assuming if the camera only uses PTP/MTP (i.e. doesn't provide a "disk" mode) then it would be impossible unless one resorted to physically removing the chip from the camera!

Oh well.

Ta, Adam

From: Marcus Meissner <marcus@...>
To: Bridgey <adam.bridge@...>
Cc: gphoto-user@...
Sent: Thu, 10 December, 2009 7:48:17
Subject: Re: [Gphoto-user] PTP Camera Forensics: Unallocated Clusters

On Wed, Dec 09, 2009 at 11:32:47AM -0800, Bridgey wrote:
> All,
>
> I am trying to ascertain whether it's possible to acquire the raw memory of the camera over PTP/MTP. In short I want to acquire the unallocated clusters in order to carve out any images that may have been deleted.

> Is this even possible over the protocol?

It is not possible.

PTP or MTP just gives the directory/file view ... but no RAW view at all.

> I'm happy to roll my sleeves up and get involved in the source code if needs be, but I'm brand new to the whole arena of PTP/MTP so would really appreciate any pointers!
>
> I did try taking advantage of the libptp/ptpcam but ptpcam wouldn't communicate with the FujiFilm S1500 eventhough gphoto2 would.

For deleted images I plug in the Card to a cardreader, dump the whole
card to a file (dd if=/dev/sdX of=card.img or similar) and then run "photorec" on it.

Ciao, Marcus

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev

_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: PTP Camera Forensics: Unallocated Clusters

2009-12-09T23:48:17Z

On Wed, Dec 09, 2009 at 11:32:47AM -0800, Bridgey wrote:
> All,
>
> I am trying to ascertain whether it's possible to acquire the raw memory of the camera over PTP/MTP. In short I want to acquire the unallocated clusters in order to carve out any images that may have been deleted.

> Is this even possible over the protocol?

It is not possible.

PTP or MTP just gives the directory/file view ... but no RAW view at all.

> I'm happy to roll my sleeves up and get involved in the source code if needs be, but I'm brand new to the whole arena of PTP/MTP so would really appreciate any pointers!
>
> I did try taking advantage of the libptp/ptpcam but ptpcam wouldn't communicate with the FujiFilm S1500 eventhough gphoto2 would.

For deleted images I plug in the Card to a cardreader, dump the whole
card to a file (dd if=/dev/sdX of=card.img or similar) and then run "photorec" on it.

Ciao, Marcus

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

PTP Camera Forensics: Unallocated Clusters

2009-12-09T11:32:47Z

All,

I am trying to ascertain whether it's possible to acquire the raw memory of the camera over PTP/MTP. In short I want to acquire the unallocated clusters in order to carve out any images that may have been deleted.

Is this even possible over the protocol? I'm happy to roll my sleeves up and get involved in the source code if needs be, but I'm brand new to the whole arena of PTP/MTP so would really appreciate any pointers!

I did try taking advantage of the libptp/ptpcam but ptpcam wouldn't communicate with the FujiFilm S1500 eventhough gphoto2 would.

Many thanks,

Adam

changed behaviour for "camera_wait_for_event"

2009-12-07T09:39:39Z

I use libgphoto2 to manage Nikon D80, D90 and D3000 cameras. Recently
I tried to move my project from libgphoto2-2.4.2 to 2.4.6 or 2.4.7 and
I noticed behaviour change, that was not mentioned in changelogs.
Since everything happens to one camera instace inside C program this
is better demostrated inside gphoto2 --shell (this cannot be seen in
command line version, only inside shell):

1. In 2.4.7 when I run inside shell "capture-image" followed by
"wait-event", the second one reports that a file was added -- the
captured one. And sometimes it gives error saying that file already
exists. That is not the case with 2.4.2, where capture command
followed by wait command could only give timeout.

2. In 2.4.2 I could manually press camera's release button several
times while in the shell, and than run same number of times
"wait-event". Each time I would get next file name in FILEADDED event.
Now with 2.4.7 after i press camera's release button several times I
only get one "FILEADDED" event followed by timeouts. And files list is
never updated until I do somethig like "capture-image"

While first case is arguably a bug, the second one in my opinion clearly is.
Is "wait"-functionality supported or is it more of experimental
feature aside from main functionality? Should it be reported?

Sincerely,
Sergey Kruk

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Can I stop the camera locking up when connected to USB?

2009-12-03T09:19:58Z

Hello,

I have a Casio Exilim FH20, and I'm trying to make a control rig for
it, so I can take pictures and retrieve them.

It's probably a stupid question but I thought I'd ask: is there any
way to stop the camera controls from locking up when the camera is
connected to a computer via USB? I thought that just maybe there's a
gphoto command that could do this.

If there was, I could capture and download pictures without having to
plug and unplug the USB cable all the time. I plan to be triggering
several cameras, so this would be a big help.

(gphoto seems to connect to the FH20 perfectly well, in both USB and
PTP modes, as far as I can tell.)

Thanks for your time,

Tim

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: Canon 5DM2 and Mirror-Lockup

2009-12-02T08:17:57Z

Hi Marcus,

Mirror Lockup (german: Spiegelverriegelung) is used to reduce
vibrations caused by the shutter. If you're capturing an image with a
long exposure time, you use it to get a few seconds between the actual
release of the shutter and the mirror. In this time, the vibrations
are hopefully gone.

This mode is very important for long exposure photography like astrophotography.

Besides the other mail on the 7D, my 5DM2 does nothing when I release
the shutter via commandline and I switched on the "Mirror lockup" or
"Spiegelverriegelung". (turning back to off, everything works again).

Best,
Andreas

On Wed, Dec 2, 2009 at 4:58 PM, Marcus Meissner <meissner@...> wrote:

> On Wed, Dec 02, 2009 at 04:53:21PM +0100, Andreas Steinel wrote:
>> Hi everybody,
>>
>> I succeded in using (a kind of) Mirror Lockup with the 5DM2 by using
>> the LiveMode. Unfortunately, you're restricted to a max of 1/30
>> exposure time or less.
>>
>> I also saw that mirror lockup is a problem at the 7D. Are there plans
>> to support shooting in mirror lockup mode? Is there anything I can do
>> to help to implement this feature?
>
> What is mirror lockup mode actually?
>
> Live View mode?
>
> Ciao, Marcus
>

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: Canon 5DM2 and Mirror-Lockup

2009-12-02T07:58:19Z

On Wed, Dec 02, 2009 at 04:53:21PM +0100, Andreas Steinel wrote:
> Hi everybody,
>
> I succeded in using (a kind of) Mirror Lockup with the 5DM2 by using
> the LiveMode. Unfortunately, you're restricted to a max of 1/30
> exposure time or less.
>
> I also saw that mirror lockup is a problem at the 7D. Are there plans
> to support shooting in mirror lockup mode? Is there anything I can do
> to help to implement this feature?

What is mirror lockup mode actually?

Live View mode?

Ciao, Marcus

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Canon 5DM2 and Mirror-Lockup

2009-12-02T07:53:21Z

Hi everybody,

I succeded in using (a kind of) Mirror Lockup with the 5DM2 by using
the LiveMode. Unfortunately, you're restricted to a max of 1/30
exposure time or less.

I also saw that mirror lockup is a problem at the 7D. Are there plans
to support shooting in mirror lockup mode? Is there anything I can do
to help to implement this feature?

Best,
Andreas

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: SX110IS

2009-11-30T19:07:14Z

On the SX110IS with download on the best I can get is about 2.5
seconds per image. So it is like 0.4 fames/sec. But for some reason it
seems slower with the download off, which takes about 3.5 seconds per
image.

Cheers

On Mon, Nov 30, 2009 at 5:47 PM, Shunjie Lau <eijnuhs@...> wrote:

> Hi guys, I am comtemplating between a DSLR or the canon SX110IS.
> The frame/sec is something I am looking for.
> With the DSLR, I am hitting about ~0.5 fames/sec...does anyone know
> about the SX110IS with capture and download over usb2 ?
>
> Thank you !
>
> --
> Sincerely,
> Shunjie Lau
>
> ------------------------------------------------------------------------------
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing.
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
> _______________________________________________
> Gphoto-user mailing list
> Gphoto-user@...
> https://lists.sourceforge.net/lists/listinfo/gphoto-user
>

--
Ph.D. Student, Yiding Han
Dept. of Electrical and Computer Engineering,
Utah State University, 4120 Old Main Hill, Logan, UT 84322-4120, USA
E-mail: yiding.h@..., bitcars@...

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

SX110IS

2009-11-30T16:47:28Z

Hi guys, I am comtemplating between a DSLR or the canon SX110IS.
The frame/sec is something I am looking for.
With the DSLR, I am hitting about ~0.5 fames/sec...does anyone know
about the SX110IS with capture and download over usb2 ?

Thank you !

--
Sincerely,
Shunjie Lau

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

canon widescreen image size

2009-11-30T16:00:10Z

Hi there,

I've got a Canon SX110 Powershot working tremendously with gphoto2.

I was reading the manual the other day and discovered this camera has
the ability to take widescreen photos - 3648 x 2048.

Unfortunately though, this image size does not appear to be selectable.

$ gphoto2 --get-config=/main/imgsettings/canonimgsize
Label: Canon Image Size
Type: RADIO
Current: large
Choice: 0 large
Choice: 1 medium 1
Choice: 2 medium 2
Choice: 3 medium 3
Choice: 4 small

I'm using the following packages from Ubuntu 9.10.

$ dpkg -l | grep gphoto2
ii gphoto2 2.4.5-2
The gphoto2 digital camera command-line clie
ii libgphoto2-2 2.4.6-1ubuntu6
gphoto2 digital camera library
ii libgphoto2-port0 2.4.6-1ubuntu6
gphoto2 digital camera port library

Should this image size be selectable??

Regards,

Andrew.

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: scanning + OCR the monkey way ...

2009-11-29T01:45:24Z

On Sun, Nov 29, 2009 at 12:22:51AM +0000, Albretch Mueller wrote:
> Hi Marcus mentioned to me about a video I couldn't get too. Can you
> let me know the URL to it? Now I have time ;-)
> Thank you

I saw that one I think:
http://www.archive.org/details/GabeScanningCenterMovie

Ciao, Marcus

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: scanning + OCR the monkey way ...

2009-11-28T16:22:51Z

Hi Marcus mentioned to me about a video I couldn't get too. Can you
let me know the URL to it? Now I have time ;-)
Thank you

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: scanning + OCR the monkey way ...

2009-11-28T13:41:16Z

On Sat, Nov 28, 2009 at 03:16:32PM +0000, Albretch Mueller wrote:
> ~
> the guys at pgdp.net (Project Gutenberg, Distributed Proofreaders)
> usually destroy books in order to make the scanning + OCR doable in a
> time frame that makes "business" sense (they volunteer their service
> as proofreaders but they must do it in the least possible time and
> with the least amount of technical hassle, so they cut off the books'
> bindings and use commercial batch scanners to do all even and then odd
> pages at once).

Archive.ORG uses gphoto to scan books.... See here:

http://sourceforge.net/mailarchive/forum.php?thread_name=alpine.DEB.2.00.0811131742180.687%40utopia.booyaka.com&forum_name=gphoto-devel

They use some interesting machines (look at the movie intro at archive.org),
two 90 degrees angled glass plates that get lifted down to the book, picture
taken, lifted up again and the human operator pages forward. Repeat.

Ciao, Marcus

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: scanning + OCR the monkey way ...

2009-11-28T10:17:44Z

Hi everyone,

this is relevant to my interests too.

What I did so far was: Using gphotos remote control feature to setup an
A640 and taking pictures in a ~7secs interval. First taking all even and
than all odd pages. Afterwards using a shell script to rename them in an
appropriate way ... and doing quality control, page number checks, etc

To improve my setup, I have to improve the lighting situation. For this
purpose it would be ideal to use LEDs to illuminate the scene when and
only when the shutter is open. I saw, that gphoto offers the feature of
executing a hook script. I seems that there can be only one script called.

It would be nice to be able to let it execute one script when the
capture command is send (ideally, when the shutter is opened, don't know
if gphoto has this information) and another script when the image is
downloaded (just before, ideally immediately when shutter is closed again).

opinions, comments ?

and btw: there is a growing community working on the whole idea:
http://www.diybookscanner.org

Thanks and best regards,
Ingo.

Albretch Mueller schrieb:

> ~
> the guys at pgdp.net (Project Gutenberg, Distributed Proofreaders)
> usually destroy books in order to make the scanning + OCR doable in a
> time frame that makes "business" sense (they volunteer their service
> as proofreaders but they must do it in the least possible time and
> with the least amount of technical hassle, so they cut off the books'
> bindings and use commercial batch scanners to do all even and then odd
> pages at once).
> ~
> The thing is that sometimes you have only one copy you can or should
> not destroy. I am actually against destroying books or anything as
> long as there is a non-invasive/destroying way to do things.
> ~
> There is plenty of software to do the preprocessing and OCR process,
> but the actual physical part of producing the images one after the
> other is the show stopper. What I have in mind is mount a camera on a
> tripod and configuring it with enough resolution to take pictures of
> the pages, which should be saved in some sort of lossless format, but
> I don't know how to drive a camera via its usb ports so that I can
> somehow drive/automate:
> ~
> 1) when or the time intervals at which to take pictures
> ~
> 2) to save the pictures prefixed in a certain way enumerating first
> even and then odd pages ...
> ~
> cameras do enumerate pictures on their own and I guess doing the
> clicking via software shouldn't be a bid deal. There may even be
> cameras with enough resolution for you to be able to get to them
> wirelessly
> ~
> I found for example:
> ~
> comp.os.linux.hardware: "Nokia phone via USB ???"
> ~
> alt.os.linux: USB camera with Linux?
> ~
> which somewhat relates to what I am trying to do. They are able to
> access the internals of the camera to just transfer files not really
> automate its functions
> ~
> I do know google uses huge and expensive machines to scan pages (and
> somehow do some OCR to since they make them searchable)
> ~
> Is it possible? What do you suggest?
> ~
> Thank you
> lbrtchx
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Gphoto-user mailing list
> Gphoto-user@...
> https://lists.sourceforge.net/lists/listinfo/gphoto-user
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: scanning + OCR the monkey way ... 99gphoto

2009-11-28T09:52:16Z

> My plan is to build a platform with uniform lighting where I place the book on the platform , press it flat with glass
~

Thank you very much. I am glad to see there are more of us culturing
these issues!

~

Why do you need to press the pages to be scanned against a glass? If
what is needed is getting the pages flat on the platform, I would go
first (faster I would say) with on side of the pages and then flip the
book and go with the other side. Even though the flipping has to be
repeated, I think it would be faster and safer to the user, as well as
less complicated and damaging to the books
~

> … and press a switch or foot-pedal.

~

hmm! This physical work should and can be automated. What about
emulating this with software either directly through the camera's USB
port or with an extra mechanical device strapped to the digital
camera? Then all you would set is the timing of when the switch goes
off
~
Also it would be better if the user has free(r) hands to operate a
computer with a GUI on which the scanned pages are being shown, etc
~

lbrtchx

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: scanning + OCR the monkey way ... 99gphoto

2009-11-28T08:57:32Z

I am working on such a project for the MacIntosh.
My plan is to build a platform with uniform lighting where I place the
book on the platform , press it flat with glass and press a switch or
foot-pedal.
The pages are captured as an image, the image appears to be visually
proofed. Meanwhile the glass is lifted and the page is flipped.
Then repeat.
The images are captured in a file. Then they can be transferred
anywhere for OCR.

I have a Canon Powershot A80 successfully taking pictures using Icarus
Camera Control. I am talking to the author about adding more
automation features. The same thing can be done via gPhoto. I am now
working on improving the lighting control. I am an electronics
engineer so this is within my capability. I will be glad to help you
as you explore options.

Gus
Denver, CO USA

On Nov 28, 2009, at 8:16 AM, Albretch Mueller wrote:

~
the guys at pgdp.net (Project Gutenberg, Distributed Proofreaders)
usually destroy books in order to make the scanning + OCR doable in a
time frame that makes "business" sense (they volunteer their service
as proofreaders but they must do it in the least possible time and
with the least amount of technical hassle, so they cut off the books'
bindings and use commercial batch scanners to do all even and then odd
pages at once).
~
The thing is that sometimes you have only one copy you can or should
not destroy. I am actually against destroying books or anything as
long as there is a non-invasive/destroying way to do things.
~
There is plenty of software to do the preprocessing and OCR process,
but the actual physical part of producing the images one after the
other is the show stopper. What I have in mind is mount a camera on a
tripod and configuring it with enough resolution to take pictures of
the pages, which should be saved in some sort of lossless format, but
I don't know how to drive a camera via its usb ports so that I can
somehow drive/automate:
~
1) when or the time intervals at which to take pictures
~
2) to save the pictures prefixed in a certain way enumerating first
even and then odd pages ...
~
cameras do enumerate pictures on their own and I guess doing the
clicking via software shouldn't be a bid deal. There may even be
cameras with enough resolution for you to be able to get to them
wirelessly
~
I found for example:
~
comp.os.linux.hardware: "Nokia phone via USB ???"
~
alt.os.linux: USB camera with Linux?
~
which somewhat relates to what I am trying to do. They are able to
access the internals of the camera to just transfer files not really
automate its functions
~
I do know google uses huge and expensive machines to scan pages (and
somehow do some OCR to since they make them searchable)
~
Is it possible? What do you suggest?
~
Thank you
lbrtchx

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day
trial. Simplify your report design, integration and deployment - and
focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

scanning + OCR the monkey way ...

2009-11-28T07:16:32Z

~
the guys at pgdp.net (Project Gutenberg, Distributed Proofreaders)
usually destroy books in order to make the scanning + OCR doable in a
time frame that makes "business" sense (they volunteer their service
as proofreaders but they must do it in the least possible time and
with the least amount of technical hassle, so they cut off the books'
bindings and use commercial batch scanners to do all even and then odd
pages at once).
~
The thing is that sometimes you have only one copy you can or should
not destroy. I am actually against destroying books or anything as
long as there is a non-invasive/destroying way to do things.
~
There is plenty of software to do the preprocessing and OCR process,
but the actual physical part of producing the images one after the
other is the show stopper. What I have in mind is mount a camera on a
tripod and configuring it with enough resolution to take pictures of
the pages, which should be saved in some sort of lossless format, but
I don't know how to drive a camera via its usb ports so that I can
somehow drive/automate:
~
1) when or the time intervals at which to take pictures
~
2) to save the pictures prefixed in a certain way enumerating first
even and then odd pages ...
~
cameras do enumerate pictures on their own and I guess doing the
clicking via software shouldn't be a bid deal. There may even be
cameras with enough resolution for you to be able to get to them
wirelessly
~
I found for example:
~
comp.os.linux.hardware: "Nokia phone via USB ???"
~
alt.os.linux: USB camera with Linux?
~
which somewhat relates to what I am trying to do. They are able to
access the internals of the camera to just transfer files not really
automate its functions
~
I do know google uses huge and expensive machines to scan pages (and
somehow do some OCR to since they make them searchable)
~
Is it possible? What do you suggest?
~
Thank you
lbrtchx

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: Canon EOS 500D

2009-11-26T03:23:29Z

Thank Sergey but I would like to continue trying it.

Marcus, added my debug log on tar.gz :)

regards

2009/11/26 Sergey Kruk <sergey.kruk@...>

> This error is known for other people with 'Canon EOS 500D'?

I have the same issue with Canon EOS 450D on kubuntu 9.10 amd64. This
problem appeared when I upgraded from 9.04.
I didn't find a way to resolve this problem. So I use Nikon :)

Sergey Kruk
==================================================

On Thu, Nov 26, 2009 at 10:19 AM, Alberto <sepu66@...> wrote:
> As we can identify the error and knowledge because it is happening?
> This error is known for other people with 'Canon EOS 500D'?
>
> 2009/11/25 Alberto <sepu66@...>
>>
>> Thank U Marcus! But it not work :(
>> If I set 'capturetarge=1' and later I execute ' gphoto2 --capture-image'
>> the camera remains blocked, after minutes, appears an error on console:
>> ERROR: Could not
>> capture.
>> *** Error (-1: «Error no especificado») ***
>>
>> With ' --debug' activated the next message appears few times:
>>
>> 60.024240 ptp2/ptp_usb_getresp(2): reading response
>> 60.024244 ptp2/ptp_usb_getpacket(2): getting next ptp packet
>> 60.024249 gphoto2-port(2): Reading 512=0x200 bytes from port...
>> 60.024967 gphoto2-port(2): Could only read 12 de 512 byte(s)
>> 60.024979 gphoto2-port(3): Hexdump of 12 = 0xc bytes follows:
>> 0000 0c 00 00 00 03 00 01 20-41 01 00 00 ....... A...
>>
>> Any ideas?
>>
>>
>> 2009/11/25 Marcus Meissner <meissner@...>
>>>
>>> On Wed, Nov 25, 2009 at 03:47:23PM +0100, Alberto wrote:
>>> > Hi!
>>> > I have compiled and installed these versions:
>>> > libgphoto2-2.4.7
>>> > gphoto2-2.4.7
>>> > gphotofs-0.4.0
>>> > on Ubuntu Linux 9.10 Karmic Koala with kernel 2.6.31-15.
>>> > All the functions of Gphoto2 work correctly with my Canon EOS 500D. The
>>> > problem is when use the option '--capture-image', the camera realises
>>> > the
>>> > photography, but the image is not written in the camera and either in
>>> > the
>>> > PC. If use '--capture-image-and-donwload' it works and the image is
>>> > stored
>>> > in the PC, but I need that the image is stored in the camera.
>>> >
>>> > Best regards!!!
>>>
>>> Set the capturetarget to "card".
>>>
>>> gphoto2 --set-config capturetarget=1
>>>
>>> Ciao, Marcus
>>
>>
>>
>> --
>>
>> Sepu ...and Linux for all
>
>
>
> --
>
> Sepu ...and Linux for all
>

> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Gphoto-user mailing list
> Gphoto-user@...
> https://lists.sourceforge.net/lists/listinfo/gphoto-user
>
>

--

Sepu ...and Linux for all

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

my-logfile.txt.tar.gz (73K) Download Attachment

Re: Canon EOS 500D

2009-11-25T23:34:33Z

> This error is known for other people with 'Canon EOS 500D'?

I have the same issue with Canon EOS 450D on kubuntu 9.10 amd64. This
problem appeared when I upgraded from 9.04.
I didn't find a way to resolve this problem. So I use Nikon :)

Sergey Kruk
==================================================
On Thu, Nov 26, 2009 at 10:19 AM, Alberto <sepu66@...> wrote:

> As we can identify the error and knowledge because it is happening?
> This error is known for other people with 'Canon EOS 500D'?
>
> 2009/11/25 Alberto <sepu66@...>
>>
>> Thank U Marcus! But it not work :(
>> If I set 'capturetarge=1' and later I execute ' gphoto2 --capture-image'
>> the camera remains blocked, after minutes, appears an error on console:
>> ERROR: Could not
>> capture.
>> *** Error (-1: «Error no especificado») ***
>>
>> With ' --debug' activated the next message appears few times:
>>
>> 60.024240 ptp2/ptp_usb_getresp(2): reading response
>> 60.024244 ptp2/ptp_usb_getpacket(2): getting next ptp packet
>> 60.024249 gphoto2-port(2): Reading 512=0x200 bytes from port...
>> 60.024967 gphoto2-port(2): Could only read 12 de 512 byte(s)
>> 60.024979 gphoto2-port(3): Hexdump of 12 = 0xc bytes follows:
>> 0000 0c 00 00 00 03 00 01 20-41 01 00 00 ....... A...
>>
>> Any ideas?
>>
>>
>> 2009/11/25 Marcus Meissner <meissner@...>
>>>
>>> On Wed, Nov 25, 2009 at 03:47:23PM +0100, Alberto wrote:
>>> > Hi!
>>> > I have compiled and installed these versions:
>>> > libgphoto2-2.4.7
>>> > gphoto2-2.4.7
>>> > gphotofs-0.4.0
>>> > on Ubuntu Linux 9.10 Karmic Koala with kernel 2.6.31-15.
>>> > All the functions of Gphoto2 work correctly with my Canon EOS 500D. The
>>> > problem is when use the option '--capture-image', the camera realises
>>> > the
>>> > photography, but the image is not written in the camera and either in
>>> > the
>>> > PC. If use '--capture-image-and-donwload' it works and the image is
>>> > stored
>>> > in the PC, but I need that the image is stored in the camera.
>>> >
>>> > Best regards!!!
>>>
>>> Set the capturetarget to "card".
>>>
>>> gphoto2 --set-config capturetarget=1
>>>
>>> Ciao, Marcus
>>
>>
>>
>> --
>>
>> Sepu ...and Linux for all
>
>
>
> --
>
> Sepu ...and Linux for all
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Gphoto-user mailing list
> Gphoto-user@...
> https://lists.sourceforge.net/lists/listinfo/gphoto-user
>
>

Re: Canon EOS 500D

2009-11-25T23:25:15Z

On Wed, Nov 25, 2009 at 04:11:06PM +0100, Alberto wrote:

> Thank U Marcus! But it not work :(
> If I set 'capturetarge=1' and later I execute ' gphoto2 --capture-image' the
> camera remains blocked, after minutes, appears an error on console:
> ERROR: Could not
> capture.
> *** Error (-1: «Error no especificado») ***
>
> With ' --debug' activated the next message appears few times:
>
> 60.024240 ptp2/ptp_usb_getresp(2): reading response
> 60.024244 ptp2/ptp_usb_getpacket(2): getting next ptp packet
> 60.024249 gphoto2-port(2): Reading 512=0x200 bytes from port...
> 60.024967 gphoto2-port(2): Could only read 12 de 512 byte(s)
> 60.024979 gphoto2-port(3): Hexdump of 12 = 0xc bytes follows:
> 0000 0c 00 00 00 03 00 01 20-41 01 00 00 ....... A...
>
> Any ideas?

Hmm, it does not seem to get the necessary events back :/

Can you mail me the full debug output?

Ciao, Marcus

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gphoto-user mailing list
Gphoto-user@...
https://lists.sourceforge.net/lists/listinfo/gphoto-user

Re: Canon EOS 500D

2009-11-25T23:19:04Z

As we can identify the error and knowledge because it is happening?
This error is known for other people with 'Canon EOS 500D'?

2009/11/25 Alberto <sepu66@...>

Thank U Marcus! But it not work :(
If I set 'capturetarge=1' and later I execute ' gphoto2 --capture-image' the camera remains blocked, after minutes, appears an error on console:
ERROR: Could not capture.
*** Error (-1: «Error no especificado») ***

With ' --debug' activated the next message appears few times:

60.024240 ptp2/ptp_usb_getresp(2): reading response
60.024244 ptp2/ptp_usb_getpacket(2): getting next ptp packet
60.024249 gphoto2-port(2): Reading 512=0x200 bytes from port...
60.024967 gphoto2-port(2): Could only read 12 de 512 byte(s)
60.024979 gphoto2-port(3): Hexdump of 12 = 0xc bytes follows:
0000 0c 00 00 00 03 00 01 20-41 01 00 00 ....... A...

Any ideas?

2009/11/25 Marcus Meissner <meissner@...>

On Wed, Nov 25, 2009 at 03:47:23PM +0100, Alberto wrote:
> Hi!
> I have compiled and installed these versions:
> libgphoto2-2.4.7
> gphoto2-2.4.7
> gphotofs-0.4.0
> on Ubuntu Linux 9.10 Karmic Koala with kernel 2.6.31-15.
> All the functions of Gphoto2 work correctly with my Canon EOS 500D. The
> problem is when use the option '--capture-image', the camera realises the
> photography, but the image is not written in the camera and either in the
> PC. If use '--capture-image-and-donwload' it works and the image is stored
> in the PC, but I need that the image is stored in the camera.
>
> Best regards!!!

Set the capturetarget to "card".

gphoto2 --set-config capturetarget=1

Ciao, Marcus

--

Sepu ...and Linux for all