You will have a job to burn the shutter, CHDK cameras are not digital SLR's.The shutter is a tiny piece of pivoted,blackened metal shim that is moved a tiny amount by an electromagnet at the end of exposure.
since the camera takes about 2000 photos a day (~700'000 photos a year) it would be best to leave the mechanical shutter open (I read it is normally open..). Does anyone has an idea how to leave it open and use the electronic shutter like in movie mode? rolling shutter is obviously not an issue.
I read the topic of jmac698 (https://chdk.setepontos.com/index.php?topic=12935.0)but was not able to understand how to tell my camera to leave the shutter open.
how to use manual focus via chdkptp? Set MF to infinite would be best because before sunrise the images are not in focus because the AF is to weak in the dark.I tried to set MF on the camera but when I startet the chdkptp command the camera starts to focus again.I read the topic https://chdk.setepontos.com/index.php?topic=14226.0 but couldn't find =set_mf(1) int the USAGE.TXT of chdkptp.
I would like to upgrade since the camera is 14 years old and for landscape I would prefere little more dynamic range and some more MP (maybe 12?) The sky is sometimes washed out.
My first suggestion would be not to worry about it. You could keep an eye on ebay or whatever for cheap spares of the same model.AFAIK, http://escursionisticivatesi.it/webcam/ has been running the same a4000 cameras for quite a few years now (code is here: https://github.com/alesanmanoweb/multilapse-CHDK if you're interested)
Yes, that is mostly a different topic. CHDK doesn't have control over whether the shutter is closed for stills. We can force it closed or open at specific points, but not prevent the firmware from closing. With reverse engineering this could be possible.Some experiments have been done taking pictures outside of the normal shooting process, but it's more of a starting point for reverse engineering than something usable https://chdk.setepontos.com/index.php?topic=12754.30
First, overriding focus is an area of CHDK with a lot of camera specific quirks, so you may need to experiment a bit to get it work. According to the source code, sx100 supports SD override in MF.So if you want to set MF mode and focus at infinity, you could just send something likeCode: [Select]=set_mf(1) set_focus(-1)from the chdkptp command prompt or a -e command line.The shoot commands (shoot, remoteshoot) also have some options to control focus. You can use -sd=<number> to control the focus distance, and -sdmode to what what focus mode to use. However, to use -1 to focus at "infinity" in chdkptp shoot commands, you need to use the latest chdkptp lua code from SVN (https://app.assembla.com/spaces/chdkptp/subversion/source/HEAD/trunk) not from the binary package.With the Lua from the binary package, you can just use a large number, focus isn't very precise on these cams.(some discussion of related issues in this thread https://chdk.setepontos.com/index.php?topic=14225.msg145121#msg145121)
chdkptp -c -e"clock -sync" -e"rs $downloadCamera -av=4.0 -sv=80 -shots=900 -int=12"
-e" -sdmode=MF -sd=100m"
FWIW, you could also get more dynamic range from your current setup by taking several shots and stack or HDR merge them. Of course, clouds and things could move a bit in between, especially if you use raw.
My command line is at the moment:Code: [Select]chdkptp -c -e"clock -sync" -e"rs $downloadCamera -av=4.0 -sv=80 -shots=900 -int=12"so I should try to add Code: [Select]-e" -sdmode=MF -sd=100m"
chdkptp -c -e"clock -sync" -e"rs $downloadCamera -av=4.0 -sv=80 -shots=900 -int=12 -sd=100m -sdmode=MF"
RAW or HDR Merge would be the next step. but I am afraid that this will make my code significantly more complicated.
Maybe a first step would be to shot in dng and convert the dng with https://www.dechifro.org/dcraw/ in 3 different exposed jpgs and merge them to one jpg.I'm still at the beginning but eager to learn and try out new things.
since the camera takes about 2000 photos a day (~700'000 photos a year)
My first suggestion would be not to worry about it. You could keep an eye on ebay or whatever for cheap spares of the same model.
Also the M3 would be OK but this camera hase no native silent shutter mode[/li][/list]
Those are options to the rs command, so it would be likeCode: [Select]chdkptp -c -e"clock -sync" -e"rs $downloadCamera -av=4.0 -sv=80 -shots=900 -int=12 -sd=100m -sdmode=MF"
chdkptp -c -e"clock -sync" -e"rs $downloadCamera -av=4.0 -sv=80 -shots=1 -int=5 -sdmode=AF -sd=1494mm"chdkptp -c -e"rs $downloadCamera -av=4.0 -sv=80 -shots=600 -int=15 -sdmode=MF -sd=1494mm"
Yes, it would be a lot more complicated, you'd need to code the shooting and bracketing yourself, instead of just 900 shots with rs.
FWIW, raw therapee (https://rawtherapee.com/) has a command line interface https://rawpedia.rawtherapee.com/Command-Line_OptionsYou can make a conversion profile in the GUI and then use it from the command line. The profiles are INI format, so you can also change things like exposure compensation quite easily from a script.
I agree…There are completely different problems when the camera is always pointed towards the sun.@lapser has reported here that his G1x can withstand more than 1500000 shots.https://www.youtube.com/user/DrLapser
There is a function for the M3. I just haven't gotten it to work properly so far.https://chdk.setepontos.com/index.php?topic=12754.40
The code is now like this (after a few 100 test shots...):Code: [Select]chdkptp -c -e"clock -sync" -e"rs $downloadCamera -av=4.0 -sv=80 -shots=1 -int=5 -sdmode=AF -sd=1494mm"chdkptp -c -e"rs $downloadCamera -av=4.0 -sv=80 -shots=600 -int=15 -sdmode=MF -sd=1494mm"I'm really not sure about this. I got focus to infinity at about 1493mm-1496mm which is fine.
What was not so funny: sometimes the focus point jumped. it was not consistend. also at Code: [Select]-sdmode=MF the focuspoint doesn't move at all? so in Code: [Select]-sdmode=MF -sd=1494mm the -sd=1494mm part is needed but doesn't change anything?
Since I have to use anydesk to access the PC which controlls the camera, my brother confirmed that the camera still focuses before releasing the shutter. So it seems not to work properly.
Is it possible to control the exposure via CHDKPTP? In the USAGE.TXT there is no command but maybe it is still possible somehow.
chdkptp -c -e"rs $downloadCamera -isomode=80 -shots=600 -int=15 -sdmode=MF -sd=1494mm"
This does not seem right. At wide angle, "infinity" is often quite close, but only 1.5 meters is unusual.
-sdmode=MFshould put the camera in MF mode. After that, the camera should not change focus on it's own (but in practice I think it can change a little after shooting). -sd should set the focus to whatever distance you set.Yes, if the camera does autofocus with -sdmode=MF something isn't right.The "safety MF" setting in the Canon menu could be on.On many cameras, if the display is turned off, the MF setting will be lost.If your connection is good enough to use chdkptp live view, you can test MF:use =set_mf(1) to enable MF mode, and then if you use =set_focus() with different numbers, you should see the focus distance change immediately.If set_mf is just not working on this port, you could try set_aflock (-sdmode=AFL in chdkptp shooting commands) instead.
You can set shutter speed, aperture and ISO individually, but there isn't currently a way to modify the Canon exposure. If you don't set them all, the other values will be set by Canon auto-exposure, but it doesn't know about any values you did override, so the result will not be correct.In fact, looking at your current command it sets Av and Sv so Canon auto exposure will probably be wrong. To get Canon auto exposure to use the right Tv, you should put the camera in Av modeCode: [Select]-e"luar require'capmode'.set('AV')"And set the Canon manual AV settingCode: [Select]-e"luar set_prop(require'propcase'.USER_AV,aperture_to_av96(4000))"Then in your shoot command, you can use just -isomode=80 without any other exposure controlsCode: [Select]chdkptp -c -e"rs $downloadCamera -isomode=80 -shots=600 -int=15 -sdmode=MF -sd=1494mm"There are some other ways approach this:The https://github.com/alesanmanoweb/multilapse-CHDK/blob/master/multilapse.lua script uses an separate script half press to read back the cameras measured exposure. In that case, it just gets the Bv, but you could return the camera Tv, Av and Sv if you wanted.You can also write your own camera side script (or use an existing one, with some glue code) to decide the exposure for each shot. See https://chdk.setepontos.com/index.php?topic=13386.msg136688#msg136688
Yes... that's why it was quite difficult to find this number. Bigger numbers just made the image even more blurry.Obviously the number doesn't represent any real physical distance, but it seems to work.
Yes indeed!! "safety MF" was ON. now it's switched off...I set the camera to =set_mf(1) and I could change the focus point with the command =set_focus().Now the camera display no longer switches off. I will try AFL. It seems to be what I wanted. but at the moment there is nobody to listen to the camera at home
Ok, thanks, very clear. The camera is actually in AV. the camera chooses the Tv, and I set Iso and Av. It does quite a nice job! (only very little "flicker" between the frames of the time-lapse ...)
The longest shutterspeed is 1 sec. I don't know why?
Interesting, it is possible to use -e"luar require'capmode'.set('AV')" in CHDKPTP command line... Is there any documentation with perhaps some explanations and examples?
chdkptp -e"source myfile.chdkptp"
chdkptp -e"exec dofile('myfile.lua')"
Started by RaduP
Started by LukeSkaff
General Help and Assistance on using CHDK stable releases
Started by 7dforlife
Creative Uses of CHDK
Started by nahuel_89p
Completed and Working Scripts
Started by artfolio
Creative Uses of CHDK