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

Comparison: CHDKPTP vs Canon's RemoteCapture

  • 129 Replies
  • 42346 Views
*

Offline reyalp

  • ******
  • 14098
Re: Comparison: CHDKPTP vs Canon's RemoteCapture
« Reply #70 on: 27 / August / 2012, 00:58:28 »
Advertisements
... because ... this circumvents the temporary bug you mentioned and it seems to work....

Code: [Select]
function shootat_CHDK_Tv(tv)
   local tv96_i = 96 * -log2(tv)
   local tv96 = string.format('%d',tv96_i)
   printf("set tv96 %s\n",tv96)
   if tv96_i == 0 then
       con:execwait('set_user_tv96('..tv96..')')  -- workaround for CHDK bug
     else
       con:execwait('set_tv96_direct('..tv96..')')
   end
   con:execwait('shoot()')
end

Of course the UI undergoes its predictable behavior for the exceptional case of 1s.
Yes, that should probably work around the problem. Note, as I said earlier, you could also just set the user tv propcase directly, which should allow you to use arbitrary values, and would still update the UI etc.

An alternative is just to send the value 1 instead of 0. This is what I used in the shoot command. The result is when you request a 1 second exposure, you get a 0.992... second exposure instead. The difference is not likely to be detectable...
Don't forget what the H stands for.

*

Offline SticK

  • *****
  • 779
Re: Comparison: CHDKPTP vs Canon's RemoteCapture
« Reply #71 on: 27 / August / 2012, 08:31:56 »
It's curious because I always feel you're ahead of me by three or four (major) posts!  So today is catch-up day // I am downloading the new stuff, rereading all you wrote from the last couple of days, and will be trying your work.  That doesn't guarantee my pea brain won't overload however.

Quote "you could also just set the user tv propcase directly, which should allow you to use arbitrary values"

I will definitely be looking into this.

Quote "An alternative is just to send the value 1 instead of 0 ... The result is when you request a 1 second exposure, you get a 0.992..second exposure instead"

In my case absolute accuracy doesn't matter too much.  The ability of the imaging system to acquire a consistent Tv exposure image-to-image is more important, but it is definitely a nice trick to know.

*

Offline SticK

  • *****
  • 779
Re: Comparison: CHDKPTP vs Canon's RemoteCapture
« Reply #72 on: 27 / August / 2012, 10:04:32 »
Quote "I've uploaded a new build, details here http://chdk.setepontos.com/index.php?topic=6231.msg89893#msg89893"

I am deeply moved by your gracious comment // you did stop me in my tracks I must admit.  You may have some idea of the objectives of this project by now, but you probably don't realize fully yet how far your help may take it.  More later, once I have presented the final comparison.

*

Offline SticK

  • *****
  • 779
Re: Comparison: CHDKPTP vs Canon's RemoteCapture
« Reply #73 on: 27 / August / 2012, 12:28:06 »
QUESTION ... where do I find the code/file/files/exes that implement your new shoot function that supports Tv, Av and ISO ?


*

Offline reyalp

  • ******
  • 14098
Re: Comparison: CHDKPTP vs Canon's RemoteCapture
« Reply #74 on: 27 / August / 2012, 12:37:49 »
QUESTION ... where do I find the code/file/files/exes that implement your new shoot function that supports Tv, Av and ISO ?
The build r291 in the chdkptp downloads area https://www.assembla.com/spaces/chdkptp/documents

The actual code for the shoot command is in cli.lua (the actual command implementation), rlib.lua (camera side component) and exposure.lua (APEX conversions)
Don't forget what the H stands for.

*

Offline SticK

  • *****
  • 779
Re: Comparison: CHDKPTP vs Canon's RemoteCapture
« Reply #75 on: 27 / August / 2012, 14:30:50 »
Improvement tip:  RemoteCapture closes the camera when I press [X] to close the app.  CHDKPTP leaves the camera running on exit, and I've noticed the leftover state is often usable, requiring manual OFF.  My suggestion is to issue [shutdown] on [X] to streamline things and make operation smoother.

*

Offline SticK

  • *****
  • 779
Re: Comparison: CHDKPTP vs Canon's RemoteCapture
« Reply #76 on: 27 / August / 2012, 15:37:02 »
New shoot -- basic test and EXIF. 

The shoot command, so far, appears to work fine for controlling the camera. 

-tv:  Tested were 1/16s to 32s are are performed on the camera and update EXIF correctly. 

-av: Tested were f2.8, f5.6 and f8 were tested and perform OK on the camera and update EXIF correctly. 

-sv: ISO *seems* to do what is expected on the camera by photo assessment, but, EXIF does not get updated properly.  Sometimes the values change, but don't the change to the value I gave.  The strange values in my case (SX110) are 164, 265 and 1600.  There may be more of those.

*

Offline reyalp

  • ******
  • 14098
Re: Comparison: CHDKPTP vs Canon's RemoteCapture
« Reply #77 on: 27 / August / 2012, 15:48:56 »
-sv: ISO *seems* to do what is expected on the camera by photo assessment, but, EXIF does not get updated properly.  Sometimes the values change, but don't the change to the value I gave.  The strange values in my case (SX110) are 164, 265 and 1600.  There may be more of those.
As mentioned in the documentation, ISO is Canon "real" ISO, which is not the same value as displayed on the screen / exif ("market" ISO). See http://chdk.wikia.com/wiki/CHDK_User_Manual#Override_ISO_value

You may now express your undying gratitude to the Canon marketing department ;)

On my a540 I noticed if the ISO isn't a standard value (available in the Canon menu) then it's not displayed in the Canon firmware review info. I haven't looked at the exif.
Don't forget what the H stands for.


*

Offline reyalp

  • ******
  • 14098
Re: Comparison: CHDKPTP vs Canon's RemoteCapture
« Reply #78 on: 27 / August / 2012, 15:55:23 »
Improvement tip:  RemoteCapture closes the camera when I press [X] to close the app.  CHDKPTP leaves the camera running on exit, and I've noticed the leftover state is often usable, requiring manual OFF.
Usable or unusable ?

I have noticed some weirdness if you have switched from playback to record mode. Switching to play before you exit the app may leave things in a better state.

Another thing you might encounter is described here: http://chdk.wikia.com/wiki/Lua/PTP_Scripting#General_information_about_executing_Lua_code_over_PTP
"Lua script execution currently leaves CHDK alt mode in a confused state. You may need to press the alt button a couple times to get the alt menu and buttons to respond as expected."

Quote
  My suggestion is to issue [shutdown] on [X] to streamline things and make operation smoother.
I don't think I'll do this, I frequently restart the app without wanting to restart the camera. A "shutdown on exit" option could be added at some point.
Don't forget what the H stands for.

*

Offline SticK

  • *****
  • 779
Re: Comparison: CHDKPTP vs Canon's RemoteCapture
« Reply #79 on: 27 / August / 2012, 16:02:20 »
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. ??

Yes correct, unusable.

I have not switched modes away from still for several days.  Not a big deal // it's just a convenience and at the very basic level it would perform like RemoteCapture.

 

Related Topics


SimplePortal 2.3.6 © 2008-2014, SimplePortal