CHDK NEWS: Unlimited Tv Exposure Bracketing and MORE - Fin..

http://chdk.wikia.com/wiki/CHDK


See Fingalo's Builds in the Downloads page for link to his homepage.


Build 122 (at the authors download) page now allows for:
(ignore the english errors, it's not his first language)

====begin Fingalo's download page quote====

Zosim now have made video bitrate and compression options in all cams,
and he also added a bracket function in continous drive mode, with 'unlimited'
number of pics!
In menu "Miscellaneous stuff" there is the new menu entry 'TV Bracketing value'.
(When starting this bracket on 15 sec in manual mode, I can get exposure times
longer than 15 seconds ie 15, 8, 30 , 4 sec etc ?!?!)

====end quote====

Did you notice that? You can now get 30 second exposures on cameras internally
limited to 15 seconds.

I'm not fully sure what is meant by bracketing continuously, or if you can get
even 60second or 2 minute exposure out of that, I've not even installed it yet,
but this sure looks promising.

Just for Tv bracketing at normal exposures, this mean you could start out a
1/500 and get as many bracketing stops as you want at 2.4 fps on the faster
cameras. (There goes some of those older, slower, difficult to write/test/debug
bracketing scripts right out the window, now all available by a simple menu
option and high-speed burst mode. ) HDR fans eat your hearts out, or ignore
the envy if you have a CHDK camera!


He also added autostart capability for scripts, and a "get_raw_nr value" uBASIC
command to detect the condition of noise-reduction, on, off, or auto.

When the camera is powered off, it automatically starts up when it first detects
any voltage on the USB port. The "autostart" capability allows you to power up
your camera by using a USB remote cable, and then automatically activate the
last loaded script.

All BY USB-CABLE REMOTE CONTROL.

This feature also allows you to write a script for any favorite camera settings,
even those that aren't stored in Custom mode. When you power-on your camera a
script can automatically set them all from whatever script was last loaded (the
last used script and its settings are retained after power-down). This provides
for an UNLIMITED number of Custom shooting modes on power-up, custom modes that
go far beyond what you can even store in the camera's own Custom mode. (Yes, you
read that right, unlimited.) You could also write a "custom.bas" script that
allows you to change its user variables right in the camera and CHDK's
script-menu, so only one script may have dozens of options in it that you can
change as needed. No need to have separate scripts for dozens (if not hundreds)
of custom options. These user-selectable variable values are retained during
power-down in CHDK's config file.

Example variables you could define in a custom.bas script:

a=zoom position startup 0-129
b=manual focus (0=on 1=off)
c=custom colors red -2 to +2
d=custom contrast -2 to +2
d=stops for 3-shot bracket mode 0 to +4
e=(whatever your little heart desires)

There is a 10 variable limit, a-j, for user-set variables by menu option, but
one variable can change many conditions just by testing for its chosen value.
1's could set flash output, 10's could set EV values, etc. So a variable value
of 58 could be used to set flash output to 5/3rds stops, and 8/3 EV bracket
stops, etc. Are you starting to see the possibilities?

If using this for custom modes, don't forget to use the convenience of the new
"exit_alt" command when it is done making the required changes, then you are
ready to go without having to exit <ALT> mode manually.

(I used the filename of "custom.bas" for example only, you can of course name
your custom-mode scripts anything you want, as many as you want. cust1.bas,
myfavs2.bas, custom_skin.bas, portraits.bas, etc.)


====being Fingalo's download page quote====

Camera settings

Autostart for scriptfiles.
When this setting is 1, Alt mode is entered and the currently active scriptfile
will start running when camera is turned on.
The setting is located in the ****Script**** selection menu.

For my S3is, using remote and autostart the camera will start up (in play mode)
at the first press on the remote.
If the remote script is active, the second press will enter recordmode and take
a picture.
The script must have some command to enter record mode (like shoot or someting
similar)

Remote Enable
1 enabled
0 disabled
Enable/disable the remote function, ( to be able to download files via cable
without turning sdcard write protection off)
The setting is located in the ****Script**** selection menu.

Script functions

a = get_autostart
Function to read if autostart flag is set (it will be set turning on the camera,
if Autostart setting is set to 1.)
0 not active
1 active

set_autostart value
Set the autostart flag (will not change the Autostart setting!)
0 flag is cleared
1 flag is set

a = get_usb_power
Read the status of usb power (remote signal)

exit_alt
Exit the alt mode from script

====end quote====

The "get_usb_power" uBASIC command was implemented due to some requests to find
a way to read the USB port so that 3-5vdc voltage applied to the USB cable could
be read as a data stream, allowing you to send rudimentary morse-codelike
sequences of power to that port. Thus enabling you to trigger different features
on your camera or activating defined subroutines in scripts by these "digitally"
signed events. Since script commands/code-lines cannot be executed faster than
10ms each, think slow-slow-slow serial data. Coupled to the right hardware (or a
well timed morse-code-key finger) this does allow you to perform things like
zoom your lens, or any other of the many dozens of manual camera controls, all
by USB remote control. Provided your script is designed to interpret the voltage
pulses and then execute them properly. Simple tests for duration might suffice
in most instances. Long press = zoom out 10 steps, short press = zoom in 10
steps. 2 short presses = trip shutter, etc.

