Comparison: CHDKPTP vs Canon's RemoteCapture - page 9 - RAW Shooting and Processing - CHDK Forum

Comparison: CHDKPTP vs Canon's RemoteCapture

  • 129 Replies
  • 23300 Views
*

Offline reyalp

  • ******
  • 12690
Re: Comparison: CHDKPTP vs Canon's RemoteCapture
« Reply #80 on: 27 / August / 2012, 16:29:08 »
Advertisements
Therefore ... if ask shoot for -sv=100 if see an EXIF value X.  But if I ask for 200, I still see X.  It appears under some conditions to be struck, for example, I had the value of 164 stuck for I think it was 100, 800 and 800. ??
The effect of CHDK overrides on EXIF values isn't very reliable, and varies between cameras and probably camera settings. To determine whether the override is working, you need to compare the light levels in the the photos, if you take pictures at e.g 100,200,400,800 there should be 1 stop of exposure difference visible in a histogram. Alternately, you could reduce the shutter speed by 1 stop and they should all be exposed about the same (histogram will vary slightly due to increased noise)

Once you've done that, you can examine the exif and determine whether the values are being recorded or not.

In some cases, CHDK overrides do not update the regular EXIF, but do update the Canon "maker note" fields.

You should also know that on many Canon cameras, the last normal ISO value is done in software rather than sensor gain, and CHDK overrides may not turn this on. E.g. on my a540, the factory max ISO is 800, but CHDK ISO override only works to 400. If you examine raws taken at 400 and 800, the pixel values are the same, meaning the "ISO" adjustment is really just cranking up the brightness in the jpeg.

On cameras with a separate "High ISO" or similar mode, this is something different again.
Quote
Yes correct, unusable.
If you can elaborate on how it becomes "unusable" it might be possible to do something about it. Note that the alt mode issue I mentioned can make it appear like the keys have no effect, but to clear this, you just have to press the button until the <alt> indicator appears, and press it again to get to non-alt mode.
Don't forget what the H stands for.

*

Offline SticK

  • *****
  • 779
Re: Comparison: CHDKPTP vs Canon's RemoteCapture
« Reply #81 on: 27 / August / 2012, 16:35:11 »
I like the RAW ON|OFF option.  Something useful too would be DARK SUBTRACT ON|OFF.

You may have a solution for this already, nonetheless, please refer to the figures.  In my case I only set WHITE BALANCE from the RemoteCapture right panel, very occasionally.  Since these are in general not very dynamic properties during typical photographic shooting (the general audience I am guessing), I am thinking of a separate function that could be called something like "set_camera" in the same style as shoot, which would handle the more universal (static) settings, like Marco ON|OFF, AF stuff, (left panel), JPG features, camera tilt (top), and those in the right panel (which includes my pet).  Is something like this doable within reason?

====

Quote "To determine whether the override is working, you need to compare the light levels in the the photos"

Yes I did this and mentioned earlier, the answer is in-camera exposure brightness follows the logical progression.

Quote "Once you've done that, you can examine the exif and determine whether the values are being recorded or not"

I did that too, but the EXIF value recording behavior is inconsistent, even if the values are not what the are supposed to be.

Quote "You should also know that on many Canon cameras, the last normal ISO value is done in software rather than sensor gain, and CHDK overrides may not turn this on."

This is *very good* to know thanks.

But unusable for me, was restarting the cli and getting no response.

*

Offline SticK

  • *****
  • 779
Re: Comparison: CHDKPTP vs Canon's RemoteCapture
« Reply #82 on: 27 / August / 2012, 16:39:36 »
... in other words it seems there are short ranges of ISO values that don't the EXIF ISO variable.

*

Offline reyalp

  • ******
  • 12690
Re: Comparison: CHDKPTP vs Canon's RemoteCapture
« Reply #83 on: 27 / August / 2012, 16:53:05 »
I like the RAW ON|OFF option.  Something useful too would be DARK SUBTRACT ON|OFF.
You can control this with the camera side lua function http://chdk.wikia.com/wiki/CHDK_scripting#set_raw_nr (note, the name is misleading, it isn't actually related to raw)

[/quote]
You may have a solution for this already, nonetheless, please refer to the figures.  In my case I only set WHITE Is something like this doable within reason?
[/quote]
You mentioned a lot of different features, and I don't specifically plan to make a gui or cli command for any of them right now. Some things controlled either by chdk lua functions, propertycases, or simulated key presses. If you are using the live view, you can just set them using the regular on camera interface, using the buttons in chdkptp.
Quote
But unusable for me, was restarting the cli and getting no response.
So you try to reconnect with chdkptp, and you get no response ? no error message or anything ?
Don't forget what the H stands for.


*

Offline SticK

  • *****
  • 779
