I don't have a fully charged set of batteries with me but my theory is that battery drain in video modes is very high and if you have a set of batteries that are partially depleted, they will quicky drop even further when the you start recording. When you stop recording, the batteries appear to recover. I'll test this with a new set of batteries this weekend but I'm seeing the same effect with CHDK loaded or not loaded.
Today I tried a new set of batteries and a potential drop is much smaller, but I noticed that the size of an SD card significantly affect the electricity consumption.Original Canon SD card 128 MB at the start indicates 100 percent of the battery charge and the video recording rate quickly drops for 5 percent.TakeMS card 8GB at the start indicates 95 percent of the battery charge and the video recording rate quickly drops for 20 percent, further diminished the percentage is much faster than on a smaller card, memory chip consumption takes its price.
I haven't had a chance to do any more video tests with fresh batteries yet - I'm actually on vacation right now so I haven't had time to do much experimentation. Will be back home on Sunday and should be doing more investigating after that.
I'd offer to look at the code but I suspect by the time I got my head around it someone more experienced will have some better answers...and I don't do much C anymore and haven't touched assembly in years. But I do plan on at least setting up enough of a dev environment to be able to build from source so when/if I get some time I can browse through the code and try to get a feel for how this all works.
I do seem to be able to load grids from playback mode as long as I load the smallest rulers grid first. For some reason loading that grid first always seems to work and I can then load other grids. But if I try to load any other grid first then the camera crashes. There may be something else going on that I'm missing though as to why that seems to work.
Did try the HDR script today while I was out and about and it seemed to work quite well...if not a little slower than I would have hoped. But I haven't even looked at the script source yet to see if there are built in pauses or something. Really hope I can find time to look at the motion sensing script soon and figure out if this camera can do faster motion sensing, right now it's too slow to be a useful feature for me just using the default sample scripts. (by even someone slowly walking past is out of frame by the time it triggers - absolutely no chance of catching lightening.) Hopefully it's just the default settings in the sample script that cause it to be so slow right now <fingers crossed>
Anyway my question is if I buy the 50 is there a chance that there is a FW rev d on the 1200 that isnt ported yet and then I have 50 cameras sitting waiting...or should I continue the battle with the A810?
I have a couple with FW - C and am happy with the results but couldnt find anymore. I picked up an A810 as a newer camera that had some CHDK ports but am sitting with it now and cant even get the FW rev to display.
Started by praveen_sb
Started by prbaxter
General Discussion and Assistance
Started by Photon
« 1 2 »
Started by noobie
RAW Shooting and Processing
Started by ripwink