Make a Motion Study Change Length Without Stretching Its Important Beats

A retiming system will produce the duration you type. Ask for a four-second version of a six-second study and something four seconds long comes back, because the system's job is to satisfy the number, not to protect what the study was saying. So the work happens before you touch the duration field: sort the study's time into events whose duration must not change and intervals that can genuinely grow or shrink, mark the fixed ones where they live, and then do the arithmetic. Flexible time available, against the floors you have committed to. The arithmetic tells you whether the requested length is servable. When it isn't, the answer is a version built for that length, and saying so plainly is part of the job.

Two kinds of time, and the vocabulary that keeps them apart

Not every second of a six-second study is interchangeable with every other second. Some of it is doing work that only exists at one speed: a gesture whose easing is part of the signature, a cut that lands on an accent, a title that has to be readable before it goes. Call that time fixed. The rest is air between events, and air is where length changes happen. Call that time flexible.

Keep that pair separate from a second pair, required and optional, which is a claim about content rather than duration. They are easy to confuse because the most common flexible interval is also the one carrying the heaviest requirement. In the example below, the wordmark sits still for a stretch while someone reads it. That stretch is unprotected — its duration can change — and it is the most important requirement in the study. Flexible does not mean filler. It means the duration is negotiable, and you still have to know the limit of the negotiation.

So each flexible interval needs a floor: the shortest version of it that still does its job. The floor for a readable dwell depends on the word count, the type size, the viewing context and the pace you have been asked for, and if you cannot say where your number came from, it is a guess dressed as a specification. Write it down anyway. A written guess can be argued with; an unspoken one gets spent by the first duration request that comes in. If you also care about the long end, give each interval a ceiling — the point past which more time stops being air and starts being a stall.

These are editorial judgments with a consequence. Nothing in the software knows about them.

Protection fixes a duration, not a position

This is the distinction that decides most real length changes, and it is easy to miss because both failures look like the same failure.

A protected region keeps its duration. It does not pin that duration to a moment in the larger sequence. Protect a 0.60-second reveal and you have protected the speed of the wipe and the type-on; you have not protected the fact that it currently begins at 2.50 seconds. Change the total length and the reveal will still take 0.60 seconds, and it may now happen somewhere else.

If the reveal is cut to a musical accent at 2.50 seconds, that is a real constraint on the whole study, and it is not a protection marker. It is a relationship between the study and the sound. You have two honest responses, and they lead to different articles:

• Re-cut the music for each length, so the accent moves with the reveal. That may be the better route, but it is a music decision, and it should be made by someone deciding what the music is for rather than by whoever is adjusting a duration field.
• Accept that the reveal no longer sits on the accent, and stop calling it synchronized in the notes. Say the accent and the reveal now overlap by some amount, or that the reveal arrives late. A version that has quietly stopped being synchronized is worse than one that was never described as synchronized.

What you cannot do is protect the reveal and assume its position came along with it. Duration and placement are separate properties, and only one of them is what the marker is holding.

Marking protection in the source, and what the markers can't promise

The mechanics are modest. You mark the protected regions inside the source composition, nest that composition into a parent, and then change the duration of the nested instance. Per Adobe's documentation for Responsive Design — Time, protected time regions preserve their duration while, in an eligible composition, the unprotected portions adapt to duration changes. The documentation was checked.

Two limits come with that sentence, and both are worth keeping in view. Eligibility is a condition — this route does not apply everywhere, so treat it as a route you have confirmed, not a route that is generally available. And the same documentation records limitations for audio-bearing Motion Graphics templates in Premiere. This example stays inside the nested-composition route and makes no claim across that line.

There is one maintenance point that catches people in the middle of a campaign. The markers belong to the source composition. If you change which regions are protected in the source — because the entry gesture had to be rebuilt shorter, say — update the markers on the nested instance rather than assuming the change propagated by itself.

And a discipline point. Do not protect a region because its current timing is pleasing. Protect it because something breaks if it changes. Every protected second is a second the system has to find somewhere else, and a study with 4.5 of its 6 seconds protected cannot be delivered at 4 seconds. That failure has no one to blame but the markers.

