Guide implementation and debugging of visual Sequence editing in Remotion Studio. It documents how sequence identifiers, node paths, and stack traces behave during hot reload, and suggests how to track expanded UI state.
Guidance for working on Remotion Studio Visual Mode, sequence identity, node paths, symbolicated stacks, override IDs, and hot reload behavior. Use when implementing or debugging visual editing of Sequences.
Review the instructions the agent will receive before you install.
Visual Mode is a feature in Remotion Studio that allows one to visually edit Sequences.
I've made the following observations:
stack -> changes on hot reload. shared by multiple sequences which have different overrideIdsnodePath -> same identity, even if line, stack and overrideId changes. asyncnodePath + index is ideal way to keep track of the expanded state. that’s the end goal.
Once nodePath is mapped to overrideId, it doesn’t change otherwise component would remount and overrideId works change.
If the same stack is found already used by another sequence, we re-use the overrideId.
nodePath to symbolicated stack could theoretically change on every file change. but multiple sequences can share the same stack and then they all have the same nodePath.
We should only fetch the nodepath for every stack once
different unsymbolicated stacks could lead to the same symbolicated stack, because of fast refresh
unsymbolicated to symbolicated stack does never change because if it does, it is a different stack due to fast refresh
Whenever adding a new Studio API route, also add it to the Browser Studio parity checklist in issue #9807. Do this in the same change, even if the route is intentionally server-only; place it in either the required Browser Studio operations or the explicitly unsupported routes.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add a reported Remotion bug to the bugs API with its affected versions, a short title, and upgrade guidance. Follow the existing entry format and place the new record first so recent bugs appear at the top.
Add a Remotion command-line or configuration option, or convert a hardcoded flag into a shared option definition. Connect parsing, configuration setters, help entries, and generated documentation so the option is consistently available and documented.
Add a new effect to @remotion/effects, including its implementation, package entry points, documentation, interactive demo, and preview images. Follow the package conventions and verify the changes with tests, formatting checks, and builds.
Add a person to the Remotion experts page by placing their portrait, entering their profile and contact links, and generating an expert card image. The instructions specify file locations, profile fields, and how to verify card generation.
Create a new @remotion package within the Remotion monorepo, a repository containing multiple packages. Set up its files, register it across the project, and prepare documentation, usage examples, and build configuration.
Add a new sound effect to @remotion/sfx, from registering the audio file to exporting its URL and documenting its use. The workflow covers playback examples, attribution, navigation entries, waveform generation, and the package build.