<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Remotion on mhbxyz.me</title><link>https://mhbxyz.github.io/en/tags/remotion/</link><description>Recent content in Remotion on mhbxyz.me</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 07 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://mhbxyz.github.io/en/tags/remotion/index.xml" rel="self" type="application/rss+xml"/><item><title>Remotion Agent Starter: describe a video edit with a manifest</title><link>https://mhbxyz.github.io/en/articles/remotion-agent-starter-video-editing-with-a-manifest/</link><pubDate>Fri, 07 Aug 2026 00:00:00 +0000</pubDate><guid>https://mhbxyz.github.io/en/articles/remotion-agent-starter-video-editing-with-a-manifest/</guid><description>&lt;h2 id="an-edit-you-can-review"&gt;An edit you can review&lt;/h2&gt;
&lt;p&gt;When an edit is just a series of clicks in an interface, it is hard to tell what changed between two versions. It is harder still to ask an agent to adjust one scene without touching everything else. With &lt;a href="https://github.com/mhbxyz/remotion-agent-starter"&gt;Remotion Agent Starter&lt;/a&gt;, I wanted to put routine editorial decisions in a JSON manifest that can be read, checked, and versioned.&lt;/p&gt;
&lt;p&gt;The manifest describes scenes, durations, media, and transitions. React and Remotion handle rendering. The separation is simple: data says &lt;strong&gt;what&lt;/strong&gt; to edit; components decide &lt;strong&gt;how&lt;/strong&gt; each frame looks.&lt;/p&gt;</description></item></channel></rss>