Capture a Small Time-Lapse Test for a Commercial Treatment
Capture a Small Time-Lapse Test for a Commercial Treatment
The treatment says the foam collapses "in a heartbeat." The client repeats it, slower, with a hand gesture. What the room actually has is a claim about duration and nothing to look at. A short interval test fixes that, and it costs an afternoon.
Keep the test small on purpose. One safe process standing in for the thing the commercial cares about. One interval you can defend. One caption that states what the viewer is really seeing. By the end you want a labeled sequence and a review movie, plus a sentence you can read aloud: this represents ten minutes in five seconds, and here is the frame count that makes that true.
Start with the change, not with a number
The usual mistake is picking an interval the way you would pick a filter. One frame every second sounds brisk. One every ten seconds sounds dramatic. Neither choice is wrong in the abstract and neither is a decision, because the interval's job is to answer a question about your subject: how long does the part I care about take?
So name the change first. Not "the process" — the specific visible difference you want the viewer to feel. An outline that shrinks. Something accumulating where nothing was before. A transition from one state into another, with a recognizable moment where it turns. A surface that stops moving. If you cannot say which of these you need, you are not ready to choose an interval, and no camera setting will rescue you.
A tray of ice cubes in shallow water, left on a counter, is a good stand-in for a lot of commercial processes: it is safe, it is cheap, its outline changes continuously, and it ends. It is also, importantly, a process you are willing to ruin. Say you are testing ice. The worthwhile question is not whether the ice looks beautiful. It is whether the last thin sliver of a cube vanishing takes long enough to be caught by a frame at your chosen spacing. Suppose that final collapse takes about forty seconds. At a five-second interval you get roughly eight frames of it and the disappearance reads as a sequence. At a sixty-second interval you may get one frame, or none, and the moment that was supposed to carry the idea simply will not exist.
That is the whole thesis in miniature: the interval chooses what change gets sampled. Everything downstream is presentation.
One boundary worth setting now. If you walk over and turn the subject between frames, you are not observing a process, you are animating one. That is stop-motion posing, a legitimate craft with a completely different relationship to the truth, and calling it a time-lapse test would be a small lie that grows. The test is unposed. You set it going and you leave it alone.
Two durations that are not the same duration
Time-lapse confuses two numbers, and they both matter.
The interval is the time between samples. Be precise about what it measures. The convention that keeps the arithmetic clean is start-to-start: the clock from the beginning of one exposure to the beginning of the next. Your camera may implement something else. Some intervalometers start counting when the exposure finishes; some refuse to fire at all if the exposure is longer than the interval; some fold the interval setting into a menu called something else entirely. Nikon's own practitioner guidance on its mirrorless cameras, published on Nikon USA, separates the two routes a camera can take — separately captured stills, which you keep and can still edit individually, versus a built-in mode that compiles a movie for you and does not hand you the source frames — and it directs readers to their actual camera manual for whatever their model offers. Take that direction. The article is written around a particular camera line, and a camera's interval semantics are a specification you should read, not infer. (https://www.nikonusa.com/learn-and-explore/c/tips-and-techniques/time-lapse-tips-and-tricks-using-nikon-mirrorless-cameras)
The playback rate is how fast the samples are shown. Twenty-four or twenty-five frames per second is the standard viewing rate; some cameras and editors default to thirty.
Now the two calculations, and they are the only arithmetic you need.
With N samples at an interval of Δt, the real time from the first exposure to the last is (N−1)Δt. Not N. The first frame is a moment, not a duration, and one interval's worth of time happened before nobody was watching.
Playback lasts N/f seconds at f frames per second. Here it is all N, because every retained frame appears on screen.
Watch how those two disagree about what "the" duration is.
Run the numbers before you run the camera
Say you plan 121 frames at five-second intervals.
Real span: 120 × 5 = 600 seconds, ten minutes.
Playback at 25 fps: 121 ÷ 25 = 4.84 seconds.
Nothing here has been captured. These are calculations from a plan, and that is exactly the point — you can do them in a chair, before you commit an afternoon, and change your mind for free.
Now run it backward, which is often the more useful direction. If the treatment promises a five-second beat, you want a playback of five seconds. Five seconds at 25 fps is 125 frames. Hold the five-second interval and the rule gives you 124 intervals for those frames to cover: 124 × 5 = 620 seconds of real time, about ten minutes twenty seconds, to produce that shot. If ten minutes twenty seconds is more than the process actually takes, you have found a real problem in the treatment, and you have found it before the shoot rather than in the edit.
A small honesty note on how you phrase the speed. Someone will ask "so it's how many times faster?" By the span-to-playback comparison, 600 seconds in 4.84 seconds is roughly 124 times. By the frames-per-second comparison — 25 fps played against one frame every five seconds — it is 125 times. The two numbers differ by exactly one interval's worth of frames, because the opening frame has no interval in front of it. This is not a problem to solve; it is a reason to put the span, the frame count and the playback rate in the caption and skip the bare multiplier. "Ten minutes in 4.84 seconds, 121 frames at five-second intervals" cannot be misread. "125× speed" can.
Keep the test comparable
The arithmetic tells you what a plan would produce. It tells you nothing about whether the process will cooperate, which is why the trial exists.
Set the frame, focus and exposure deliberately, then record what you set. Lock focus if the subject stays put. Keep the camera from adjusting brightness on its own, because an automatic exposure decision that quietly shifts between frames turns into a pulsing flicker in playback that the client will read as a mistake in the effect rather than a mistake in the camera. If the light in the room genuinely changes over the run — daylight through a window, a lamp coming on — that is a condition of the observation, and it belongs in your notes either as intended or as an artifact. Write down what was in the frame besides the subject, the room temperature if it plausibly matters, and how long the whole thing ran.
Then run a short trial before the long capture. Give it a tight interval, tighter than you think you need, and watch for the things a plan cannot predict: a stage that blows past between two frames, focus that drifts as the subject changes shape, a brightness shift you did not cause. The trial's job is to tell you how fast the fastest interesting change actually is, in this setup, today. Use that to set the production interval so the transition you care about gets several frames rather than one.
Be honest about what a trial can and cannot tell you. A three-minute trial describes three minutes. If the interesting part of the process happens at the forty-minute mark, the trial observed a different phase of the same event, and its rate of change is evidence about that phase only. Extrapolating is reasonable; treating the extrapolation as measured is not.
The same caution applies if you decide to run the capture twice at two different intervals to compare them. Tempting, and genuinely informative, and not a controlled experiment. Two trays of ice are two different pieces of ice; two runs on two afternoons are two different rooms. If the second run shows fewer frames of the final collapse, that could be because the interval was longer or because the cube was shaped differently or the room was warmer. Say which interpretation you are offering. Comparing a result against your own earlier result is not the same as repeating a measurement.
Keep the source stills. This is the practical reason to prefer the interval timer that retains individual frames over a mode that hands you only a finished movie. You cannot inspect a movie frame by frame with the same ease, you cannot re-edit one frame's exposure, and you cannot demonstrate to a skeptical colleague that frame 87 is where the interesting thing happened. Whatever route you take, know which one you took before you start.
Assemble it and judge what you got
Assemble the sequence at the declared rate and check the count against the plan. If you intended 125 frames and you have 118, something interrupted the run — a card filling, a battery, a lapse in the trigger — and those missing frames are a gap in the record, not a detail to smooth over. Never close a gap by renaming files into a continuous sequence. A missing stage is information. An invented continuity is a fabrication, and in a client review it is one that will eventually be found.
Then watch for the right thing. Not "is the clip fast." Fast is easy and the client will supply their own adjective. Watch whether the transition you identified in the first place is legible: the moment the surface changes, the point where accumulation becomes obvious, the disappearance of the last sliver. If that moment reads, the interval was right. If it slides past, the interval was too long. If the clip feels stuttery and the motion between frames is confusing rather than exciting, the interval was too short for the amount of change actually happening, and you are now watching a slideshow of almost-identical moments.
It helps to say out loud what this test is not. It is not accelerated continuous footage, where a camera recorded every instant and playback was sped up — a different route with a different cost, a different look, and every moment retained. It is not stop-motion. And it is not a demonstration that the client's real process behaves like a tray of ice. The test's claim is narrower and more useful: here is how a change of roughly this pace, sampled at this interval, reads on screen in this many seconds. Whether the production process matches it is a question for the shoot.
The caption is the deliverable
A test like this earns its place in a treatment when someone can point at it and say what it shows, precisely, including its limits. The interval and the playback rate each decided something different — one chose which moments exist, the other chose how quickly those moments pass in front of a viewer — and both decisions are legible in a single line under the image.
Pick the interval because you know what must remain visible, run the trial because you do not yet know how fast it goes, keep the frames because you will want the audit later, and caption the real span beside the screen time. Then the sequence in the treatment is not a mood. It is a claim, and the frame count is standing behind it.
Frequently asked questions
How should you choose the interval for a time-lapse test?
Start with the change, not a number. Name the specific visible difference you want the viewer to feel, such as an outline shrinking, something accumulating, a transition with a recognizable turning moment, or a surface stopping. The interval's job is to answer how long the part you care about takes. For the ice example, if the final collapse takes about forty seconds, a five-second interval gives roughly eight frames, while a sixty-second interval may give one frame or none.
What is the difference between the interval and the playback rate?
The interval is the time between samples, and the article uses start-to-start as the convention that keeps arithmetic clean, while noting your camera may implement something else. The playback rate is how fast the samples are shown, commonly 24 or 25 frames per second. With N samples at interval delta t, the real time from first to last exposure is (N minus 1) times delta t, not N. Playback lasts N divided by f seconds at f frames per second.
How can the arithmetic check a treatment before you shoot?
Run the calculation backward. If the treatment promises a five-second beat at 25 fps, you want 125 frames. Holding a five-second interval gives 124 intervals for those frames to cover: 124 times 5 equals 620 seconds, about ten minutes twenty seconds. If that is more than the process actually takes, you have found a real problem in the treatment before the shoot rather than in the edit.
What can a short trial tell you, and what can it not tell you?
A short trial tells you how fast the fastest interesting change actually is in this setup today, so you can set the production interval so the transition gets several frames rather than one. It also reveals stages that blow past between frames, focus drift, and unplanned brightness shifts. But a three-minute trial describes three minutes. If the interesting part happens at forty minutes, the trial observed a different phase, and its rate of change is evidence about that phase only. Treating an extrapolation as measured is not honest.
Why keep source stills and avoid filling gaps in the sequence?
Keeping individual frames lets you inspect frame by frame, re-edit one frame's exposure, and demonstrate that frame 87 is where something happened. If you intended 125 frames and have 118, something interrupted the run, and those missing frames are a gap in the record. Never close a gap by renaming files into a continuous sequence. A missing stage is information; an invented continuity is a fabrication that will eventually be found in client review.