https://mhbxyz.github.io/en/tags/video/Recent content in Video on mhbxyz.meHugoenMon, 19 Oct 2026 00:00:00 +0000https://mhbxyz.github.io/en/articles/openwatchparty-synchronize-playback-despite-latency/Mon, 19 Oct 2026 00:00:00 +0000https://mhbxyz.github.io/en/articles/openwatchparty-synchronize-playback-despite-latency/<p>In my <a href="https://mhbxyz.github.io/en/articles/openwatchparty-synchronized-watch-parties-for-jellyfin/">first OpenWatchParty article</a>, I introduced the Jellyfin plugin and its Rust session server. The harder question remained: how do you make the same scene play at the same time on several machines when their clocks, networks, and players behave differently?</p> <h2 id="establish-a-shared-clock">Establish a shared clock</h2> <p>The server cannot assume that two computers display the same time. The client therefore sends a timestamped ping. When the response arrives, it measures the round-trip time and estimates the offset between its clock and the server&rsquo;s. Several measurements are smoothed so that a latency spike does not cause a sudden jump.</p>https://mhbxyz.github.io/en/articles/remotion-agent-starter-video-editing-with-a-manifest/Fri, 07 Aug 2026 00:00:00 +0000https://mhbxyz.github.io/en/articles/remotion-agent-starter-video-editing-with-a-manifest/<h2 id="an-edit-you-can-review">An edit you can review</h2> <p>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 <a href="https://github.com/mhbxyz/remotion-agent-starter">Remotion Agent Starter</a>, I wanted to put routine editorial decisions in a JSON manifest that can be read, checked, and versioned.</p> <p>The manifest describes scenes, durations, media, and transitions. React and Remotion handle rendering. The separation is simple: data says <strong>what</strong> to edit; components decide <strong>how</strong> each frame looks.</p>