On page 11, 5th messeage - May / 2009, 19:04:22 - user Obihoernchen posted photo of some program, which shows delay of the triggering. Can you anyone tell me the name of this program? I want measure delay of triggering of my A590is.
First of all, I noticed that in all modes I get a red message in the top left corner of the camera screen that says "uBASIC:9 Parse err". I don't think I've ever noticed that before. Did I do something wrong in copying the script?
I think this matches the error I've been getting from the motion detector script when in video mode. Its difficult to read but I think I have noticed the word exiting. Does that mean that it thinks I'm in play mode when I'm in video mode? Is there some setting that I should change to make it realize its in video mode? I've looked for something like that but couldn't find anything...
(Btw is there a reason that the motion detector script I am using, the first one, doesn't seem to be on the main scripts page? I went there to check and I found a different one instead, but I think the one I've been using works better.)
The motion detection script works very well in photo mode, but it doesn't work in video mode at all. It simply exits immediately when I try to run it. I think that maybe it isn't detecting that the camera is in video mode. Has anyone else had this problem, or know how to fix it? I really want to use the motion detector with video. (Alternately, if anyone knows of another script that would work that would also be great, but I really like how this one works with the photos and I'd love to use it with video).
You should try an older version of the MDFB script from here:
Because the wiki doesn't allow file attachments and I don't want to read support requests from people who break my scripts incorrectly copy pasting them using weird browsers on even more weird operating systems with increasingly weird character sets. And because I'm downright lazy.
Yes, either your script is corrupt (memory card could be corrupt or you may have copied or edited the script incorrectly) or you are running an incompatible CHDK version. Anything that goes wrong for you may be due to this.
Yes. If this is correct, the ixus80_sd1100 get_mode is broken in CHDK. You can probably make things printed by the test script prevail on the screen longer by duplicating each of the if M=? then print "something" lines...say, 20 times each.
Started by LjL
« 1 2 »
Started by fudgey
Started by A630Lover
Started by Mushin
Started by waspinator