UMBRA

Your guide to eclipse day success.

Totality lasts a couple of minutes and it does not come back. The difference between the photos you dreamed about and a day you would rather forget is almost always preparation, not gear. Here is how I get ready, and what I do when something goes sideways.

The one rule: rehearse the whole thing for real before the day, in conditions as close to the real event as you can manage. Everything below is in service of that. Umbra automates the shutter so you can watch the sky, but the automation is only as good as the run you tested.

Weeks ahead  build confidence, not just a script

Do a full, realistic dress rehearsal

Not a quick indoor test. Run the complete sequence from first contact to last, outdoors, in heat and sun like the real day, with the exact rig you will actually use.

Use the Analyzer ahead of time

After a rehearsal, drop the memory card into your Mac and run the Simulation Analyzer. It reads every frame and reconciles it against your script: counts, timing, exposure, drops. Fix whatever it flags now, while you still can. Doing this weeks early is the single best way to catch a problem that would otherwise only show up on eclipse day.

Leave about a second between frames

Tight bursts look great on paper, but the real limit is how fast each body writes to its card, and a body with any per-frame processing on (long-exposure or high-ISO noise reduction) is slower still. I run about 1 second between frames. Multi-camera rigs start dropping frames at 0.4 to 0.6 second spacing but stay clean at 1 second, and you still get roughly 180 frames per body across a 3-minute totality, far more than the corona's slow change needs. Reliability beats frame count. Umbra's Script Wizard sets its minimum spacing from the rig you actually have connected, for exactly this reason, and it is more generous on the universal driver than on a native SDK.

Turn off in-camera noise reduction

This one bit me in testing. Long-Exposure NR and High-ISO NR make a body do extra processing after each frame, so it can't keep up with a fast burst, and it drops shots. The tell is sneaky: on a four-camera run with an identical script, the two bodies that had NR on dropped roughly twice as many frames as the other two. Umbra now flags that asymmetry for you, but it can't read the setting over USB, so check each body yourself: turn Long-Exposure NR and High-ISO NR off before the day. You can always denoise in post; you can't get the frame back.

Practice removing your solar filter

At second contact you have a few seconds to pull the filter, and again at third contact to put it back. Practice until it is smooth and does not jog your framing.

Practice and test a battery swap on every body

Some cameras behave oddly across a battery swap: they drop the USB session, forget a setting, or take a moment to re-enumerate. Find out how each of yours behaves now.

Have a backup plan, and a manual-takeover plan

Decide in advance what you do if something breaks during totality, because you will not have time to think it through then.

Scope a last-minute location change

Weather moves. You may have to relocate the day before, or even the morning of, to a spot with a shorter or longer totality, or with less time to set up.

The night before  remove tomorrow's surprises

Charge, format, scout

The morning of  get everything going, calmly

Power up early and verify the whole chain

Protect the Mac from the heat

This is the failure that catches the most people. A hot Mac throttles its CPU, and a throttling Mac drops shots.

During the eclipse  trust it, watch the sky, stay ready

Let the automation work, hold your plan in your hand

Gear that helps

A few inexpensive things that save the day

Next: the getting-started guide walks through the app itself, and the script language guide covers how to write or tweak a capture script by hand.