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 PNG

import track_camera; print(track_camera.run(clip="C:/shots/sh010.mp4", focal=35, sensor=36))  # live/MCP only

vse_edit.py

• Builds into its own Edit scene (--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-fade volume 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 --crossfade frames, 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+ needs image_settings.media_type = "VIDEO" before file_format = "FFMPEG". It reports the file size, and the test decodes it back (frame count, size).