Skip to content

🎥 Make videos programmatically with React

Skills: Replace Series examples with TransitionSeries

Jonny Burger7c496ab21e87
diff --git a/packages/codex-plugin/skills/remotion-best-practices/remotion-markup/sequencing.md b/packages/codex-plugin/skills/remotion-best-practices/remotion-markup/sequencing.md
index 83c7ea03b8..16c6f0a4ce 100644
--- a/packages/codex-plugin/skills/remotion-best-practices/remotion-markup/sequencing.md
+++ b/packages/codex-plugin/skills/remotion-best-practices/remotion-markup/sequencing.md
@@ -90,42 +90,42 @@ Always premount any `<Sequence>`!
</Sequence>
```
-## Series
+## TransitionSeries
-Use `<Series>` when elements should play one after another without overlap.
+Use `<TransitionSeries>` when elements should play one after another without overlap.
```tsx
-import { Series } from "remotion";
+import { TransitionSeries } from "@remotion/transitions";
-<Series>
- <Series.Sequence durationInFrames={45}>
+<TransitionSeries>
+ <TransitionSeries.Sequence durationInFrames={45}>
<Intro />
- </Series.Sequence>
- <Series.Sequence durationInFrames={60}>
+ </TransitionSeries.Sequence>
+ <TransitionSeries.Sequence durationInFrames={60}>
<MainContent />
- </Series.Sequence>
- <Series.Sequence durationInFrames={30}>
+ </TransitionSeries.Sequence>
+ <TransitionSeries.Sequence durationInFrames={30}>
<Outro />
- </Series.Sequence>
-</Series>;
+ </TransitionSeries.Sequence>
+</TransitionSeries>;
```
-Same as with `<Sequence>`, the items will be wrapped in an absolute fill element by default when using `<Series.Sequence>`, unless the `layout` prop is set to `none`.
+Same as with `<Sequence>`, the items will be wrapped in an absolute fill element by default when using `<TransitionSeries.Sequence>`, unless the `layout` prop is set to `none`.
-### Series with overlaps
+### TransitionSeries with overlaps
Use negative offset for overlapping sequences:
```tsx
-<Series>
- <Series.Sequence durationInFrames={60}>
+<TransitionSeries>
+ <TransitionSeries.Sequence durationInFrames={60}>
<SceneA />
- </Series.Sequence>
- <Series.Sequence offset={-15} durationInFrames={60}>
+ </TransitionSeries.Sequence>
+ <TransitionSeries.Sequence offset={-15} durationInFrames={60}>
{/* Starts 15 frames before SceneA ends */}
<SceneB />
- </Series.Sequence>
-</Series>
+ </TransitionSeries.Sequence>
+</TransitionSeries>
```
## Frame References Inside Sequences
diff --git a/packages/codex-plugin/skills/remotion-markup/sequencing.md b/packages/codex-plugin/skills/remotion-markup/sequencing.md
index 83c7ea03b8..16c6f0a4ce 100644
--- a/packages/codex-plugin/skills/remotion-markup/sequencing.md
+++ b/packages/codex-plugin/skills/remotion-markup/sequencing.md
@@ -90,42 +90,42 @@ Always premount any `<Sequence>`!
</Sequence>
```
-## Series
+## TransitionSeries
-Use `<Series>` when elements should play one after another without overlap.
+Use `<TransitionSeries>` when elements should play one after another without overlap.
```tsx
-import { Series } from "remotion";
+import { TransitionSeries } from "@remotion/transitions";
-<Series>
- <Series.Sequence durationInFrames={45}>
+<TransitionSeries>
+ <TransitionSeries.Sequence durationInFrames={45}>
<Intro />
- </Series.Sequence>
- <Series.Sequence durationInFrames={60}>
+ </TransitionSeries.Sequence>
+ <TransitionSeries.Sequence durationInFrames={60}>
<MainContent />
- </Series.Sequence>
- <Series.Sequence durationInFrames={30}>
+ </TransitionSeries.Sequence>
+ <TransitionSeries.Sequence durationInFrames={30}>
<Outro />
- </Series.Sequence>
-</Series>;
+ </TransitionSeries.Sequence>
+</TransitionSeries>;
```
-Same as with `<Sequence>`, the items will be wrapped in an absolute fill element by default when using `<Series.Sequence>`, unless the `layout` prop is set to `none`.
+Same as with `<Sequence>`, the items will be wrapped in an absolute fill element by default when using `<TransitionSeries.Sequence>`, unless the `layout` prop is set to `none`.
-### Series with overlaps
+### TransitionSeries with overlaps
Use negative offset for overlapping sequences:
```tsx
-<Series>
- <Series.Sequence durationInFrames={60}>
+<TransitionSeries>
+ <TransitionSeries.Sequence durationInFrames={60}>
<SceneA />
- </Series.Sequence>
- <Series.Sequence offset={-15} durationInFrames={60}>
+ </TransitionSeries.Sequence>
+ <TransitionSeries.Sequence offset={-15} durationInFrames={60}>
{/* Starts 15 frames before SceneA ends */}
<SceneB />
- </Series.Sequence>
-</Series>
+ </TransitionSeries.Sequence>
+</TransitionSeries>
```
## Frame References Inside Sequences
diff --git a/packages/skills/skills/remotion-captions/display-captions.md b/packages/skills/skills/remotion-captions/display-captions.md
index 6e6b7297be..2ecdbe14da 100644
--- a/packages/skills/skills/remotion-captions/display-captions.md
+++ b/packages/skills/skills/remotion-captions/display-captions.md
@@ -33,7 +33,7 @@ Fetch its source code from https://www.remotion.dev/elements/captions/basic-capt
## Displaying captions alongside video content
-Keep each clip's video and captions inside the same `<Sequence>`, `<Series.Sequence>`, or `<TransitionSeries.Sequence>`.
+Keep each clip's video and captions inside the same `<Sequence>` or `<TransitionSeries.Sequence>`.
Put the clip's `trimBefore`, `durationInFrames`, and `playbackRate` on that shared parent so trimming or changing the speed affects both.
For independently positioned clips, put `from` on the shared `<Sequence>` too.
@@ -52,15 +52,16 @@ Give the caption area a width and position it over the video. In this
```tsx title="src/MyComposition.tsx"
import { Video } from "@remotion/media";
-import { Series, staticFile, useVideoConfig } from "remotion";
+import { TransitionSeries } from "@remotion/transitions";
+import { staticFile, useVideoConfig } from "remotion";
import { BasicCaptions } from "./basic-captions";
export const MyComposition: React.FC = () => {
const { fps } = useVideoConfig();
return (
- <Series>
- <Series.Sequence
+ <TransitionSeries>
+ <TransitionSeries.Sequence
name="Opening"
trimBefore={4 * fps}
durationInFrames={20 * fps}
@@ -99,8 +100,8 @@ export const MyComposition: React.FC = () => {
},
]}
/>
- </Series.Sequence>
- <Series.Sequence
+ </TransitionSeries.Sequence>
+ <TransitionSeries.Sequence
name="Next clip"
trimBefore={1 * fps}
durationInFrames={5 * fps}
@@ -139,8 +140,8 @@ export const MyComposition: React.FC = () => {
},
]}
/>
- </Series.Sequence>
- </Series>
+ </TransitionSeries.Sequence>
+ </TransitionSeries>
);
};
```
diff --git a/packages/skills/skills/remotion-interactivity/SKILL.md b/packages/skills/skills/remotion-interactivity/SKILL.md
index e59b484b8a..ba2a36e57b 100644
--- a/packages/skills/skills/remotion-interactivity/SKILL.md
+++ b/packages/skills/skills/remotion-interactivity/SKILL.md
@@ -203,9 +203,8 @@ distinction when moving animation styles.
Keep a `<Sequence>` when it provides shared timing for multiple siblings,
overrides dimensions for `useVideoConfig()`, or wraps a component that does not
-handle timing. Keep `<Series.Sequence>` for consecutive layout and
-`<TransitionSeries.Sequence>` for transitions; direct `from` props do not
-replace those behaviors.
+handle timing. Keep `<TransitionSeries.Sequence>` for consecutive layout,
+with or without transitions; direct `from` props do not replace those behaviors.
## Give every independently editable item its own JSX node
@@ -215,20 +214,22 @@ items come from the same JSX node, they share one source-editing target.
For every composition registration, clip, scene, layer or sequence that should
be editable on its own, write a separate JSX node and keep its editable props
on that node. This applies to `<Composition>`, `<Still>`, built-in media
-components, `<Sequence>`, `<Series.Sequence>`, `<TransitionSeries.Sequence>`
+components, `<Sequence>`, `<TransitionSeries.Sequence>`
and custom components.
For example, author an editable timeline like this:
```tsx title="Separate source nodes"
-<Series>
- <Series.Sequence name="Introduction" durationInFrames={90}>
+import { TransitionSeries } from "@remotion/transitions";
+
+<TransitionSeries>
+ <TransitionSeries.Sequence name="Introduction" durationInFrames={90}>
<Introduction />
- </Series.Sequence>
- <Series.Sequence name="Demo" durationInFrames={150}>
+ </TransitionSeries.Sequence>
+ <TransitionSeries.Sequence name="Demo" durationInFrames={150}>
<Demo />
- </Series.Sequence>
-</Series>
+ </TransitionSeries.Sequence>
+</TransitionSeries>
```
A `.map()` or another programmatic loop would create multiple runtime items
diff --git a/packages/skills/skills/remotion-markup/SKILL.md b/packages/skills/skills/remotion-markup/SKILL.md
index e083842b64..b0711274ff 100644
--- a/packages/skills/skills/remotion-markup/SKILL.md
+++ b/packages/skills/skills/remotion-markup/SKILL.md
@@ -33,9 +33,8 @@ with editable props, and register reusable scenes as connected compositions.
Put timing directly on components that support it; avoid redundant `<Sequence>` wrappers.
Give every timed component that supports `premountFor` one second of premounting:
`premountFor={fps}`, where `fps` comes from `useVideoConfig()`. Apply this to
-media, interactive components, `<Sequence>`, `<Series.Sequence>`,
-`<TransitionSeries.Sequence>`, and `<TransitionSeries.Overlay>`, including
-timed components nested inside scenes. Premount the parent timeline item too
+media, interactive components, `<Sequence>`, `<TransitionSeries.Sequence>`,
+and `<TransitionSeries.Overlay>`, including timed components nested inside scenes. Premount the parent timeline item too
when a nested item needs to mount before the parent starts. A component without
`premountFor`, such as `<TransitionSeries.Transition>`, needs no substitute.
diff --git a/packages/skills/skills/remotion-markup/connected-compositions.md b/packages/skills/skills/remotion-markup/connected-compositions.md
index 9ddfe225be..16a74bd34a 100644
--- a/packages/skills/skills/remotion-markup/connected-compositions.md
+++ b/packages/skills/skills/remotion-markup/connected-compositions.md
@@ -10,7 +10,7 @@ Use connected composition when a section has its own layers or timing, will be r
2. Prefer making the component interactive with `Interactive.withSchema({wrapInSequence: true})`, following [Remotion Interactivity](../remotion-interactivity/SKILL.md).
Render the exported component directly in the parent with inline timing and editable props.
It does not need an additional `<Sequence>` to connect to its registration.
- For consecutive scenes or transitions, render one direct instance as the only child of a `<Series.Sequence>` or `<TransitionSeries.Sequence>`.
+ For consecutive scenes or transitions, render one direct instance as the only child of a `<TransitionSeries.Sequence>`.
3. Register the **same component reference** with `<Composition component={...}>` in the root.
Give it a unique `id` and the dimensions, fps, and natural duration needed to preview the scene on its own. A `<Folder>` can keep scene compositions together.
diff --git a/packages/skills/skills/remotion-markup/multi-scene-video.md b/packages/skills/skills/remotion-markup/multi-scene-video.md
index ac61314459..26681cbf09 100644
--- a/packages/skills/skills/remotion-markup/multi-scene-video.md
+++ b/packages/skills/skills/remotion-markup/multi-scene-video.md
@@ -4,8 +4,8 @@ Put each substantial scene in its own component and file.
Register those components as [connected compositions](connected-compositions.md) so each scene has an editable Studio timeline.
Treat the parent timeline as an editable document: Author every scene that
-should be edited independently as a separate interactive component,
-`<Series.Sequence>`, or `<TransitionSeries.Sequence>` JSX node. Keep its `name` and
+should be edited independently as a separate interactive component
+or `<TransitionSeries.Sequence>` JSX node. Keep its `name` and
`durationInFrames` inline so the node has its own source-editing target.
Programmatic rendering is suitable only when the generated scenes are
intentionally controlled as one source template.
@@ -103,5 +103,5 @@ Keep each scene's standalone metadata and `defaultProps` consistent with how it
With no transition, this example needs a 210-frame main composition.
If you add a transition, account for its overlap in the main duration; see [transitions](transitions.md).
-Use `<Series>` for consecutive scenes that do not need transitions.
+Use `<TransitionSeries>` for consecutive scenes that do not need transitions.
For independently placed scenes, prefer components made with `Interactive.withSchema({wrapInSequence: true})` and put `from` and `durationInFrames` directly on each instance.
diff --git a/packages/skills/skills/remotion-markup/sequencing.md b/packages/skills/skills/remotion-markup/sequencing.md
index de5fb5a986..da556121ea 100644
--- a/packages/skills/skills/remotion-markup/sequencing.md
+++ b/packages/skills/skills/remotion-markup/sequencing.md
@@ -34,7 +34,7 @@ Set `premountFor={fps}` on every timed component that supports the prop, using
`fps` from `useVideoConfig()`. This mounts it one second before its start in
Studio, allowing media and other content to prepare. Put the prop directly on
the timed component, including `<Audio>`, `<Video>`, interactive components,
-`<Sequence>`, `<Series.Sequence>`, `<TransitionSeries.Sequence>`, and
+`<Sequence>`, `<TransitionSeries.Sequence>`, and
`<TransitionSeries.Overlay>`:
```tsx
@@ -46,7 +46,7 @@ parent starts. The composition cannot premount before frame 0.
## TransitionSeries
-Use `<TransitionSeries>` for consecutive scenes that may need transitions. Without a transition, the scenes play without overlap. Use `<Series>` from `remotion` when transitions are not needed.
+Use `<TransitionSeries>` for consecutive scenes, with or without transitions. Without a transition, the scenes play without overlap.
```tsx
import { TransitionSeries } from "@remotion/transitions";
diff --git a/packages/skills/skills/remotion-markup/video-editing.md b/packages/skills/skills/remotion-markup/video-editing.md
index 36aa1f2e28..b88ba94e2c 100644
--- a/packages/skills/skills/remotion-markup/video-editing.md
+++ b/packages/skills/skills/remotion-markup/video-editing.md
@@ -15,10 +15,9 @@ Choose the timeline structure based on the editing behavior:
- Use independently positioned clips when moving or resizing one clip should
not affect any other clip.
-- Use `<Series>` for consecutive clips when changing one clip's duration should
- reposition every later clip.
-- Use `<TransitionSeries>` when consecutive clips also need transitions or
- overlays.
+- Use `<TransitionSeries>` for consecutive clips when changing one clip's
+ duration should reposition every later clip. It also supports transitions
+ and overlays.
Use `const {fps} = useVideoConfig()` in the enclosing composition and set
`premountFor={fps}` on each timed clip, sequence, and overlay that supports it.
@@ -33,7 +32,7 @@ expression when the user trims or splits it.
For a clip with synchronized captions or overlays, make a shared timing group
the editable timeline item. Keep the video and its synchronized layers inside
one `<Sequence>` for independently positioned clips, or inside the same
-`<Series.Sequence>` or `<TransitionSeries.Sequence>` for consecutive clips.
+`<TransitionSeries.Sequence>` for consecutive clips.
Put the clip's `trimBefore`, `durationInFrames`, and `playbackRate` on that
shared parent, plus `from` when using an independently positioned `<Sequence>`.
@@ -90,58 +89,59 @@ Use literal frame counts when they are already known;
Moving or resizing one of these clips does not reposition later clips. Gaps and
overlaps are therefore allowed.
-## Consecutive clips with `Series`
+## Consecutive clips with `TransitionSeries`
-Use `<Series>` when the clips should remain adjacent and do not need
-transitions. The example below has no synchronized captions; for captioned
-clips, put the captions inside each sequence and move the video's trim to
-that shared sequence as described above:
+Use `<TransitionSeries>` when the clips should remain adjacent. No transition
+components are needed for consecutive playback. The example below has no
+synchronized captions; for captioned clips, put the captions inside each
+sequence and move the video's trim to that shared sequence as described above:
```tsx
-<Series>
- <Series.Sequence name="Opening" durationInFrames={78} premountFor={fps}>
+import { TransitionSeries } from "@remotion/transitions";
+
+<TransitionSeries>
+ <TransitionSeries.Sequence name="Opening" durationInFrames={78} premountFor={fps}>
<Video
src="https://remotion.media/video.mp4"
trimBefore={0}
premountFor={fps}
/>
- </Series.Sequence>
- <Series.Sequence name="Interview" durationInFrames={66} premountFor={fps}>
+ </TransitionSeries.Sequence>
+ <TransitionSeries.Sequence name="Interview" durationInFrames={66} premountFor={fps}>
<Video
src="https://remotion.media/video.webm"
trimBefore={12}
premountFor={fps}
/>
- </Series.Sequence>
- <Series.Sequence name="Closing" durationInFrames={90} premountFor={fps}>
+ </TransitionSeries.Sequence>
+ <TransitionSeries.Sequence name="Closing" durationInFrames={90} premountFor={fps}>
<Video
src="https://remotion.media/video.mp4"
trimBefore={72}
premountFor={fps}
/>
- </Series.Sequence>
-</Series>
+ </TransitionSeries.Sequence>
+</TransitionSeries>
```
-The `<Series.Sequence>` is the editable clip row. Changing its
+The `<TransitionSeries.Sequence>` is the editable clip row. Changing its
`durationInFrames` repositions every later sequence. Do not set `from` on a
-`<Series.Sequence>`; the series calculates each start frame.
+`<TransitionSeries.Sequence>`; the series calculates each start frame.
Keep every sequence as a separate JSX node with a hardcoded `name` and
`durationInFrames`. The child may also be a custom clip or scene component:
```tsx
-<Series.Sequence name="Product demo" durationInFrames={150} premountFor={fps}>
+<TransitionSeries.Sequence name="Product demo" durationInFrames={150} premountFor={fps}>
<ProductDemo />
-</Series.Sequence>
+</TransitionSeries.Sequence>
```
## Consecutive clips with transitions
Use `<TransitionSeries>` when the timeline needs transitions or overlays.
-Preserve the same one-source-node-per-clip structure. As with `<Series>`, put
-a clip's synchronized captions inside its sequence and apply shared timing
-to that parent:
+Preserve the same one-source-node-per-clip structure. Put a clip's synchronized
+captions inside its sequence and apply shared timing to that parent:
```tsx
<TransitionSeries name="Video timeline">
diff --git a/packages/template-prompt-to-motion-graphics/README.md b/packages/template-prompt-to-motion-graphics/README.md
index 6449ffadf5..10bc45c19a 100644
--- a/packages/template-prompt-to-motion-graphics/README.md
+++ b/packages/template-prompt-to-motion-graphics/README.md
@@ -63,7 +63,7 @@ Skills enable contextual expertise without bloating every prompt. Located in `sr
| **typography** | Kinetic text - typewriter effects, word carousels, text highlights |
| **messaging** | Chat UI - bubble layouts, WhatsApp/iMessage styling, staggered entrances |
| **transitions** | Scene changes - TransitionSeries, fade/slide/wipe effects |
-| **sequencing** | Timing control - Sequence, Series, staggered delays |
+| **sequencing** | Timing control - Sequence, TransitionSeries, staggered delays |
| **spring-physics** | Organic motion - spring configs, bounce effects, chained animations |
| **social-media** | Platform-specific formats - aspect ratios, safe zones |
| **3d** | Three.js integration - 3D scenes, camera setup |
diff --git a/packages/template-prompt-to-motion-graphics/src/skills/sequencing.md b/packages/template-prompt-to-motion-graphics/src/skills/sequencing.md
index 1543f97f69..89a9038609 100644
--- a/packages/template-prompt-to-motion-graphics/src/skills/sequencing.md
+++ b/packages/template-prompt-to-motion-graphics/src/skills/sequencing.md
@@ -33,40 +33,40 @@ import { Sequence } from "remotion";
</Sequence>
```
-## Series for Sequential Playback
+## TransitionSeries for Sequential Playback
-Use Series when elements should play one after another without overlap.
+Use TransitionSeries when elements should play one after another without overlap.
```tsx
-import { Series } from "remotion";
+import { TransitionSeries } from "@remotion/transitions";
-<Series>
- <Series.Sequence durationInFrames={45}>
+<TransitionSeries>
+ <TransitionSeries.Sequence durationInFrames={45}>
<Intro />
- </Series.Sequence>
- <Series.Sequence durationInFrames={60}>
+ </TransitionSeries.Sequence>
+ <TransitionSeries.Sequence durationInFrames={60}>
<MainContent />
- </Series.Sequence>
- <Series.Sequence durationInFrames={30}>
+ </TransitionSeries.Sequence>
+ <TransitionSeries.Sequence durationInFrames={30}>
<Outro />
- </Series.Sequence>
-</Series>;
+ </TransitionSeries.Sequence>
+</TransitionSeries>;
```
-## Series with Offset for Overlap
+## TransitionSeries with Offset for Overlap
Use negative offset for overlapping sequences:
```tsx
-<Series>
- <Series.Sequence durationInFrames={60}>
+<TransitionSeries>
+ <TransitionSeries.Sequence durationInFrames={60}>
<SceneA />
- </Series.Sequence>
- <Series.Sequence offset={-15} durationInFrames={60}>
+ </TransitionSeries.Sequence>
+ <TransitionSeries.Sequence offset={-15} durationInFrames={60}>
{/* Starts 15 frames before SceneA ends */}
<SceneB />
- </Series.Sequence>
-</Series>
+ </TransitionSeries.Sequence>
+</TransitionSeries>
```
## Staggered Element Entrances