heygen-com--hyperframes/skills/remotion-to-hyperframes/references/sequencing.md

Sequencing translation: Sequence, Series, Composition root

How Remotion's nested Sequence tree maps to HF's flat data-start / data-duration markup with a single paused GSAP timeline.

The core idea

Remotion's <Sequence from={F} durationInFrames={D}> is a coordinate transform: it shifts useCurrentFrame() by F and clips the child component to the window [F, F+D]. HF doesn't have a per-element "current frame" — there's a single composition seek time and the runtime hides/shows elements based on their data-start / data-duration.

Result: the nested tree flattens into a list of siblings on the same parent, each with their own time window.

<Composition> → root #stage

<Composition
  id="MyVideo"
  component={MyVideo}
  durationInFrames={300}
  fps={30}
  width={1280}
  height={720}
/>

<div
  id="stage"
  data-composition-id="MyVideo"
  data-start="0"
  data-duration="10"      <!-- 300/30 -->
  data-fps="30"
  data-width="1280"
  data-height="720"
>
  <!-- composition content -->
</div>

data-start="0" is required on #stage (the runtime needs it to anchor playback; missing it triggers a lint warning).

<AbsoluteFill> → positioned div

<AbsoluteFill style={{ backgroundColor: "#0a0a0a" }}>...children...</AbsoluteFill>

<div style="position:absolute;inset:0;background-color:#0a0a0a;">...children...</div>

AbsoluteFill is just a styled div in Remotion. Translate to a div with position:absolute; inset:0 and copy through any other style props.

<Sequence> → time-windowed div

<Sequence from={0} durationInFrames={90}>
  <TitleCard />
</Sequence>

<div data-start="0" data-duration="3" data-track-index="0">
  <!-- TitleCard children inlined -->
</div>

Convert frames to seconds: from/fps, durationInFrames/fps. Pick a data-track-index per parallel rendering layer (background = 0, overlays = 1, audio = 2, etc.). Sequential scenes can share an index.

Nested <Sequence> flattens

Remotion adds offsets when sequences nest:

<Sequence from={60} durationInFrames={120}>
  <Sequence from={30} durationInFrames={60}>
    <ImageScene />
  </Sequence>
</Sequence>

The inner sequence's effective window is [60+30, 60+30+60] = [90, 150].

Translate by computing the sum and emitting one HF div with the resolved window:

<div data-start="3" data-duration="2" data-track-index="0">
  <!-- ImageScene children -->
</div>

<Series> → siblings with sequential offsets

<Series>
  <Series.Sequence durationInFrames={60}>
    <A />
  </Series.Sequence>
  <Series.Sequence durationInFrames={120}>
    <B />
  </Series.Sequence>
  <Series.Sequence durationInFrames={90}>
    <C />
  </Series.Sequence>
</Series>

Each Sequence.Sequence lives in the next time slot. Emit siblings with data-start accumulating:

<div data-start="0" data-duration="2" data-track-index="0">A</div>
<div data-start="2" data-duration="4" data-track-index="0">B</div>
<div data-start="6" data-duration="3" data-track-index="0">C</div>

Crossfading scene boundaries

Remotion <Sequence> shows/hides at hard boundaries by default. HF does the same — but if your composition needs a smooth fade between scenes, you have to drive opacity explicitly with GSAP at the boundary:

const tl = gsap.timeline({ paused: true });
tl.set(scene1, { opacity: 1 }, 0);
tl.set(scene1, { opacity: 0 }, 2); // hard cut at 2s
tl.set(scene2, { opacity: 1 }, 2);

For a 0.5 s crossfade:

tl.to(scene1, { opacity: 0, duration: 0.5 }, 1.5);
tl.to(scene2, { opacity: 1, duration: 0.5 }, 1.5);

For Remotion <TransitionSeries> translations see transitions.md.

<Loop>

<Loop durationInFrames={30}>
  <Spinner />
</Loop>

HF doesn't have a <Loop> primitive. Translate to a GSAP timeline with repeat: -1:

const spinTl = gsap.timeline({ paused: true, repeat: -1, repeatRefresh: false });
spinTl.to(spinner, { rotate: 360, duration: 1.0, ease: "none" });
// Embed in the main composition timeline at the right offset:
mainTl.add(spinTl, 3);

This is fragile — Remotion's <Loop> resets internal state every iteration, which GSAP repeat does too, but if the looped child has its own animation, you need to be careful that GSAP's repeatRefresh is on or off as needed. For most simple "spin forever" cases this is fine.

<Freeze>

<Freeze frame={30}>
  <Animated />
</Freeze>

Drop the wrapper. <Freeze> pins useCurrentFrame() at a constant for the children — but in HF, the children's animation is already driven by explicit GSAP tweens, so freeze translates to "don't tween this element".

Multiple parallel tracks

When you have a background video + overlay text + audio playing simultaneously, use distinct data-track-index values:

<div data-track-index="0">background video</div>
<div data-track-index="1">overlay text</div>
<audio data-track-index="2" ...></audio>

The runtime picks track ordering from the index. See media.md for media-specific track conventions.