See Finagol's CHDK2 download page for further info on this next amazing build.

Build #122 now available for these Canon cameras
:
(model / firmware version)

A570 1.00e
A570 1.01a
A610 1.00e
A610 1.00f
A620 1.00f
A630 1.00c
A640 1.00b
A700 1.00b
A710 1.00a
G7 1.00g
G7 1.00i
G7 1.00j
IXUS700 (SD500) 1.01a
IXUS800 (SD700) 1.01b
S2IS 1.00e
S2IS 1.00f
S2IS 1.00g
S3IS 1.00a

Update:

Okay, after testing the new Tv bracketing mode.

I set my camera to Manual mode, ISO80, with a 15" (15-second) exposure, hi-speed
continuous mode. CHDK options of NR-OFF, Tv Braketing Value = 1 EV. The NR off
just so I wouldn't have to put up with an agonizingly amount of noise-reduction
frames being taken between each one too. As it was my finger got tired of
holding the button down. Next time I'll have to just use a script for this.

These are the exposure times I get:

Shot 1 = 15"
Shot 2 = 8"
Shot 3 = 30"
Shot 4 = 4"
Shot 5 = 60" (1 minute)
Shot 6 = 2"
Shot 7 = 60"
Shot 8 = 1"
Shot 9 = 60"
Shot 10 = 1/2"
Shot 11 = 60"
Shot 12 = 1/4"
etc.

It appears that the cameras are limited to a 1 minute exposure maximum. Or at
least mine is.

So, you have to go through a 15" exposure, an 8" exposure, a 30" exposure, a 4"
exposure (~1 minute of shots) before you get to continuous 60" exposures with
little to no delay between them. But hey, when you're doing night photography of
some nebulosity in the night-sky on a tracking-mount, like that matters?
I'll just consider that its "running start" warm-up. I wonder if it tops off at
1/3200" and then quits? I suspect it just keeps repeating a 1/3200", 60"
sequence.

So, for free I just went from a 15" exposure limit in my camera to a 1-minute
limit. Not too shabby.

Then consider the other HDR uses, when starting out at normal exposure rates.

In the Tv Bracketing setting you have the option of Off, 1/3, 2/3, or 1 stop to
choose from too. High-speed continuous mode of 2.4fps with exposure bracketing,
unlimited number of shots, each bracketed shot being one stop-setting further
up, and another stop-setting further down. For free. Doesn't get better than
that for a 177k download. A 5-stop set of 5 images in 2 seconds.

