Night-time time-lapse

fudgey

You can safely remove that set_focus(subjdist) and the script will work, but you will then absolutely remember to use manual focus and set it as you please (Inf usually). Then again that focus setting didn't work for me at all, I left it there because I hoped it would for some other cameras. Maybe it's not a good idea to call that under half shoot after all...

Your set_focus=subjdist doesn't do anything for the focus, I think. Actually I'm a bit surprised it didn't produce an error as set_focus is a keyword reserved for the function (reyalp you reading this? Did he redefine the builtin function by doing that?).

fbonomi

if you change
set_focus(subjdist)
into
set_focus=subjdist
you are just disabling the line...
more exactly, you are defining a new variable called "setfocus" and assigning to this variable the value of subjdist. This variable will never be read and therefore the line becomes useless.

that could be fine, but as I told you check that shots taken in very dark conditions are focused.

careyer

Hi folks,

I' was eager to test the sunsetF15 script on my IXUS70 but it turns out that it does not work. I get a pretty much overexposed picture right from the first picture and it does not change at all for the upcomming pictures. As far as I remember

The shutter speed of the first pictures is:
1", 0"6, 0"4, 1/4, 1/5, 1/6, 1/10, 1/13, 1/15, 1/20, 1/25 @ ISO 100 at normal daylight.

The shutter speed does not get any faster than 1/25 for some reason and I guess the script should not start at 1" at daylight
conditions.

Could the author of the script please help/contact me to solve that problem?

BTW my camera settings before starting the script are:
- focus: infinity
- WB: sunlight
- flash : off
- review time : off
- ISO : 100

Thank you!
careyer (tomyb@gmx.net)

fbonomi

careyer. which version of the script are you using?

fudgey

careyer
I' was eager to test the sunsetF15 script on my IXUS70 but it turns out that it does not work. I get a pretty much overexposed picture right from the first picture and it does not change at all for the upcomming pictures. As far as I remember

It's possible that the script only works in M mode as I probably wrote in the docs. By M mode I mean an M mode that offers user defined Av and Tv and ISO with no automatic exposure kicking in (at least tx1 calls something totally different 'M'). Not all cameras have a such a mode, if yours is one of them you're out of luck until someone modifies the script to work in other modes as well (if it doesn't in its current form).

In any case I remember that the starting Tv is the current manual mode Tv setting, which obviously will not be anything sane if you are not in M mode, but if you set a proper exposure manually before starting the script, it will be very close to the script's decision and there will be little or no bad frames in the start.

fbonomi

mmhhh yes, very well pointed out.

I am working with an Ixus80, and its M mode is by no means a Manual mode as you usually would understand. It just enabled a bunch of other features in the camera's menu.

Id does not certainly allow to set Tv AND Av, as the Ixus80 has no Iris 🙁

fudgey

Without looking at the script, I'd try in Tv mode, manual ISO and CHDK ND filter override (off). Of course you need to have that Tv mode to try it.

darwin-t

Do you have any problem with dew on the camera?

fudgey

darwin-t
Do you have any problem with dew on the camera?

For me not so far. The camera heats up during use which probably helps keep it dry. The only precaution I've taken is that I don't take the camera indoors from freezing cold winter without first turning it off and removing batteries.

PhyrePhoX

you should wrap the camera airproof into some kind of plastic wrap/bag when you take it in from outside (and its freezing outside). then let the camera adjust its temperature for several hours inside that bag. this should help.

chuckheron

This is great stuff!
I can't wait to try it tonight!

I've been doing sunsets for the last couple of weeks (just a basic shooter, without stretching the exposure limits)
I tried the Sunset4.bas script last night that was posted to the wiki, and then started digging in the forums today.. I'm going to run sunsetF16 as soon as I get a chance..

I noticed that it loaded a data table at one point during initialization, (A/CHDK/DATA/sunsetF16.tbl)
does this have important stuff in it, or will it do ok without?

On the other side of the exposure coin,
I was wondering how hard it would be to push into the high speed shutter settings
when the sun is actually directly visible to the camera (as it's moving down toward
the horizon)

I've seen a couple high speed shots of the direct sun that made it a nice orange disc.
On a clear day, watching the sun go down without it being heavily over exposed and
then transitioning into a nighttime sky would be particularly nice!

You guys have done some great work!
All of the Lua libraries are very well coded, I need to dig into them further,
and maybe I can make a contribution...

Thanks!
-chuck

shaltzman

hello everybody, timelapser!
i'll try to be clear with my poor english level, and my "unknowledge" of informatic languages. For time lapse and photo it's a bit better.
I installed CHDK one week ago on my a590is (1.0.0.E), it's running very well (since i use powershots, 2003, i dream about you done guys...thanks a lot!). I try the fantastic set_14 and sunsetF15 (the last builds, i think) during these days, but everytime it crashes, for both scripts, with "press button to close" or nothing at the end of the log file. I read all the posts about that, and don't know now what to do. So i write this post.
All my canon settings was off (focus, flash..), in manual mode...everything seems ok but it crashes at 6 photos or 135...never more that one hour of running the script.
If somebody knows how to solve that problem, and have some time to waste with me, it will be great!
(i have time to try some tests with mys a590is (§particularly for the beginning of the day), so if i can contribute, i'll be enjoy...but i don't know languages...)
thx again for all!!!

shaltzman

Hello
the sunsetF16 works better...
Why can't we use photoshop histogramm to appreciate brightness? What is different with script values? (because on photoshop it's from 0 to 255)
thx