One study, four requested lengths

The example below is a plan on paper, not a render. The arithmetic is exact and internally consistent; no composition was built and no version was viewed. Treat the numbers as a structure to copy onto your own study rather than as readings from a test.

A six-second study, thirty frames a second. An entry assembly builds the mark; a dwell lets the wordmark be read; a reveal wipes in a tagline; a tail holds the tagline and a URL. Two regions are protected for duration.

The baseline places the reveal at 2.50 seconds. Requests come in for 5.00, 8.00 and 3.50 seconds.

5.00 seconds. Fixed durations total 1.30 seconds, so 3.70 seconds of flexible time is available against floors summing to 2.70. One second has to come out. If the reveal is free of the music, that second can come from either flexible interval, and a distribution like dwell 1.40 with tail 2.30 works. If the accent is locked at 2.50 seconds, the dwell cannot shrink at all — 0.70 plus 1.80 is what puts the reveal on the accent — so the entire second comes out of the tail, leaving 1.90, which is still above the 1.50 floor. Either way this length is servable. Note that the two routes produce different pieces: one has a tighter read, the other has a shorter ending.

Then inspect what the retime actually did. The distribution may not match your priorities, and the system did not do anything wrong when it chose otherwise. If the dwell came back at 1.10 seconds, that is under the reading floor, and you correct it by taking time from somewhere else and rebuilding the tail. Add 0.10 to the dwell, subtract 0.10 from the tail, confirm both are inside their bounds.

The lengths no placement can serve

At some point the arithmetic stops having a solution, and the useful thing is to see it before you spend an afternoon nudging keyframes.

8.00 seconds needs 6.70 seconds of flexible time against ceilings summing to 6.50. There is no protected event standing in the way; the system can produce eight seconds, and the extra 0.20 would go into the dwell as a stall. That is a judgment failure rather than a system failure, and the fix is not to shorten the request. Put something in the dwell — a second product view, a line that only appears in the long version — so the added time is occupied rather than absorbed. With the accent locked at 2.50 seconds, though, the problem changes shape: the tail would have to run 4.90 seconds against a 3.50 ceiling, 1.40 over, and no honest distribution exists. Eight seconds then needs a music edit or a different structure.

3.50 seconds fails on the floor. Flexible time available is 2.20 against floors of 2.70, half a second short. This is the case worth examining slowly, because a half second looks close enough to solve by trimming.

Take the URL out of the tail. Its floor drops by 0.40, to 1.10, and the total floors become 3.60 — still 0.10 over. Rebuild the entry gesture at 0.45 instead of 0.70 and you save 0.25 more, reaching 3.35, which fits. But that second change means reopening a protected region, which means the retime is no longer the operation you are performing. And it is a change to a protected duration made under pressure from a length request, which is exactly the direction of travel the markers exist to prevent. With the accent still locked at 2.50 seconds, 3.50 leaves 0.40 seconds for the tail against a 1.50 floor, and the position has to give as well.

So the shortest request needs three separate concessions: the URL goes, the entry gesture is rebuilt, and the reveal loses the accent. That is a description of a different study. Say it that way. "The reading requirement and the entry gesture together account for more than the length allows before any air" is a sentence a producer can act on. Silently compressing the dwell and delivering three and a half seconds is not, even though it looks like compliance.

Retimed version or rebuilt version

The comparison is only fair if both routes are judged against the same requirements, so hold the floors fixed and ask what each route does with them at 5.00 seconds.

The retimed version keeps the four events in order at their original speeds and removes air. Its advantages are real: one source to maintain, later changes to the look propagating to every length, and a family of versions that are visibly the same campaign. Its costs are subtler. Near the floors, the piece reads as hurried — a dwell at 1.20 seconds that was designed against 1.80 does not feel efficient, it feels rushed — and the entry and reveal keep a six-second pace inside a five-second piece, which some viewers register as the same advertisement cut short rather than a shorter advertisement.

The rebuilt version is designed at 5.00 seconds. The tagline might arrive with the wordmark instead of after it, the entry and dwell might overlap, the URL might be abandoned entirely because the end card carries it. Its advantage is coherence: the beats were chosen for this length, so nothing is spending its floor. Its cost is maintenance. There are now two studies, and a late change to the mark or the palette has to be made twice, by someone who remembers that the two differ deliberately.

