Ultimate Intervalometer - a script for shooting over a long duration - v4.9 - page 5 - Completed and Working Scripts - CHDK Forum  

Ultimate Intervalometer - a script for shooting over a long duration - v4.9

  • 651 Replies
  • 188048 Views
*

Offline bwh13

  • *
  • 28
Advertisements
I used the STICK utility to make a bootable disk - terrific utility by the way.

STICK downloads and installs the 1.1.0 (stable) version, so I just deleted all that pasted the 1.2.0 version on the card instead. 

To answer your questions: 1) Neither CHDK nor the script was running, 2) I was using the firm update method (the problem).
Funny the things you never think of when writing a script.  I'll add a note to the wiki docs for the script warning about this.   Although I notice that the lack of a daylight savings time mode (per your earlier question) is already clearly documented there - but then who reads documentation these days anyway?   :o

Quote
I've parsed through the 'Ultimate' script and it looks like it places the camera in 'Playback' mode and it does retract the lens.
Hmmm ...  where do you see this?  The variable "display_mode" determines the resting state and unless you set it to be PlayKey ( i.e. 3) then it won't switch to playback mode and let the lens retract.  Maybe your camera autormatically retracts the lens in shooting mode as well as in playback mode?


STICK downloads and installs the 1.1.0 (stable) version, so I just deleted all that pasted the 1.2.0 version on the card instead.
You can edit STICK's config file to pick which version it will use.
« Last Edit: 20 / July / 2013, 08:55:23 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

can there be code running between shutter releases,
Yes.
Quote
and can the intervals be 200-600ms?
Yes.   But bear in mind that while the interval between the end of one shot and the start of the next shot can be that short,  the actual shot will typically take from one to two seconds to complete.

My camera has an FPS of 13. So that would mean it only takes ~77ms per shot. Why would it take 2 seconds for each to complete? I'm looking for a way to take pictures every 200ms, triggered from a PC (while running other things between the shots). Is there another script that could do that for me?

My camera has an FPS of 13. So that would mean it only takes ~77ms per shot. Why would it take 2 seconds for each to complete?
The specs I found for the ixus70 say it will do 1.7 fps in continous mode.
http://www.canon-europe.com/For_Home/Product_Finder/Cameras/Digital_Camera/IXUS/Digital_IXUS_70/#p-specification11
 http://www.photographyblog.com/reviews_canon_digital_ixus_70_5.php
And that's in "continuous mode" only - so I think that typically means it is not focusing and calculating exposure before every shot.

Quote
I'm looking for a way to take pictures every 200ms, triggered from a PC (while running other things between the shots). Is there another script that could do that for me?
If you are triggering from a PC then you probably want to be working with chdkptp. 
http://chdk.wikia.com/wiki/PTP_Extension#chdkptp
Its fully scriptable but I strongly suspect it will not let you shoot at 5 fps.  Your camera simply cannot go that fast.
« Last Edit: 21 / July / 2013, 16:05:25 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16


My camera has an FPS of 13. So that would mean it only takes ~77ms per shot. Why would it take 2 seconds for each to complete?
The specs I found for the ixus70 say it will do 1.7 fps in continous mode.
http://www.canon-europe.com/For_Home/Product_Finder/Cameras/Digital_Camera/IXUS/Digital_IXUS_70/#p-specification11
 http://www.photographyblog.com/reviews_canon_digital_ixus_70_5.php
And that's in "continuous mode" only - so I think that typically means it is not focusing and calculating exposure before every shot.

Quote
I'm looking for a way to take pictures every 200ms, triggered from a PC (while running other things between the shots). Is there another script that could do that for me?
If you are triggering from a PC then you probably want to be working with chdkptp. 
http://chdk.wikia.com/wiki/PTP_Extension#chdkptp
Its fully scriptable but I strongly suspect it will not let you shoot at 5 fps.  Your camera simply cannot go that fast.

I can get any camera I need to accomplish this task. The Canon PowerShot SX50 HS, for example, has 13 FPS. Would that work to shoot every ~100ms?

*

Offline srsa_4c

  • ******
  • 4451
I can get any camera I need to accomplish this task. The Canon PowerShot SX50 HS, for example, has 13 FPS. Would that work to shoot every ~100ms?
I might be missing something, but I don't see what exactly you're trying to do.
You're talking about high speed shooting, PC triggering, and running 'some code' between the shots. Is that the PC or the camera that should run that additional code? Does that 'high speed' need to be an exact FPS? Do you want to trigger each shot individually, or just trigger once to shoot a bunch of images?
Anyway.
High speed shooting is only possible in continuous mode (if the camera actually supports the required burst speed). If you already have a camera, try what it can do in that high speed mode.
If you need to access the images immediately on the PC, you'll need to use CHDK's PTP support, and a camera for which 'remote capture' is implemented. I don't know how high shooting speed can be reached this way though.

I can get any camera I need to accomplish this task. The Canon PowerShot SX50 HS, for example, has 13 FPS. Would that work to shoot every ~100ms?
I might be missing something, but I don't see what exactly you're trying to do.
You're talking about high speed shooting, PC triggering, and running 'some code' between the shots. Is that the PC or the camera that should run that additional code? Does that 'high speed' need to be an exact FPS? Do you want to trigger each shot individually, or just trigger once to shoot a bunch of images?
Anyway.
High speed shooting is only possible in continuous mode (if the camera actually supports the required burst speed). If you already have a camera, try what it can do in that high speed mode.
If you need to access the images immediately on the PC, you'll need to use CHDK's PTP support, and a camera for which 'remote capture' is implemented. I don't know how high shooting speed can be reached this way though.


So, my end game is to run a script from a computer that takes a picture, sends a serial command to a light, then repeats 5 times. I need to be able to control the when each picture is taken, so each shot has to be triggered individually. I don't need access to the images immediately, but only after each 5 shot set.

I tried PTP, but it takes a couple seconds before I can take another shot.

So, my end game is to run a script from a computer that takes a picture, sends a serial command to a light, then repeats 5 times. I need to be able to control the when each picture is taken, so each shot has to be triggered individually. I don't need access to the images immediately, but only after each 5 shot set.
I tried PTP, but it takes a couple seconds before I can take another shot.
Like I said earlier,  I do not believe you are going to find a P&S camera (at least not a Canon) that will take individually triggered pictures at a rate faster than 1 fps.   And you will be luckly to get that.

The faster frame rates you see are when shooting in continuous mode.  Somebody would have to hack things enough to allow a delay between shots - something we can't do today.  However, some combination of the bracketing in continuous mode and the USB remote sync code might make the project not too hard.

« Last Edit: 22 / July / 2013, 14:52:52 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline bwh13

  • *
  • 28
Waterwingz-
Documentation: of course!  Sometimes the forum is a crutch for doing one's homework.  Duly noted.

Playback mode: it was in the function "switch_mode (m)"  It's line # 188 in my text editor.  It also outputs the same to the log file.  This problem was fixed when I figured out the bootable disk though.

STICK: figured that one out too.  It's actually a dropdown menu in the UI now.  1.2.0 is the "trunk" version - which I did not know at the time.

Great success with the script thus far: still working on the voltage spike from my solar charging circuit board (which shuts the rig down), though.  Will post some links when I get this project sorted out!

Many thanks!

Playback mode: it was in the function "switch_mode (m)"  It's line # 188 in my text editor.  It also outputs the same to the log file. 
That function only gets called if you have selected the "Display Blanking Mode" to be "Playkey"  (and once after each startup).
Ported :   A1200    SD940   G10    Powershot N    G16

 

Related Topics