JoeNeptune
I just read back some and saw the interesting shutter release trigger for scripts. I wonder if using a double click on the half shutter button, so you can have your script ready with other shots possible until script is needed, would be useful?
Please forgive me if its all ready that way or is otherwise uncompatible as i havent been able to check it out yet.
Keep up the great work!
ciao
Akusai
Hi everyone and a big Thanks to to the great work you've done with the 400plus!
I have a question if anyone got an idea what I am doing wrong. I've tried searching the forum and google - but without success (perhaps I was just using the wrong keywords).
I'm trying to use the intervalometer -> which in itself works fine. But one or two weeks ago I wanted the camera to work through the night, making a picuture every 30 seconds from the nightsky.
To save battery power I wanted the display disabled, so I switched it off and then choose Settings > Config-Scripts > LCD Display > off. After that I started the Intervalometer.
To my surprise it took only one picture and then stopped. Only after switching the display on (either by pressing "Display" or "Playback") or pressing the shutter button the camera took another picture.
I tried a little bit to play around - but without success - I couldn't convince the 400D to take more than one picture without doing anything else.
Yesterday I had a little bit more time and downloaded the latest nightly build (20120713-r140😎. I deleted the settings file and the presets file on the CF Card and tried intervalometer again -> worked without a hitch. Until I again used Settings -> Config-Scripts -> LCD Display -> Off.
It seems as soon as the Display is switched off (when switching into the 400plus menu) and the Option "Display - Off" under Scripts is activated, the Intervalometer refuses to take anymore pictures.
Does anyone have an idea if that is expected or what settings I would have to make to keep display off and get the Intervalometer working?
As a sidenote:
"Auto Power off" is "Off" (in the standard Canon menu in the 1st settings tab)
"Config-Scripts -> Disable power-off" is "Yes"
Thanks
eduperez
That looks like a bug to me. Using those options, 400plus should just turn the display off, but we have recently learned that it can also put the camera in a low power mode than pauses all running tasks. I'll have a look at this later, thanks for reporting it.
David Reyes
Hi!!, first...thanks to all of the developers for such a great piece of software!.
I've been using the 400plus hack since april. I had some issues with the latest release 20120415-12.
Intervalometer is not working with 1 sec intervals. Can't making less than 3 sec intervals. I had to rolled out to 20120415-7 release, and 1 sec intervals are working again.
Anyone experience the same issue?
Thanks again!
eduperez
David Reyes
Hi!!, first...thanks to all of the developers for such a great piece of software!.
I've been using the 400plus hack since april. I had some issues with the latest release 20120415-12.
Intervalometer is not working with 1 sec intervals. Can't making less than 3 sec intervals. I had to rolled out to 20120415-7 release, and 1 sec intervals are working again.
Anyone experience the same issue?
Thanks again!
We had stability issues with the intervalometer, and had to add some delays between shots; this probably breaks with shorter intervals. I'll have a look at this later, but will probably be hard to fix.
cyberhun
Great job on chdk for the eos 400d - I just installed it, nice work guys.
The intervalometer script works perfectly but I can't get the handwaving script to fire the shutter.
In the wiki it says:
"This script will fire the camera when the display-off sensor (at the rear of the camera) is triggered"
Does this mean when you push the 'display off/on' button?
I tried that but nothing happened when I covered and uncovered the lens with my hand.
I can tell the script is running because the blue light flashes and it beeped when started.
Any ideas?
eduperez
cyberhun
Great job on chdk for the eos 400d - I just installed it, nice work guys.
The intervalometer script works perfectly but I can't get the handwaving script to fire the shutter.
In the wiki it says:
"This script will fire the camera when the display-off sensor (at the rear of the camera) is triggered"
Does this mean when you push the 'display off/on' button?
I tried that but nothing happened when I covered and uncovered the lens with my hand.
I can tell the script is running because the blue light flashes and it beeped when started.
Any ideas?
No, it is neither the DISP button nor the front lens. Have you noticed the camera automatically switches the display off when you try to look through the viewfinder? That is: there is a sensor at the back of the camera (two red/black circles just below the viewfinder), that detects when there is an object (your face, usually) near the camera. To start the handwaving script, you must place your hand behind the camera, and trigger that sensor.
Hope this helps.
cyberhun
That totally helped.
Thank-you.
😉
eduperez
David Reyes
Hi!!, first...thanks to all of the developers for such a great piece of software!.
I've been using the 400plus hack since april. I had some issues with the latest release 20120415-12.
Intervalometer is not working with 1 sec intervals. Can't making less than 3 sec intervals. I had to rolled out to 20120415-7 release, and 1 sec intervals are working again.
Anyone experience the same issue?
Thanks again!
I just tried to use the intervalometer with 1s intervals, and it is working; what shutter speed where you using?
David Reyes
Hi, edu, thanks for your reply!.
Yes, the intervalometer actually works when you set 1 sec intervals, BUT is not a shot every 1 sec, is more like every 2 or 3 seconds...
I was using a shutther speed of 1/80, and also used 1/600 in others circumstances.
Everything works great with 20120415-7 release, so i keep that version for now.
Cheers!
eduperez
David Reyes
Hi, edu, thanks for your reply!.
Yes, the intervalometer actually works when you set 1 sec intervals, BUT is not a shot every 1 sec, is more like every 2 or 3 seconds...
I was using a shutther speed of 1/80, and also used 1/600 in others circumstances.
Everything works great with 20120415-7 release, so i keep that version for now.
Cheers!
The problem with earlier versions is that sometimes 400plus can fire the shutter too fast, and the camera gets locked or displays an "ERR-99" message. I added some delays, and it seems to be more stable now; but this also means that sometimes the intervalometer may not meet the deadline for a shot, and has to skip forward for the next one. A faster CF card may help, but I cannot guarantee anything...
I'll try to change how those delays work, and see if that improves the situation; but I very much prefer a slow but stable camera than a fast one that fails.
David Reyes
Ok, i understand the stability problem. I had some problems too with my camera locking and get unresponsive because of the buffer filling quickly, so im using Jpgs instead of Raw, im sacrifying some quality but i can use 1 sec intervals.
Thank edu!!
ELB
I'd like to thank all those who have contributed to developing the 400+. She has made some of my shots so much easier or even possible! I have been happily running it for a year now.
I used to think manipulating a film camera was something any user could do because all the functions were basic and manual. Then I picked up a DSLR. The only way to make your camera work now requires some dev-computer knowledge! Can't wait to try the long exposure script with Perseids meteor shower this weekend.
Many thanks.
0xAF
Show us the results later 😉
ELB
Forecast was for rain until the am. the Storm slowed and rain didn't come until 2am. Cloud cover was almost 100%... Such a shame. I am still optimistic about using her for long exposure. Just means I need to make another trip to the woods.
Cheers.
0xAF
cant remember if we already posted this (i do not see it), but if you have a broken camera we may use it.
if it's 400d please contact us, if it's another camera please see here:
http://www.magiclantern.fm/whats-new/78-news/133-defective-cameras
aalper
hello everyone.. i ve been using this for a while and it's really a great job. i have recomendations. yesterday i tried time lapse and i wish i could select intervalometer in self timer option. i wanted to shoot runrise if i had an intervalometer option in self timer menu i didnt have to wake up. and in intervalometer menu shot count restrict to 250 . why is that? i want to shoot thousand maybe? is there a way to resolve this issues?
sterr
I use CHDK long time but never use some extended functions, as maximum is AEB script. But some problem in the world of DSLR canon not solved. It is lenses of old film cameras. As SIGMA, Tamron etc. Perfect quality, but protocol of controlling apperture is wrong. Shutting only on full open diaphragm. I know that it's really solve in CHDK, because I see is source lens parameters read. It's will be more effective CHDK update than all do before. Main problem is get old commands for old lenses for change it protocols in CHDK and make compatible with new DSLR Cameras.
And issue that I found in 400d plus - I can't shut with long time. I will set all parameters and move cursor to 'ready' (I dont, know how it in english may be 'apply') but nothing matter. use v13 400d plus. camera XTi.
eduperez
David Reyes
Ok, i understand the stability problem. I had some problems too with my camera locking and get unresponsive because of the buffer filling quickly, so im using Jpgs instead of Raw, im sacrifying some quality but i can use 1 sec intervals.
Thank edu!!
It's been a long time, but I finally got back to this problem. I
think I finally managed to fix the cause of the locks when the scripts fires the shutter too quickly; and with the fix, the delays I had to introduce in version 20120415-11 can be removed now. Please, have a look at
comment 48 in issue 192, there is an experimental AUTOEXEC.BIN file there; scripts should be very fast with that version, as fast as the camera goes.
eduperez
I just released version 20120415-15, which hopefully fixes all issues about speed or stability in scripts.
