The Invisible Seam

Here is the fact underneath that message: a three-hour episode is not three hours of animation. It is a few minutes of animation, arranged so you cannot find the place where it starts again. This is the least glamorous part of what we do and probably the part we think about most.

Why there is a loop at all

The honest maths first, because the alternative sounds like an excuse when it comes later.

Rendering genuinely unique frames for eight hours is roughly a hundred times the render time of a five-minute loop, and render time is the one part of this that cannot be worked around by caring more. A long episode also has to stream reasonably on a phone in a bedroom with poor signal, and unique frames compress far worse than repeating ones — the encoder's whole job is finding repetition, and we would be removing its best material.

So an eight-hour episode is built from layers that repeat. So is essentially every ambient video you have ever left on. The question was never whether to loop, only whether you find the seam.

The loop isn't the compromise. The compromise is when you can see where it joins.

In the four-minute cat we listed four working rules; the fourth was let the loop be invisible. This is that rule with its sleeves rolled up.

The trick with awkward numbers

The most useful technique is also the simplest, and we did not invent it — it comes from music, where people have been hiding repetition for centuries.

Do not loop the scene. Loop each layer separately, at lengths that do not divide into each other.

Rain at 47 seconds. Steam at 31. The fire's slow breath at 23. The lamp flicker at 19. Each is short enough to render and store cheaply, but because none of those numbers share a factor, the combination only returns to its exact starting state after about six and a half hours.

It breaks down when a layer is visually dominant. If the rain is the loudest thing on screen, its 47 seconds will be found on its own, however cleverly the other three are offset. Dominant layers have to be long, or irregular, or both.

Three ways to hide a seam, and what each costs

There is no free method; each buys invisibility with something.

1. 1

   Cross-fade the join

   Overlap the end of the loop with its beginning and dissolve between them. Cheap, universal, and the reason so much ambient video has a faint breathing quality — on a still shot, a regular dissolve reads as a slow pulse of light. You have hidden a seam by installing a heartbeat, and people feel the heartbeat even when they cannot name it.

2. 2

   Hide the join behind motion

   Put the cut where something else is moving — a cloud shadow, a page turning, a car light crossing the wall. It works completely. But we allow ourselves roughly one moving element per scene, so this spends the shot's entire motion budget on housekeeping instead of on the room. It is the option that most often makes a scene worse in a way you cannot point at.

3. 3

   Make the loop longer than anyone's patience

   The honest one. Render nine or fourteen minutes instead of ninety seconds, offset the layers, accept the render hours and the file size. This is what we do for the long flagship episodes, and the only method with no aesthetic cost — just an ordinary financial and temporal one.

Almost every episode is some mixture of the three, and the mixture is decided by the schedule far more often than by taste.

We take this seriously because discovery is a one-way door.

Before you find it, you are looking at a room. After you find it, you are looking at a file. The scene has not changed by one pixel, but your attention has switched from the thing to the mechanism, and it does not switch back — not in that episode, and often not in the next one, because now you are the sort of viewer who checks.

That is what our minute-34 correspondent lost, and why the message stung. He did not lose seven seconds of rain. He lost the ability to be inside that particular room, permanently — and we gave that away to save render hours in a week that was already behind.

When we stop looping altogether

There are places we simply pay full price.

Anything with a fire in the foreground. Fire is the one element where the eye holds an unreasonably precise memory, and a repeating flame is uncanny the way a repeating face is uncanny. Foreground fire gets rendered long — twelve to fifteen minutes minimum — even when the budget hates it.

Anything with an animal in it. Same reason. A living thing that repeats its exact behaviour stops reading as alive, and the illusion of a room where someone lives collapses with it.

Openings. The first four or five minutes of every episode are unique, no loop at all, because that is when attention is highest. It is also the honest place to spend: the beginning is the part everybody sees.

Where our seams are

The useful part of a piece like this is the list, so here is the list. These are the episodes where we know the seam is findable, and roughly where.

The first eight-hour rain window. The one the message was about. A 47-second rain loop with one drop brighter than the others, visible in the left pane throughout, and the whole episode runs on that single cycle. The worst seam in the catalogue, on our most-watched file, which is a special kind of annoying.

The early fireside episode. Flames on a 12-second loop with a cross-fade, and a visible dip in brightness at each join. We knew during the render and shipped it anyway because the schedule had eaten the buffer. It is the reason foreground fire is now on the pay-full-price list.

The first harvest-day episode. Everything is offset correctly except the wind in the trees, which is dominant, three minutes long, and therefore findable around the twenty-minute mark if you are the kind of person who notices trees.

The winter-hearth long version. Picture is fine. The sound has a nine-minute bed with an identifiable creak in it, and several people found the creak before we did.

We have not gone back to fix any of these. Re-rendering an eight-hour file to remove a seam is dozens of hours of machine time for something most viewers will never see, and we would rather spend those hours on an episode that does not exist yet. That is a real trade-off, not a principle.

The part that will not be solved

There is no version of this where the seam goes away. Every finite file repeats; the only real variable is whether the repeat falls outside the span of anybody's patience.

What we can promise is which side of that line we are trying to stand on — and that when we fail, we would rather name the episodes than let you find them yourself at minute 34.

The evening is warm here.