Re: Comparison: CHDKPTP vs Canon's RemoteCapture
« Reply #84 on: 27 / August / 2012, 18:28:50 »
Quote "So you try to reconnect with chdkptp, and you get no response ? no error message or anything ?"

This is not major as I mentioned ... but  ..   Power ON.  chdkptp.  Connect, live, viewfinder rec.  [X].  chdkptp. Connect, live, viewfinder (should still be live, camera LCD black) rec (no live).  Play (still image).  Rec (now live OK).  shoot.   [X].  chdkptp.  Connect, live, viewfinder (live view OK).   [X].  chdkptp.  Connect, live, viewfinder (live view OK).   shoot.  etc OK.  Can't recreate systematically // perhaps I could have done something else wrong that gave me trouble before // not sure.

Quote "If you are using the live view, you can just set them using the regular on camera interface, using the buttons in chdkptp."

Once the camera is mounted on the instrument I can't touch it.  Many weeks from now anyway // revisit then.  So cli functions like set_raw_nr will be useful.  Eventually White Balance will be needed.  For now, you have opened the door to functionality required to proceed with camera selection testing // that is fabulous.

====

EXIF ISO, is there anything you can do with it?  Getting that info (even if not the Canon values) is very useful to me. 


*

Offline reyalp

  • ******
  • 12690
Re: Comparison: CHDKPTP vs Canon's RemoteCapture
« Reply #85 on: 27 / August / 2012, 21:30:21 »
Once the camera is mounted on the instrument I can't touch it.
I meant the "up/down/left/right/set" etc buttons in the GUI. You can navigate the regular firmware options using those, right ?

Quote
EXIF ISO, is there anything you can do with it?  Getting that info (even if not the Canon values) is very useful to me.
Did you check the maker notes?

Quote
This is not major as I mentioned ... but  ..   Power ON.  chdkptp.  Connect, live, viewfinder rec.  [X].  chdkptp. Connect, live, viewfinder (should still be live, camera LCD black) rec (no live).  Play (still image).  Rec (now live OK).  shoot.   [X].  chdkptp.  Connect, live, viewfinder (live view OK).   [X].  chdkptp.  Connect, live, viewfinder (live view OK).   shoot.  etc OK.
I don't really understand this, but depending on your USB driver and windows configuration, other software can put the camera in some mode where the screen goes black and chdkptp can't access it. It's also possible the camera can go into some kind of sleep mode on it's own, although the CHDK disable LCD off option should block that (and usually sending a simulated keypress will wake it up).
Don't forget what the H stands for.

*

Offline SticK

  • *****
  • 779
Re: Comparison: CHDKPTP vs Canon's RemoteCapture
« Reply #86 on: 27 / August / 2012, 22:23:28 »
Sideshow snag, perhaps you can help  ... I have been using Camera A on the laptop since the installation of CHDKPTP.  Now I moved the CHDK SD card to Camera B.  With no USB, CHDK comes up fine, ie, Camera B works OK untethered.  However, if I plug USB, it comes up in Device Manager as:
   Imaging Devices
     Canon Power Shot
and the Canon download menu comes up instead of windows being silent.  Of course CHDKPTP does not recognize it.

Moving the SD card back to Camera A, all is fine.   In the Device Manager shows:
   libusb-win32 devices
     Canon Power Shot
and CHDKPTP works fu=ine.

It seems as though the installation (libusb??) memorized Camera A??

Help.

*

Offline reyalp

  • ******
  • 12690
Re: Comparison: CHDKPTP vs Canon's RemoteCapture
« Reply #87 on: 27 / August / 2012, 22:30:09 »
You may have to install the inf driver for each actual camera.

I have also had to install it for plugging into different ports, but this does not seem consistent.

edit:
said filter, should have said inf

edit:
I think on cameras that report a serial number, windows recognizes individual cameras. My a540 does not report a serial number, D10 does. I don't know where the cutoff is, possibly digic III or dryos.
« Last Edit: 27 / August / 2012, 22:32:09 by reyalp »
Don't forget what the H stands for.


*

Offline SticK

  • *****
  • 779
Re: Comparison: CHDKPTP vs Canon's RemoteCapture
« Reply #88 on: 27 / August / 2012, 22:55:11 »
Does this mean I have to install/uninstall the libusb driver each time I switch cameras?

*

Offline reyalp

  • ******
  • 12690
Re: Comparison: CHDKPTP vs Canon's RemoteCapture
« Reply #89 on: 27 / August / 2012, 23:08:32 »
Does this mean I have to install/uninstall the libusb driver each time I switch cameras?
You shouldn't need to uninstall it. You may need to install it for new cameras. You definitely need to install it for different models, don't know about different cameras of the same model (may depend on the serial number thing).
Don't forget what the H stands for.

 

Related Topics