fbonomi

shaltzman
Why can't we use photoshop histogramm to appreciate brightness? What is different with script values? (because on photoshop it's from 0 to 255)

Yes, we could use the 0-255 range instead of the 0-1023 range, it's just a matter of multplying them by 4.

but BEWARE: there is a HUGE difference between the histogram read by the script and the histogramas seen in photoshop, as the script reads the RA image and photoshop sees the conveterted image.

For example, the 0 in photoshop might not correspond to the 0 in the RAW, the 255 in photoshop might not correspond to the 1023 in RAW. Plus, the two are not linearly correlated!!

shaltzman

thx for details of histogram!

Today, another bug happens. The script runs, but the parameters (exposure time and iso) don't change. It is always 1/2000eme sec and ISO 100....pictures are all black...I try to change script parameters, but nothing changes. The script ran very well since weeks. I don't do special modifications since the last use of the script, which was good...I don't know!

there's "deleteuntilmbfree"... :

log:
--- Log opened at 2009/07/08 22:21:45 ---
platform: a590 100e
version: CHDK 0.9.8-776 built on Jun 12 2009 08:53:35
Sunset F1
Parameters (user given in paranthesis)
picsAnHour: 120
max_tv: -420 (10 s)
default_sv: 419 (ISO 100)
max_sv: 707 (ISO 800)
histo_under_start: 0 (0)
histo_under_end: 23 (23)
histo_under_limit: 30
histo_under_weight: 30
histo_over_start: 160 (160)
histo_over_end: 1023 (1023)
histo_over_limit: 4
histo_over_weight: 0
histo_median_value: 16 (80)
histo_median_weight: 50
focus_to_inf: 1
jpg_quality: -1 (no change)
jpg_resolution: -1 (no change)
startupdelay: 0 min

## Time Frame bv night_correct day_correct dusk_factor correct current_tv smoothed_tv shoot_tv shoot_sv Topt Tccd Tbat
disk.deleteUntilMbFree - Mb Min:20Mb Target40disk.deleteUntilMbFree - get free spacedisk.deleteUntilMbFree - Exitutil.sleepUntilNextPeriodOfAnHour - start
util.sleepUntilNextPeriodOfAnHour - end
00 - -287, 273 = smartShoot(newFileName(),2781,419,65535)
Histo Measure: 0 0 0
Correct: 0 0 -2500
Correction: 3125
01 - night_correct:3125
02 - -141=-287-273+419
Measured: -287 273, Calculated: -141
03 - -2922=((-141-2781) * 100 ) / 100
04 - -14610=-14610*5
05 - -140 = -287 - 273+
06 - -140>=96
08 - -140<=96 - 576
10 - 409=((96--140)*1000)/576
11 - -7357=-14610+((3125--14610)*409)/1000
12 - 2634=2634 + (-7357/50)
13 - 2634=2634
14 - 2634=2634
15 - 419=419
16 - 2634<-420
19 - 419 > 707
## 2009/07/08 22:22:04 1 -287 3125 -14610 409 -7357 2634 2634 2634 419 30 37 28
22 - 419
23 - 2634
disk.deleteUntilMbFree - Mb Min:20Mb Target40disk.deleteUntilMbFree - get free spacedisk.deleteUntilMbFree - Exitutil.sleepUntilNextPeriodOfAnHour - start

If there's a known solution for that, it would be perfect... if not, i will format and install again everything...
thx

bugsplatter

fbonomi
current_tv=current_tv + (correct/50)

'Proper' smoothing adds some of the old and the new, so given a smoothing factor 'alpha', you would use: 'value = value * (1 - alpha) + new * alpha' which results in an exponential filter which should approach the final value and not oscillate if 'alpha' factor is correctly chosen. Start with alpha = 0.33 then modify alpha to speed or slow the resulting filtered value.

I've not tried this yet as I have a different scenario I want to try, for timelapse to auto-skip night-time with longer sampling 'til start of new day. Unless I can teach the cam to do startrails by night, dawn/dusk and cloud movie by day 😀

munk_e

I wanted to use a max shutter speed of about 1/10 s, but the script only allows a range of 1 to 65 seconds. This is important for my use, as I'll be using it on a roadtrip for multiple days and if I'm driving, the images cannot have a long exposure to look right. It also has the benefit of preserving the time between each frame.

I changed

[tt]max_tv=sec_to_tv96(check_range(b,1,65))[/tt]

to

[tt]max_tv=b[/tt]

and set b to a Tv96 value that I want

fbonomi

munk_e

I wanted to use a max shutter speed of about 1/10 s, but the script only allows a range of 1 to 65

In this case, why don't you just use a simple intervalometer?

munk_e

fbonomi

munk_e

I wanted to use a max shutter speed of about 1/10 s, but the script only allows a range of 1 to 65

In this case, why don't you just use a simple intervalometer?

I wanted to have exposures through day and night transitions, and with all I've read here I suspected it wouldn't work as day breaks. Your post had me studying a bit more and I see I just needed to learn how to configure the settings correctly for my project. I did a few simple tests with yass v2 and it does indeed get the exposure correct when there's more light after darkness. With so much to learn, I guess I got ahead of myself and didn't see the simpler approach, thanks!

nahuel_89p

Wow wow wow, what is LUA? How do i install this beautyful feature in my Canon 350D?

« Previous Page Next Page »