20 Open-Source Motion Repositories Are Just the Start—What’s Really Scarce Is a System That Can Repeatedly Ship Finished Videos

eigen posted a list of 20 open-source repositories covering motion, 3D, audio, and rendering. It came with a demo video that looks decent. Saving it is fast; shipping is slow. The truly hard part comes after the list.

These repositories are described as open-source skills for Opus 5.5. More accurately, they are a composable toolbox. Motion, Simulation, Shaders, Audio, and Export each handle one segment. Stuff all 20 into one project, and you’ll usually just end up with an engineering mess that’s hard to maintain.

What’s really worth looking at is the approach in the article eigen referenced. The model doesn’t generate pixels directly; it writes code, and the code draws the frames one by one. A seek(t) function calculates the current state from the timestamp. A 25-second video at 30 FPS has 750 frames, and the renderer can jump directly to frame 600 without first running through the previous 599 frames. Change the text, change the color, change the pacing—no need to regenerate the entire video.

This and common AI video models are two different production models. One outputs a video file; the other outputs an editable animation. For ordinary users, the difference may just be how fast you can change the text. For developers and teams, the difference is whether you can do QA, whether you can batch-produce, and whether you can sell the same template to different clients.

The article’s author breaks the system into six parts: Brief Compiler turns client information into structured data, Scene Engine turns data into animation instructions, Renderer outputs frames, Quality Controller finds issues, Variant Generator generates hooks, aspect ratios, and CTAs, and Delivery System packages and delivers. The core principle is simple: keep brand data and animation code separate. Change the client, change the copy, change the CTA—without rewriting the engine.

The tool list can be viewed by responsibility; you don’t have to use all of them.

Video and Motion:

01 Remotion, a React video engine. https://github.com/remotion-dev/remotion
02 Anime.js, timelines, easing, and orchestration. https://github.com/juliangarnier/anime
03 Glaxnimate, vector animation and keyframes. https://github.com/KDE/glaxnimate
04 Curtains.js, shader-driven image and video distortion. https://github.com/martinlaxenaire/curtainsjs
05 VFX-JS, glitch, bloom, and pixel effects. https://github.com/fand/vfx-js

3D, Physics, and Materials:

06 Three.js, 3D scenes, lighting, and cameras. https://github.com/mrdoob/three.js
07 Blender, modeling, rigging, and cinematic rendering. https://github.com/blender/blender
08 UIKit, build interfaces inside 3D scenes. https://github.com/pmndrs/uikit
09 GaussianSplats3D, render Gaussian splats in Three.js. https://github.com/mkkellogg/GaussianSplats3D
10 NVIDIA Warp, GPU physics simulation. https://github.com/NVIDIA/warp
11 Origami Simulator, folding geometry and paper simulation. https://github.com/amandaghassaei/OrigamiSimulator
12 MaterialX, procedural materials and shader graphs. https://github.com/AcademySoftwareFoundation/MaterialX
13 Alembic, animated geometry cache. https://github.com/alembic/alembic

Generation, Audio, and Delivery:

14 ComfyUI, node-based image and video generation. https://github.com/Comfy-Org/ComfyUI
15 LMMS, beats, synths, and scoring. https://github.com/LMMS/lmms
16 Essentia, audio and music analysis. https://github.com/MTG/essentia
17 WaveSurfer.js, interactive audio waveforms. https://github.com/katspaugh/wavesurfer.js
18 OBS Studio, screen capture and recording. https://github.com/obsproject/obs-studio
19 OpenTimelineIO, move edit timelines between different tools. https://github.com/AcademySoftwareFoundation/OpenTimelineIO
20 FFmpeg, encoding, compression, and delivery. https://github.com/FFmpeg/FFmpeg

Remotion is a relatively key link in this workflow. It renders videos with React components, so titles, product screenshots, data charts, feature reveals, logo transitions, and CTAs can be made into reusable components, and then data from different clients can be passed into the same composition. The official project also offers Agent Skills; the command is npx skills add remotion-dev/skills. The license needs to be checked separately. Remotion offers a free commercial license to eligible individuals and teams of three or fewer; larger teams and certain automation scenarios have different requirements. Check the current terms before commercialization.

QA is the part most people skip. The article’s author recommends five review rounds: storyboard, frames before and after key transitions, mobile-size preview, brand and fact checking, and the full video and audio. FFmpeg can extract frames and assemble a contact sheet, for example ffmpeg -i output.mp4 -vf "fps=1,scale=270:-1,tile=5x5" -frames:v 1 contact.png. But fixed intervals aren’t enough; you need to extract frames separately before and after transitions. There’s also a hard rule: don’t trust a model that hasn’t checked the rendered output when it says “the animation looks good.”

The “one-click finished video” narrative also doesn’t hold up under scrutiny. In the material, @mablesjoseph’s 45-second hand-drawn short—according to the creator—used 163 model calls and hours of work. @tdinh_me said a video that cost about $1,000 a year ago can now be made with Opus 5.5 in under 30 minutes. @achxvi also showed a product video completed in 45 minutes. These examples show that the output is starting to be useful; they don’t prove that everyone can immediately make money from it.

On the business side, the article’s author recommends charging by deliverable, not by number of prompts. He gives a hypothetical $750 launch package: one product, one narrative, three opening hooks, three aspect ratios, two CTAs, including MP4, cover frame, and a limited number of revision rounds. The number is an example, not a guarantee of market price. What should be tracked more is time for the first design, time per variant, rendering and API costs, number of revisions, delivery errors, and repeat purchases. A system only makes business sense if it reduces repetitive production work without sacrificing quality.

One commenter put it directly: pick three tools, do one scene a day, deliver a 30-second reel by Friday, watch completion rate, then iterate. That’s closer to the next step than bookmarking 20 repositories. A good video is a piece of work; a reusable motion engine is an asset.