Intervalometer with auto shutter time - for day, night, sunrise, sunset... - page 2 - Completed and Working Scripts - CHDK Forum supplierdeeply

Intervalometer with auto shutter time - for day, night, sunrise, sunset...

  • 21 Replies
  • 15801 Views
Advertisements
One question: Is there a way to delay the start or first shot of the script (so I could set up the camera out the night before but set it to wait ~6 hours (just before sunrise) before it starts shooting). I've tried that with other scripts, but without success.
What did you try ?

Presumably a big sleep command at the start of the script would work.

Or if you want to get fancy,  sit in a loop watching the current exposure level and start when it gets light enough.

Do you have an external power supply ? That's a long time for the camera to be turned on draining batteries no matter what you do.
Ported :   A1200    SD940   G10    Powershot N    G16

What did you try ?

Presumably a big sleep command at the start of the script would work.
Or if you want to get fancy,  sit in a loop watching the current exposure level and start when it gets light enough.
I haven't tried coding it myself, I'm pretty wary of messing with the code. I meant I had tried other scripts... like the SunsetF16 script, which is pretty good and it includes a configurable delay, but the delay never worked (no matter what I put it, it would start shooting immediately).

Do you have an external power supply ? That's a long time for the camera to be turned on draining batteries no matter what you do.
Yes! I got an external power supply (A Canon CA-DC10 for my SD870 Camera).
A couple notes here to perhaps help someone else who tries this...
1) If you're going to get a DC adapter, get the official one, the first cheaper Chinese knockoff I bought off ebay was nothing but trouble.
2) If the camera isn't taking pictures and the screen isn't on (I use the headphone in the output jack trick to keep the screen off), the power drain is very small (can last 6+ hours on a good battery).

Now, congrats outslider.

Have done some work with timelapse with DSLR (latest:
) , but I've recently switch my TL gear to a wonderful Powershot G12. It's all need, compact camera, plenty of manual control and sharp and colorful pictures around 10MP RAW files. I've done some well succeed tests with the sunsetf16 script for day/night TL (here's my last try:
) to circumvent the 1 sec limit , but I'm gonna try this script. At first look it seems to me more of practical use.

Will post here the feedback.

Thanks for sharing.

Daniel Santos @ Lisbon, Portugal.

So, I figured out how to add a start-up delay (WOOHOO!). If anyone else is interested, I'm attaching my modified script. It has two new parameters at the beginning for delay (hours) and delay (minutes). And I got the delay to countdown on the screen (in minutes). So far I've only tested it a few times on my SD870, but it seems to work.


So, I figured out how to add a start-up delay (WOOHOO!). If anyone else is interested, I'm attaching my modified script. It has two new parameters at the beginning for delay (hours) and delay (minutes). And I got the delay to countdown on the screen (in minutes). So far I've only tested it a few times on my SD870, but it seems to work.
Good job !   Now you need to figure out the tricky method - start when the sun comes up and the illumination level is acceptable.
Ported :   A1200    SD940   G10    Powershot N    G16

Hello, folks!

I have a new version of the Universal Intervalometer. This version has been written not more than 1 hour ago, so it is really fresh alpha stage - be carefull:D

Changes, changes:

  • rewritten, simplified code - all these drawings are removed now (maybe they'll back)
  • two modes: accurate and fast

With new - fast - mode I got the speed as high as 1 photo for less than 3 sec.

The difference between fast and accurate mode:
  • accurate mode
    half shoot is pressed, camera measures the brightness, shutter button is releassed to apply changes and then full shoot() function runs - this way your photo has good exposure
  • fast mode
    half shoot is pressed, camera measures the brightness, set_tv96_direct is called, but half-press is not released - instead shoot() is called; this way you don't wait for another measurement, but your exposure will be appliet for the next photo.

So - in accurate mode you get each photo with shutter time calculated for current conditions, in fast mode you get shutter time calculated from previous conditions - this is faster but less accurate.

However, since you need fast mode when the delay between photos is small you can assume that the brightness doesn't change too much:)

On my sx130 this script can take 1 photo for less than 3 sec.

And here is the attachment:
« Last Edit: 20 / April / 2013, 17:45:03 by outslider »
if (2*b || !2*b) {
    cout<<question
}

Compile error: poor Yorick

How do I may go about in setting the intervalometer to infinite, rather than a limited shots?

Although there's no such option you can always do one of following:

- set the number of shoots to really big value (I'm pretty sure that 10^6 is more than enough)
- modify the source code:)

Regards!
if (2*b || !2*b) {
    cout<<question
}

Compile error: poor Yorick


Although there's no such option you can always do one of following:

- set the number of shoots to really big value (I'm pretty sure that 10^6 is more than enough)
- modify the source code:)

Regards!
I have changed the value 1000 to 9999 in the script text on the computer, but each time loading it on the camera, it displays the value last set by me on the camera.
This happens despite that I have set "save params" to off.

I have changed the value 1000 to 9999 in the script text (...)

Please, specify, where you have changed this value - in which place in the script?

(...) but each time loading it on the camera, it displays the value last set by me on the camera.
This happens despite that I have set "save params" to off.

That's because the CHDK loads parameters you have previously set on camera. These settings are stored somewhere in CHDK folder (DATA or something - I'm not sure now).

Can't you simply change the value on camera in script menu settings?

You can also change the 157th and 181st lines from this:

Code: (lua) [Select]
until PHOTO_NO>n

to this:

Code: (lua) [Select]
until true

This should cause the script to completely ignore the value set in the menu and do infinite shooting.

Regards:)
if (2*b || !2*b) {
    cout<<question
}

Compile error: poor Yorick

 

Related Topics