Whoa, cool. I just tested this starting out at 1/500", f/2.7, when it rapidly
(and I do mean rapidly) fired off the bracketing steps it quickly reached
1/3200". Normally you are limited to 1/1600" at f/2.7. You can't use 1/3200"
unless you are at f/8.0 (it's incremental according to shutter speed, as shutter
speed goes above 1/1600" the available aperture gets less and less).

I just found out the images taken at 1/3200" were still being done at f/2.7!
Just like it overrides the shutter speed limit on the low end, it overrides the
f/stop limits on the top end. Sweet!



Including original post below for easy saving in one txt file if needed.



On Thu, 22 Nov 2007 20:13:24 GMT, KevenGaston <none.DeleteThis@anywhere.org> wrote:

>
>
>http://chdk.wikia.com/wiki/CHDK
>
>
>See Fingalo's Builds in the Downloads page for link to his homepage.
>
>
>Build 122 (at the authors download) page now allows for:
>(ignore the english errors, it's not his first language)
>
>====begin Fingalo's download page quote====
>
>Zosim now have made video bitrate and compression options in all cams,
>and he also added a bracket function in continous drive mode, with 'unlimited'
>number of pics!
>In menu "Miscellaneous stuff" there is the new menu entry 'TV Bracketing value'.
>(When starting this bracket on 15 sec in manual mode, I can get exposure times
>longer than 15 seconds ie 15, 8, 30 , 4 sec etc ?!?!)
>
>====end quote====
>
>Did you notice that? You can now get 30 second exposures on cameras internally
>limited to 15 seconds.
>
>I'm not fully sure what is meant by bracketing continuously, or if you can get
>even 60second or 2 minute exposure out of that, I've not even installed it yet,
>but this sure looks promising.
>
>Just for Tv bracketing at normal exposures, this mean you could start out a
>1/500 and get as many bracketing stops as you want at 2.4 fps on the faster
>cameras. (There goes some of those older, slower, difficult to write/test/debug
>bracketing scripts right out the window, now all available by a simple menu
>option and high-speed burst mode. ) HDR fans eat your hearts out, or ignore
>the envy if you have a CHDK camera!
>
>
>He also added autostart capability for scripts, and a "get_raw_nr value" uBASIC
>command to detect the condition of noise-reduction, on, off, or auto.
>
>When the camera is powered off, it automatically starts up when it first detects
>any voltage on the USB port. The "autostart" capability allows you to power up
>your camera by using a USB remote cable, and then automatically activate the
>last loaded script.
>
>All BY USB-CABLE REMOTE CONTROL.
>
>This feature also allows you to write a script for any favorite camera settings,
>even those that aren't stored in Custom mode. When you power-on your camera a
>script can automatically set them all from whatever script was last loaded (the
>last used script and its settings are retained after power-down). This provides
>for an UNLIMITED number of Custom shooting modes on power-up, custom modes that
>go far beyond what you can even store in the camera's own Custom mode. (Yes, you
>read that right, unlimited.) You could also write a "custom.bas" script that
>allows you to change its user variables right in the camera and CHDK's
>script-menu, so only one script may have dozens of options in it that you can
>change as needed. No need to have separate scripts for dozens (if not hundreds)
>of custom options. These user-selectable variable values are retained during
>power-down in CHDK's config file.
>
>Example variables you could define in a custom.bas script:
>
>a=zoom position startup 0-129
>b=manual focus (0=on 1=off)
>c=custom colors red -2 to +2
>d=custom contrast -2 to +2
>d=stops for 3-shot bracket mode 0 to +4
>e=(whatever your little heart desires)
>
>There is a 10 variable limit, a-j, for user-set variables by menu option, but
>one variable can change many conditions just by testing for its chosen value.
>1's could set flash output, 10's could set EV values, etc. So a variable value
>of 58 could be used to set flash output to 5/3rds stops, and 8/3 EV bracket
>stops, etc. Are you starting to see the possibilities?
>
>If using this for custom modes, don't forget to use the convenience of the new
>"exit_alt" command when it is done making the required changes, then you are
>ready to go without having to exit <ALT> mode manually.
>
>(I used the filename of "custom.bas" for example only, you can of course name
>your custom-mode scripts anything you want, as many as you want. cust1.bas,
>myfavs2.bas, custom_skin.bas, portraits.bas, etc.)
>
>
>====being Fingalo's download page quote====
>
>Camera settings
>
>Autostart for scriptfiles.
>When this setting is 1, Alt mode is entered and the currently active scriptfile
>will start running when camera is turned on.
>The setting is located in the ****Script**** selection menu.
>
>For my S3is, using remote and autostart the camera will start up (in play mode)
>at the first press on the remote.
>If the remote script is active, the second press will enter recordmode and take
>a picture.
>The script must have some command to enter record mode (like shoot or someting
>similar)
>
>Remote Enable
>1 enabled
>0 disabled
>Enable/disable the remote function, ( to be able to download files via cable
>without turning sdcard write protection off)
>The setting is located in the ****Script**** selection menu.
>
>Script functions
>
>a = get_autostart
>Function to read if autostart flag is set (it will be set turning on the camera,
>if Autostart setting is set to 1.)
>0 not active
>1 active
>
>set_autostart value
>Set the autostart flag (will not change the Autostart setting!)
>0 flag is cleared
>1 flag is set
>
>a = get_usb_power
>Read the status of usb power (remote signal)
>
>exit_alt
>Exit the alt mode from script
>
>====end quote====
>
>The "get_usb_power" uBASIC command was implemented due to some requests to find
>a way to read the USB port so that 3-5vdc voltage applied to the USB cable could
>be read as a data stream, allowing you to send rudimentary morse-codelike
>sequences of power to that port. Thus enabling you to trigger different features
>on your camera or activating defined subroutines in scripts by these "digitally"
>signed events. Since script commands/code-lines cannot be executed faster than
>10ms each, think slow-slow-slow serial data. Coupled to the right hardware (or a
>well timed morse-code-key finger) this does allow you to perform things like
>zoom your lens, or any other of the many dozens of manual camera controls, all
>by USB remote control. Provided your script is designed to interpret the voltage
>pulses and then execute them properly. Simple tests for duration might suffice
>in most instances. Long press = zoom out 10 steps, short press = zoom in 10
>steps. 2 short presses = trip shutter, etc.
>
>See Finagol's CHDK2 download page for further info on this next amazing build.
>
>Build #122 now available for these Canon cameras
>:
>(model / firmware version)
>
>A570 1.00e
>A570 1.01a
>A610 1.00e
>A610 1.00f
>A620 1.00f
>A630 1.00c
>A640 1.00b
>A700 1.00b
>A710 1.00a
>G7 1.00g
>G7 1.00i
>G7 1.00j
>IXUS700 (SD500) 1.01a
>IXUS800 (SD700) 1.01b
>S2IS 1.00e
>S2IS 1.00f
>S2IS 1.00g
>S3IS 1.00a