I'd like to take second and sub-second timelapse videos with my Canon 7D. I've tried both DslrDashboard and Magic Lantern, and couldn't figure out how to set the timelapse any faster than that. Worse, both of them ended up taking photos at such a jittery rate that I could hear it was completely off kilter. The camera would take one photo, then wait for a couple seconds before taking two in less than half a second, and so on, making the result unusable for video making. I was using manual focus and manual mode, with shutter time, f-stop and ISO all set to static values. I generally set white-balance manually using a grey card, but I don't remember if I did for this shoot.
The camera is otherwise perfectly capable of taking many photos per second, even at RAW quality. Is there some fundamental issue with the timing used when remote controlling (and even when using custom firmware) causing this, or did I miss an important setting to make it all work? If this is simply an issue with both these products, are there other software products which will reliably take 1 Hz or faster time lapse series?
To be clear, the question is not how to make timelapse photos as quickly as possible, but rather:
- How to avoid jitter, that is, the time between images deviating significantly from the preset in either direction.
- How to take sub-second timelapse series, not necessarily anywhere near the hardware limit. I know of no software which allows for even 1/2 second delay between photos.
I have two memory cards, one which says "UDMA 7" and the other (a Sandisk Extreme) which says simply "UDMA". I don't remember which one I used, but AFAIK both of these should be more than fast enough.
I did a double check using Magic Lantern, to quantify the results. I set it to take 1 FPS, set focus to manual, ISO 100, disabled bracketing, set quality to small JPEG, set drive mode to single shooting and turned off preview. In 390 seconds it took 389 photos. Sounds accurate enough, but that's until we consider the jitter. If the timing was jitter free there would be exactly one timestamp with zero photos, and all the rest would have one.
To summarise the graph, 173 timestamps had 0 photos, 45 had 1 photo, and 172 had 2 photos. So it looks like the either timer is way off, or the camera is not recording timestamps in the EXIF tags appropriately.
Now the question is: What could still be causing this? Please note that this operation produced very small amounts of data compared to normal shooting (each image was only ~2 MB).
The Triggertrap app+kit is another interesting solution, but I've two reservations:
- Their web page seems to be falling apart, with several broken links encountered within minutes. If the company goes under without first open sourcing their software I fear the app will not be maintained and the kit will be useless as soon as I get an unsupported phone. I would be happy to be convinced otherwise - maybe the app functionality can be replicated easily - but longevity is a major concern.
- After the disappointment with the other solutions and Triggertrap issues with Android audio, I'm wondering just how fast the app can actually trigger on my camera. Betting 30 quid on it seems a bit premature right now.