🟡 Cloud Rendering - Release RVE Cloud out of beta
Take RVE Cloud (server-side render / portal / jobs / billing) from beta to a public release.
🟣 SDK - Claude and ChatGPT Integrations
Allow developers to connect their RVE-powered editor to AI assistants such as Claude and ChatGPT. The integration should give end users the ability to edit and create videos through natural-language commands. For example, a user could ask the AI to add captions, trim a clip, change the aspect ratio, rearrange elements, or generate a new video structure. RVE should provide a standard integration layer that exposes supported editor actions and safely applies changes to the editor state. Developers should be able to choose which actions are available within their product.
🟣 SDK - some questions!
Is the timeline state programmatically accessible/mutable via `useEditorContext` (reading and writing clips/overlays in real time), or only via props/callbacks? is there an ETA or any interest in exposing an API to control the editor from an external agent?"
Zoom in and out of the Player
Context Users should be given the option to zoom in and out of the player. This will help create more detailed edits in videos.
Vertical Resize Timeline Area
The ability to resize the timeline area content. At the moment its fixed height and when you add too many tracks it takes up the entire area.
Caption Improvements
Improve the caption settings. More font option, more effects, more styles. Example:
🟣 SDK - “Text Behind Image” effects for videos and images
Implement a creative feature that allows users to place text behind subjects in both videos and images. The effect should detect the foreground (e.g., people or main objects) and render the text seamlessly behind them to create a layered, cinematic look. Example:
Can ffmpeg be used?
Boss, could remotion and ffmpeg be combined to add an additional local export function? Can they be combined in this way? It was found that the server side is a bit consuming the server
Guidance for existing projects
Hello RVE & Sam, We’ve decided to slowly migrate to RVE and I’m wondering if there’s any guidance or lessons learned from the community, sorry if this is already somewhere. My main challenges are: 1) How do I use/customize RVE Components from the private pro repo in my application, but do it in a way where its relatively straight forward to bring in changes from upcoming releases. 2) Is RVE 8 and the installable NPM packages going to support all features or is it intended as a proof-of-concept. We’re still in the planning phase, so if its worth it to wait for a fully featured npm package, that’s possible, but the post about the npm package wasn’t really clear on what will be supported. Thanks in advance! Z
Better error messages for invalid JSON
Currently this is the error message shown if there is an issue with the JSON (for example, in a template). It would be very helpful if we could see which line in the JSON caused the issue to help with debugging.
Figma File Representing RVE
Be great to get a figma file representing the design / layout of RVE.
When will version 8 be updated?
Hello, boss. I think the major version is updated every two months. When will the 8th version be updated? I'm still using the 7th version
Timeline context menu opens inconsistently
Right clicking on a timeline item doesn’t always open the shadcn context menu. Sometimes it does, sometimes it opens the native browser context menu. I’ve reproduced this issue in Chrome and Arc browser (Chromium based).
🟣 SDK - Export to Video Tools (DaVinci, Premiere, Capcut etc.)
Investigate how RVE timelines could be exported for use in other video editors such as DaVinci Resolve, Premiere Pro, or Final Cut. OTIO (OpenTimelineIO) may be one possible format, but it’s not the main focus — the goal is simply to find the most practical export method. Objectives Review different export options for interoperability between RVE and other editors. Explore what formats are most widely supported: EDL / XML (used by Premiere, Final Cut) AAF OTIO (used by DaVinci Resolve and open-source tools) Check what information each format can store (clips, start/end, media path, transitions, text, etc.). Create a small test export from an RVE project (2–3 clips) using whichever format seems simplest to start with. Try importing into at least one major editor (DaVinci, Premiere, etc.) to evaluate compatibility.
Transcript based video editor
Similar to descript, tella.tv where based on the transcript it trims/edits the video. This would be very useful feature - Generate transcript using your own api key - Show transcript with timestamp on sidebar - Ability to simply edit text and the video gets edited (with option to restore words/video)
💡 Integrate Remotion's new @remotion/media-parser package
Rewrite RVE to use the new @remotion/media-parser package. for huge performance improvements