The choice follows from what the request is for. If it is a delivery format — the same idea, tighter — retime. If it is a different length of attention, rebuild. And when a requested length cannot be served because a requirement would have to be abandoned, the rebuild is not the fallback. It is the answer.

What to recheck, and the range you can quote

Protected durations do not prove that anything is legible. Check the reading state at the size and in the condition it will actually be seen in, not at 100 percent on a desktop monitor with the timeline two feet away. That check is a person looking at the render, and if you have not done it, the reading floor is still a guess, however carefully it was derived.

Check the sound. Any length change moves events relative to the music, and a voice track adds its own constraint: the timing of what is heard is now partly a question about the words. This is where the documented limitation for audio-bearing Motion Graphics templates in Premiere matters, and it is a reason to keep the demonstration inside the nested-composition route rather than extending it by analogy.

Then recheck the thing the system decided for you: where each unprotected interval landed. Compare the delivered event times against the intended ones. The protection markers handle what cannot move. They have no opinion about what should.

For this study, the range you can quote is 4.00 seconds at the tight end to 7.80 at the long end, and with the accent locked at 2.50 seconds it narrows to 4.60–6.60, with every second of change coming out of the tail. Inside that band, retiming is a legitimate route, with the caveat that the outer edges are floors and ceilings rather than comfortable working positions. Below 4.00, or below 4.60 with the sync intact, the request needs a version built to that length.

That band is a property of this study's requirements, not of the software. A study with a two-second legal line and a 0.40-second logo sting has a different band, and finds it the same way: name the fixed events, write the floors, do the subtraction, and when the subtraction fails, explain the exception instead of absorbing it.

Frequently asked questions

What should happen before entering a requested duration?

Sort the study's time into fixed events whose duration must not change and flexible intervals that can grow or shrink, mark the fixed ones where they live, write floors for the flexible intervals, and then do the arithmetic: flexible time available against the floors. If the requested length is not servable, the answer is a version built for that length, said plainly.

Does protecting a region also keep it at the same moment in the sequence?

No. Protection keeps a duration, not a position. A protected 0.60-second reveal keeps the speed of the wipe and type-on, but when the total length changes it may begin somewhere else. If it was cut to a musical accent at 2.50 seconds, that is a relationship to the sound, not a protection marker; either re-cut the music for each length or stop calling it synchronized. Duration and placement are separate properties.

How do floors and ceilings relate to required and optional content?

Fixed and flexible are about duration; required and optional are about content. A flexible interval can carry the heaviest requirement—for example, a wordmark dwell that must be readable—while its duration is still negotiable. Its floor is the shortest version that still does its job, and its ceiling is the point past which more time becomes a stall.

In the example, why does 3.50 seconds require a different study?

Flexible time available is 2.20 seconds against floors of 2.70. Removing the URL lowers the tail floor by 0.40, to 1.10, but total floors become 3.60—still 0.10 over. Rebuilding the entry gesture at 0.45 instead of 0.70 saves 0.25 and reaches 3.35, which fits, but that reopens a protected region. With the accent locked at 2.50 seconds, 3.50 leaves 0.40 seconds for the tail against a 1.50 floor. So the request needs the URL gone, the entry gesture rebuilt, and the reveal losing the accent: three concessions that describe a different study.

When should a requested length be retimed versus rebuilt?

Retime when the request is a delivery format—the same idea, tighter—holding floors fixed. Its advantages are one source to maintain and later changes propagating to every length; near the floors it can read hurried, with entry and reveal keeping a six-second pace inside a shorter piece. Rebuild when the request is a different length of attention; the beats are chosen for that length so nothing spends its floor, but there are now two studies to maintain. When a requirement would have to be abandoned, the rebuild is not the fallback—it is the answer.

Further reading

• Fit Temporary Music to a Commercial Sample: Re-edit the Structure or Stretch the Time? — The same choice appears in temporary music: removing parts before the arrival or changing the tempo, with the arrival protected either way.