blender-video-editing
Skill779 starsChanged 15 days agoMITView on GitHub
Video in Blender 5.2 - Video Sequencer edits from Python (clips, image sequences, crossfades, titles, music fades, proxies, color management, H.264/AAC output) and motion tracking (feature detection, camera solve, scene orientation, tripod and plane tracking, stabilization) for VFX shots. Use to cut renders/footage together or match-move a camera.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- blender-addon-developmentSkill
- blender-animationSkill
- blender-asset-qaSkill
- blender-character-riggingSkill
- blender-clothingSkill
- blender-coreSkill
- blender-environment-kitsSkill
- blender-export-pipelinesSkill
- blender-facial-shapekeysSkill
- blender-game-optimizationSkill
- blender-geometry-nodesSkill
- blender-hair-groomingSkill
- blender-hardsurface-modelingSkill
- blender-lighting-lookdevSkill
- blender-pbr-materialsSkill
- blender-pipeline-automationSkill
- blender-renderingSkill
- blender-retopology-uvSkill
- blender-scene-setupSkill
- blender-sculptingSkill
- blender-simulationSkill
- blender-stylized-nprSkill
- blender-texture-bakingSkill
- blender-texturingSkill
- blender-time-of-daySkill
- blender-weather-fxSkill
- blender-workflow-recipesSkill
The file
Files
Video editing and tracking
The execution model is in blender-core. Rendering the 3D shots and the compositor (5.0 API) are in blender-rendering.
One call each
scripts/vse_edit.py -- --clips //renders/sh010/ //renders/sh020/ //logo.png --crossfade 12 --title "Project" --audio //music.wav --out //edit.mp4 --render
scripts/vse_edit.py -- --clips a.mp4 b.mp4 c.mp4 --crossfade 0 --fps 24 --out //review/f_#### --render # hard cuts to PNGimport track_camera; print(track_camera.run(clip="C:/shots/sh010.mp4", focal=35, sensor=36)) # live/MCP onlyvse_edit.py
- Builds into its own
Editscene (--scene), so 3D scenes stay untouched. Clips go on alternating channels 1/2, crossfades (CROSS) on 3, the title on 4, clip audio on 6/7 (movies get their sound strip), and music on 8 (trimmed to the edit with a--audio-fadevolume fade-out). - A clip may be a movie, a still (
--still-seconds), a folder of frames, or a####pattern. Each crossfade overlaps the previous clip by--crossfadeframes, so the edit gets shorter by that much per cut. Re-running replaces the previous edit. - Sets view transform Standard: footage must pass through untouched (measured: AgX turned pure red into 0.86/0.23/0.13). Grade on purpose with strip modifiers instead.
- Output:
.mp4/.mov/.mkv= H.264 (CRF high, preset good) + AAC 192k stereo. Any other path = PNG frames. 5.0+ needsimage_settings.media_type = "VIDEO"beforefile_format = "FFMPEG". It reports the file size, and the test decodes it back (frame count, size).
Editing rules pros follow
- Match the frame rate first (
--fps= the footage/render rate). Mixed rates drift audio. Re-render or retime (SPEEDeffect) instead. - Heavy footage: build proxies (
strip.use_proxy = True, 25/50%,sequencer.rebuild_proxy). 5.2 builds only proxies (no.blen_tctimecode files anymore). - Per-strip color:
strip.colorspace_settings.name(sRGB for 8-bit video, Linear Rec.709 for EXR renders). A dedicated edit scene keeps 3D color settings out of the edit. - 5.2 API:
strips.new_movie(..., stream=N)/new_sound(stream=N)pick a stream from multi-track files.strip.connectionslists connected strips. New effect typeCOMPOSITOR(a node-tree effect). Text strips have Subtitles / Main Title / Corner Title presets in the UI. Timing usesleft_handle/right_handle/duration(5.1 names). Strip keyframes live on the scene's action.
Motion tracking (track_camera.py, live session)
- The Clip Editor operators need a window, so this borrows the largest area, runs, and restores it. In
-bit raises. It detects features at the first and last frame, tracks both ways, deletes tracks shorter thanmin_frames, solves (auto keyframes, refines focal only if unknown), deletes tracks abovemax_errorpx and re-solves, then runssetup_tracking_scene(camera + Camera Solver constraint, background footage, frame range). - Measured on a synthetic 40-frame dolly at 960×540: 56 tracks, 0.19 px solve error, 35 mm focal kept exactly. Quality bar: < 0.3 px great, < 0.5 good, > 1 px slides.
- Give
focal/sensorwhenever known. The solver is far more stable than when refining the focal. Set the sensor before the focal (focal is stored in px). - Nodal pans (camera only rotates):
tripod=True. A normal solve fails without parallax. - Orient the scene after solving (UI, Clip Editor context): select 3 floor tracks →
clip.set_plane(plane="FLOOR"), 1 track →clip.set_origin(), 2 tracks a known distance apart →clip.set_scale(distance=…). Otherwise scale and up are arbitrary. - Other jobs: screen/sign replacement →
clip.create_plane_track()on 4+ tracks of a planar surface. Shaky footage → 2D stabilization (tracking.stabilization.use_2d_stabilization, add tracks). Points for modeling →clip.bundles_to_mesh().
Shooting/footage tips that make solves work
Fast shutter (little motion blur), real parallax (move the camera, don't just pan), textured static surfaces at several depths, no rolling-shutter whip pans, and a lens grid shot to calibrate distortion when using wide lenses.
Gotchas
bpy.ops.render.render(animation=True)renders the sequencer only whenscene.render.use_sequenceris on and the strips are in the scene being rendered. The script renders its own edit scene.- Removing a clip also removes its effect strips. Collect names before deleting in loops.
- Image sequences must be contiguous. Missing frames show as black.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

