Skip to content

πŸŽ₯ Make videos programmatically with React

Skills: Premount timed items and select scenes on canvas

Jonny Burgerdc7cdeecee88
diff --git a/packages/skills/skills/remotion-interactivity/SKILL.md b/packages/skills/skills/remotion-interactivity/SKILL.md
index 1c2935c017..cbf5c7318e 100644
--- a/packages/skills/skills/remotion-interactivity/SKILL.md
+++ b/packages/skills/skills/remotion-interactivity/SKILL.md
@@ -98,22 +98,22 @@ Each key in the schema is a prop that Studio can read and edit at the call site.
Props that are not in the schema still work, but are not editable in Studio.
Keys may use dot notation, such as `style.color`.
-| Type | Use for | Keyframable |
-| --- | --- | --- |
-| `text-content` | Text, such as a title | No |
-| `number` | Numbers, with optional `min`, `max`, `step`, `integer` | Yes |
-| `boolean` | On/off switches | Yes (hold) |
-| `color` | CSS color strings | Yes |
-| `enum` | A choice between `variants`, each with its own nested schema | Opt-in (hold) |
-| `array` | Lists of numbers, colors, enums and more | No |
-| `asset` | Media sources, with optional `assetType` | No |
-| `font-family` | CSS font family | No |
-| `font-weight` | Font weight | Yes |
-| `translate`, `scale`, `rotation-css`, `rotation-degrees`, `transform-origin` | Transforms | Yes |
-| `uv-coordinate` | A normalized `[x, y]` point on the element | Yes |
-| `svg-path` | SVG path data | Yes |
-| `remotion-captions` | `Caption[]` data | No |
-| `hidden` | A value kept out of the controls | β€” |
+| Type | Use for | Keyframable |
+| ---------------------------------------------------------------------------- | ------------------------------------------------------------ | ------------- |
+| `text-content` | Text, such as a title | No |
+| `number` | Numbers, with optional `min`, `max`, `step`, `integer` | Yes |
+| `boolean` | On/off switches | Yes (hold) |
+| `color` | CSS color strings | Yes |
+| `enum` | A choice between `variants`, each with its own nested schema | Opt-in (hold) |
+| `array` | Lists of numbers, colors, enums and more | No |
+| `asset` | Media sources, with optional `assetType` | No |
+| `font-family` | CSS font family | No |
+| `font-weight` | Font weight | Yes |
+| `translate`, `scale`, `rotation-css`, `rotation-degrees`, `transform-origin` | Transforms | Yes |
+| `uv-coordinate` | A normalized `[x, y]` point on the element | Yes |
+| `svg-path` | SVG path data | Yes |
+| `remotion-captions` | `Caption[]` data | No |
+| `hidden` | A value kept out of the controls | β€” |
Every field needs a `default` and should have a `description`, which Studio shows as the label.
Set `keyframable: false` to show a static control.
@@ -201,6 +201,13 @@ handle timing. Keep `<Series.Sequence>` for consecutive layout and
`<TransitionSeries.Sequence>` for transitions; direct `from` props do not
replace those behaviors.
+When an outer `<TransitionSeries>` only organizes full-frame scenes, set
+`showInTimeline={false}` on that parent. Studio puts a full-frame parent outline
+above an unselected child with the same hit area, so clicking the canvas would
+otherwise select the container instead of the active scene sequence. Hiding
+the parent row removes its canvas outline while keeping child sequences
+visible and selectable in the timeline.
+
## Give every independently editable item its own JSX node
The Studio edits the JSX source node that created an item. If multiple runtime
diff --git a/packages/skills/skills/remotion-markup/SKILL.md b/packages/skills/skills/remotion-markup/SKILL.md
index b9192940f6..a331185fa1 100644
--- a/packages/skills/skills/remotion-markup/SKILL.md
+++ b/packages/skills/skills/remotion-markup/SKILL.md
@@ -24,21 +24,35 @@ Use `Easing.bezier()` and `Easing.spring()` to customize timing.
Structure your markup according to [Remotion Interactivity Best Practices](../remotion-interactivity/SKILL.md).
Prefer `Interactive.withSchema({wrapInSequence: true})` for custom visual components
with editable props, and register reusable scenes as connected compositions.
+For a multi-scene video, set `showInTimeline={false}` on the structural
+`<TransitionSeries>` parent when its child sequences should be selected by
+clicking the canvas. The child sequences remain visible and selectable in the
+timeline. See [Multi-scene videos](multi-scene-video.md).
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
+when a nested item needs to mount before the parent starts. A component without
+`premountFor`, such as `<TransitionSeries.Transition>`, needs no substitute.
+See [Premounting](sequencing.md#premounting) for the `layout="none"` constraint.
The Studio edits the JSX source node that created an item. Author every composition registration, clip, scene, layer and sequence that should be editable independently as its own JSX node, with its editable props inline.
Programmatic loops are suitable when the generated instances are intentionally controlled as one source template, not when users need to edit the instances
separately.
```tsx
-import { useCurrentFrame, Easing, interpolate, Interactive } from "remotion";
+import { useCurrentFrame, useVideoConfig, Easing, interpolate, Interactive } from "remotion";
export const FadeIn = () => {
const frame = useCurrentFrame();
+ const {fps} = useVideoConfig();
return (
<Interactive.Div
name="Title"
+ premountFor={fps}
style={{
opacity: interpolate(frame, [0, 2 * fps], [0, 1], {
extrapolateRight: "clamp",
@@ -99,19 +113,22 @@ Use `staticFile()` for files in `public/` or pass a remote URL directly:
```tsx
import { Audio, Video } from "@remotion/media";
-import { staticFile, CanvasImage, AnimatedImage } from "remotion";
+import { staticFile, CanvasImage, AnimatedImage, useVideoConfig } from "remotion";
export const MyComposition = () => {
+ const {fps} = useVideoConfig();
+
return (
<>
- <Video src={staticFile("video.mp4")} style={{ opacity: 0.5 }} />
- <Audio src={staticFile("audio.mp3")} />
+ <Video src={staticFile("video.mp4")} premountFor={fps} style={{ opacity: 0.5 }} />
+ <Audio src={staticFile("audio.mp3")} premountFor={fps} />
<CanvasImage
src={staticFile("logo.png")}
+ premountFor={fps}
style={{ width: 100, height: 100 }}
/>
- <Video src="https://remotion.media/video.mp4" />
- <AnimatedImage src={staticFile('nyancat.gif')} />
+ <Video src="https://remotion.media/video.mp4" premountFor={fps} />
+ <AnimatedImage src={staticFile('nyancat.gif')} premountFor={fps} />
</>
);
};
@@ -142,6 +159,7 @@ export const MyScene = () => {
<Video
name="Background"
src="https://remotion.media/video.mp4"
+ premountFor={fps}
objectFit="cover"
style={{
position: "absolute",
@@ -152,6 +170,7 @@ export const MyScene = () => {
<LowerThird
name="Lower third"
from={1 * fps}
+ premountFor={fps}
accentColor="#0b84f3"
style={{
opacity: interpolate(frame, [1 * fps, 2 * fps], [0, 1], {
@@ -271,6 +290,10 @@ export const RemotionRoot: React.FC = () => {
The following timing props are supported by built-in components (`<AbsoluteFill>`, `<Interactive.*>`, `<Img>`, `<AnimatedImage>`, `<CanvasImage>`, `<HtmlInCanvas>`, `<Solid>`, `<Sequence>` from `remotion`, `<Video>` and `<Audio>` from `@remotion/media`, `<Gif>`, and more).
Custom components made with `Interactive.withSchema({wrapInSequence: true})` accept them too, see [Prefer interactive components with their own timelines](../remotion-interactivity/SKILL.md#prefer-interactive-components-with-their-own-timelines).
+Set `premountFor={fps}` on these timed items when they support it, including
+items starting at frame 0. At frame 0, the composition has no earlier frames
+to premount into; the prop still keeps the same one-second default if the item
+is moved later.
### `from`
@@ -331,7 +354,13 @@ Other items need `durationInFrames` to define the loop range:
<Interactive.Div durationInFrames={2 * fps} loop {/* ... */} />
```
-To limit the total length of a loop, wrap it in an outer item with `durationInFrames`.
+Put timing and volume directly on `<Audio>` rather than wrapping one audio
+track in a `<Sequence>`. If a looping track's volume is clamped to zero after
+its intended end, a direct `<Audio>` needs no outer sequence; its silent tail
+remains in the timeline until the parent ends. With `loop`, `durationInFrames`
+sets the range to repeat, not the total clip length. Use an outer timed item
+only when the looping clip itself must end at an exact frame. A non-looping
+`<Audio>` can take `from` and `durationInFrames` directly.
`<Img>`, `<CanvasImage>`, `<Solid>` and shapes do not support `loop` because their output does not change over time.
diff --git a/packages/skills/skills/remotion-markup/audio.md b/packages/skills/skills/remotion-markup/audio.md
index 42e9450fed..f2b6773e28 100644
--- a/packages/skills/skills/remotion-markup/audio.md
+++ b/packages/skills/skills/remotion-markup/audio.md
@@ -145,9 +145,19 @@ Reverse playback is not supported.
Use `loop` to loop the audio indefinitely:
```tsx
-<Audio src={staticFile("audio.mp3")} loop />
+<Audio src={staticFile("audio.mp3")} loop premountFor={fps} />
```
+Put `name`, `from`, `loop`, `volume`, and `premountFor` directly on `<Audio>`.
+For a looping music bed whose volume fades to zero and stays there, this
+avoids an extra sequence while producing the intended audible end. The silent
+audio remains in the timeline until its parent ends.
+
+With `loop`, `durationInFrames` on `<Audio>` selects the range to repeat; it
+does not set the total playback length. Use an outer timed item only when the
+looping clip itself must end at an exact frame. For audio that does not loop,
+put `durationInFrames` directly on `<Audio>` to cap it.
+
Use `loopVolumeCurveBehavior` to control how the frame count behaves when looping:
- `"repeat"`: Frame count resets to 0 each loop (default)
diff --git a/packages/skills/skills/remotion-markup/multi-scene-video.md b/packages/skills/skills/remotion-markup/multi-scene-video.md
index 2e6aae4707..b6df1f90d5 100644
--- a/packages/skills/skills/remotion-markup/multi-scene-video.md
+++ b/packages/skills/skills/remotion-markup/multi-scene-video.md
@@ -13,31 +13,43 @@ intentionally controlled as one source template.
Use `<TransitionSeries>` when the scenes may have transitions.
Install `@remotion/transitions` if it is missing.
Give each sequence an inline `durationInFrames` value so Studio can edit its timing.
+Set `showInTimeline={false}` on the outer `<TransitionSeries>` when it is only
+a structural container. Otherwise its full-frame canvas outline competes with
+the active scene's full-frame outline and may receive clicks. This hides only
+the container row; the scene sequences remain in the timeline and selectable
+on the canvas.
Example:
```tsx
// MyVideo.tsx
import {TransitionSeries} from '@remotion/transitions';
+import {useVideoConfig} from 'remotion';
import {OpeningScene} from './OpeningScene';
import {FeatureScene} from './FeatureScene';
-export const MyVideo = () => (
- <TransitionSeries>
- <TransitionSeries.Sequence
- name="Opening"
- durationInFrames={90}
- >
- <OpeningScene />
- </TransitionSeries.Sequence>
- <TransitionSeries.Sequence
- name="Feature"
- durationInFrames={120}
- >
- <FeatureScene />
- </TransitionSeries.Sequence>
- </TransitionSeries>
-);
+export const MyVideo = () => {
+ const {fps} = useVideoConfig();
+
+ return (
+ <TransitionSeries showInTimeline={false}>
+ <TransitionSeries.Sequence
+ name="Opening"
+ durationInFrames={90}
+ premountFor={fps}
+ >
+ <OpeningScene />
+ </TransitionSeries.Sequence>
+ <TransitionSeries.Sequence
+ name="Feature"
+ durationInFrames={120}
+ premountFor={fps}
+ >
+ <FeatureScene />
+ </TransitionSeries.Sequence>
+ </TransitionSeries>
+ );
+};
```
Register the same scene components, plus the parent video, in the root:
diff --git a/packages/skills/skills/remotion-markup/sequencing.md b/packages/skills/skills/remotion-markup/sequencing.md
index 74e080ad63..3b4551ff55 100644
--- a/packages/skills/skills/remotion-markup/sequencing.md
+++ b/packages/skills/skills/remotion-markup/sequencing.md
@@ -8,6 +8,8 @@ metadata:
Prefer timing props directly on built-in interactive components and custom
components made with `Interactive.withSchema({wrapInSequence: true})`.
Avoid wrapping a single timing-capable component in a redundant `<Sequence>`.
+Put `name`, `from`, `durationInFrames`, `loop`, `volume`, and `premountFor`
+directly on `<Audio>` whenever their combination gives the intended timing.
See [Remotion Interactivity](../remotion-interactivity/SKILL.md) for creating
schema-wrapped components and [connected compositions](connected-compositions.md)
@@ -16,8 +18,8 @@ for registering them with their own Studio timelines.
```tsx
// Title and Subtitle are exported with Interactive.withSchema({wrapInSequence: true}).
<>
- <Title name="Title" from={30} durationInFrames={60} />
- <Subtitle name="Subtitle" from={60} durationInFrames={60} />
+ <Title name="Title" from={30} durationInFrames={60} premountFor={fps} />
+ <Subtitle name="Subtitle" from={60} durationInFrames={60} premountFor={fps} />
</>
```
@@ -28,14 +30,46 @@ use `layout="none"` when no layout wrapper is needed.
## Premounting
-Use `premountFor` when media or expensive content needs preparation before it
-becomes visible. Pass it directly to a timing-capable component:
+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
+`<TransitionSeries.Overlay>`:
```tsx
-<Title from={60} durationInFrames={90} premountFor={30} />
+<Title from={60} durationInFrames={90} premountFor={fps} />
```
-Note that parent sequences may also need premounting, otherwise there is no effect.
+Premount parent timeline items as well when a nested item must mount before the
+parent starts. The composition cannot premount before frame 0.
+
+`<Sequence layout="none">` cannot use `premountFor`. If it only wraps one
+timing-capable component, remove the wrapper and put its timing and
+`premountFor={fps}` directly on that component. Otherwise, use the default
+sequence layout so the parent can premount.
+
+For example, time a music bed directly on `<Audio>`:
+
+```tsx
+<Audio
+ name="Music bed"
+ src={staticFile("music.mp3")}
+ from={392}
+ loop
+ premountFor={fps}
+ volume={interpolate(frame, [392, 420, 6150, 6158], [0, 0.14, 0.14, 0], {
+ extrapolateLeft: "clamp",
+ extrapolateRight: "clamp",
+ })}
+/>
+```
+
+Here the volume reaches zero at frame 6158 and stays there. Omit
+`durationInFrames`: with `loop`, it sets the range to repeat rather than the
+total clip length. The silent audio remains in the timeline until the parent
+ends. Use an outer timed item only when the looping clip itself must end at an
+exact frame.
## TransitionSeries
@@ -44,14 +78,14 @@ Use `<TransitionSeries>` for consecutive scenes that may need transitions. Witho
```tsx
import { TransitionSeries } from "@remotion/transitions";
-<TransitionSeries>
- <TransitionSeries.Sequence durationInFrames={45}>
+<TransitionSeries showInTimeline={false}>
+ <TransitionSeries.Sequence durationInFrames={45} premountFor={fps}>
<Intro />
</TransitionSeries.Sequence>
- <TransitionSeries.Sequence durationInFrames={60}>
+ <TransitionSeries.Sequence durationInFrames={60} premountFor={fps}>
<MainContent />
</TransitionSeries.Sequence>
- <TransitionSeries.Sequence durationInFrames={30}>
+ <TransitionSeries.Sequence durationInFrames={30} premountFor={fps}>
<Outro />
</TransitionSeries.Sequence>
</TransitionSeries>;
diff --git a/packages/skills/skills/remotion-markup/transitions.md b/packages/skills/skills/remotion-markup/transitions.md
index a2630d39e5..f240423f89 100644
--- a/packages/skills/skills/remotion-markup/transitions.md
+++ b/packages/skills/skills/remotion-markup/transitions.md
@@ -12,6 +12,15 @@ metadata:
- **Transitions** (`<TransitionSeries.Transition>`) β€” crossfade, slide, wipe, etc. between two scenes. Shortens the timeline because both scenes play simultaneously during the transition.
- **Overlays** (`<TransitionSeries.Overlay>`) β€” render an effect (e.g. a light leak) on top of the cut point without shortening the timeline.
+Set `premountFor={fps}` on every `<TransitionSeries.Sequence>` and
+`<TransitionSeries.Overlay>`, using `fps` from `useVideoConfig()`. Premount
+timed children inside those items as well. `<TransitionSeries.Transition>`
+does not accept `premountFor`.
+
+For a multi-scene timeline, set `showInTimeline={false}` on the outer
+`<TransitionSeries>` so clicking a full-frame scene selects its sequence
+instead of the full-frame container. The child sequence rows stay visible.
+
Children are absolutely positioned.
## Prerequisites
@@ -26,15 +35,15 @@ npx remotion add @remotion/transitions
import { TransitionSeries, linearTiming } from "@remotion/transitions";
import { fade } from "@remotion/transitions/fade";
-<TransitionSeries>
- <TransitionSeries.Sequence durationInFrames={60}>
+<TransitionSeries showInTimeline={false}>
+ <TransitionSeries.Sequence durationInFrames={60} premountFor={fps}>
<SceneA />
</TransitionSeries.Sequence>
<TransitionSeries.Transition
presentation={fade()}
timing={linearTiming({ durationInFrames: 15 })}
/>
- <TransitionSeries.Sequence durationInFrames={60}>
+ <TransitionSeries.Sequence durationInFrames={60} premountFor={fps}>
<SceneB />
</TransitionSeries.Sequence>
</TransitionSeries>;
@@ -51,12 +60,13 @@ import {interpolate, Solid, useCurrentFrame, useVideoConfig} from 'remotion';
const LightLeakOverlay: React.FC = () => {
const frame = useCurrentFrame();
- const {durationInFrames, height, width} = useVideoConfig();
+ const {durationInFrames, fps, height, width} = useVideoConfig();
return (
<Solid
width={width}
height={height}
+ premountFor={fps}
effects={[
lightLeak({
progress: interpolate(frame, [0, durationInFrames - 1], [0, 1], {
@@ -69,14 +79,14 @@ const LightLeakOverlay: React.FC = () => {
);
};
-<TransitionSeries>
- <TransitionSeries.Sequence durationInFrames={60}>
+<TransitionSeries showInTimeline={false}>
+ <TransitionSeries.Sequence durationInFrames={60} premountFor={fps}>
<SceneA />
</TransitionSeries.Sequence>
- <TransitionSeries.Overlay durationInFrames={20}>
+ <TransitionSeries.Overlay durationInFrames={20} premountFor={fps}>
<LightLeakOverlay />
</TransitionSeries.Overlay>
- <TransitionSeries.Sequence durationInFrames={60}>
+ <TransitionSeries.Sequence durationInFrames={60} premountFor={fps}>
<SceneB />
</TransitionSeries.Sequence>
</TransitionSeries>;
@@ -94,12 +104,13 @@ import {interpolate, Solid, useCurrentFrame, useVideoConfig} from 'remotion';
const LightLeakOverlay: React.FC = () => {
const frame = useCurrentFrame();
- const {durationInFrames, height, width} = useVideoConfig();
+ const {durationInFrames, fps, height, width} = useVideoConfig();
return (
<Solid
width={width}
height={height}
+ premountFor={fps}
effects={[
lightLeak({
progress: interpolate(frame, [0, durationInFrames - 1], [0, 1], {
@@ -112,21 +123,21 @@ const LightLeakOverlay: React.FC = () => {
);
};
-<TransitionSeries>
- <TransitionSeries.Sequence durationInFrames={60}>
+<TransitionSeries showInTimeline={false}>
+ <TransitionSeries.Sequence durationInFrames={60} premountFor={fps}>
<SceneA />
</TransitionSeries.Sequence>
- <TransitionSeries.Overlay durationInFrames={30}>
+ <TransitionSeries.Overlay durationInFrames={30} premountFor={fps}>
<LightLeakOverlay />
</TransitionSeries.Overlay>
- <TransitionSeries.Sequence durationInFrames={60}>
+ <TransitionSeries.Sequence durationInFrames={60} premountFor={fps}>
<SceneB />
</TransitionSeries.Sequence>
<TransitionSeries.Transition
presentation={fade()}
timing={linearTiming({ durationInFrames: 15 })}
/>
- <TransitionSeries.Sequence durationInFrames={60}>
+ <TransitionSeries.Sequence durationInFrames={60} premountFor={fps}>
<SceneC />
</TransitionSeries.Sequence>
</TransitionSeries>;
@@ -145,6 +156,7 @@ const LightLeakOverlay: React.FC = () => {
- `durationInFrames` β€” how long the overlay is visible (positive integer).
- `offset?` β€” shifts the overlay relative to the cut point center. Positive = later, negative = earlier. Default: `0`.
+- `premountFor` β€” set to `fps` for one second of premounting.
## Available transition types
diff --git a/packages/skills/skills/remotion-markup/video-editing.md b/packages/skills/skills/remotion-markup/video-editing.md
index 2e029a778d..d43ed62cde 100644
--- a/packages/skills/skills/remotion-markup/video-editing.md
+++ b/packages/skills/skills/remotion-markup/video-editing.md
@@ -20,6 +20,10 @@ Choose the timeline structure based on the editing behavior:
- Use `<TransitionSeries>` when consecutive clips also need transitions or
overlays.
+Use `const {fps} = useVideoConfig()` in the enclosing composition and set
+`premountFor={fps}` on each timed clip, sequence, and overlay that supports it.
+When a clip is inside a series sequence, premount both the sequence and clip.
+
## Independently positioned clips
Place every `<Video>` directly in the composition and hardcode its timing
@@ -31,6 +35,7 @@ props. `from={0}` may be omitted:
src="https://remotion.media/video.mp4"
trimBefore={0}
durationInFrames={78}
+ premountFor={fps}
/>
<Video
name="Interview"
@@ -38,6 +43,7 @@ props. `from={0}` may be omitted:
trimBefore={12}
from={78}
durationInFrames={66}
+ premountFor={fps}
/>
<Video
name="Closing"
@@ -45,6 +51,7 @@ props. `from={0}` may be omitted:
trimBefore={72}
from={144}
durationInFrames={90}
+ premountFor={fps}
/>
```
@@ -64,22 +71,25 @@ transitions:
```tsx
<Series>
- <Series.Sequence name="Opening" durationInFrames={78}>
+ <Series.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}>
+ <Series.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}>
+ <Series.Sequence name="Closing" durationInFrames={90} premountFor={fps}>
<Video
src="https://remotion.media/video.mp4"
trimBefore={72}
+ premountFor={fps}
/>
</Series.Sequence>
</Series>
@@ -93,7 +103,7 @@ 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}>
+<Series.Sequence name="Product demo" durationInFrames={150} premountFor={fps}>
<ProductDemo />
</Series.Sequence>
```
@@ -104,21 +114,23 @@ Use `<TransitionSeries>` when the timeline needs transitions or overlays.
Preserve the same one-source-node-per-clip structure:
```tsx
-<TransitionSeries name="Video timeline">
- <TransitionSeries.Sequence name="Opening" durationInFrames={78}>
+<TransitionSeries name="Video timeline" showInTimeline={false}>
+ <TransitionSeries.Sequence name="Opening" durationInFrames={78} premountFor={fps}>
<Video
src="https://remotion.media/video.mp4"
trimBefore={0}
+ premountFor={fps}
/>
</TransitionSeries.Sequence>
<TransitionSeries.Transition
presentation={fade()}
timing={linearTiming({durationInFrames: 12})}
/>
- <TransitionSeries.Sequence name="Interview" durationInFrames={66}>
+ <TransitionSeries.Sequence name="Interview" durationInFrames={66} premountFor={fps}>
<Video
src="https://remotion.media/video.webm"
trimBefore={12}
+ premountFor={fps}
/>
</TransitionSeries.Sequence>
</TransitionSeries>