Skip to content

chantier: Remotion-parity — wave 2 #54

Closed

Description

@LeadcodeDev

Tracking issue for the Remotion-parity chantier (2026-07-19), following the analysis comparing rustmotion's verified capabilities against Remotion 4.x video families. Same process as wave 1 (#24): one branch + squash-merged PR per workstream, sequential integration, full suite at each merge.

Execution order & status

Lot A — family unlockers

Lot B — motion-design finish

Backlog (instruction needed before commitment)

Decision log

  • Whisper: subprocess-first (auto-detect whisper.cpp CLI, like the ffmpeg philosophy) — no heavy C++ build deps in the default binary; SRT/VTT import is fully offline.
  • Audio analysis: rustfft (pure Rust) as a pre-analysis pass — single-binary principle intact.
  • Squash-merge autonomous per the standing authorization (wave 1).

Activity

  1. LeadcodeDev commented on Jul 19, 2026

    @LeadcodeDev
    OwnerAuthor

    Wave 2 complete: 9 workstreams squash-merged (PRs #55–#63), test suite 222 → 332, CI green at tip. Every Lot A family unlocker and all of Lot B shipped. Backlog issues #52 (Lottie evaluation) and #53 (time remapping) remain open — both deliberately instruction-gated. Declared non-goal recorded: 3D scenes/meshes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions