Render Orchestration
These buttons run the engine CLIs. The pipeline lives in the CLIs and carries every governance gate, so nothing here reimplements it. Jobs run in the background and stream their real output, failures included.
RENDER ONE CLAIM — npm run render
Renders cost 2 to 8 minutes of CPU. The job runs in the background and streams its log below. Concurrency is 1: a second render queues.
WEEKLY BATCH
Validates rotation, then renders every ready entry.
BRAG CUT
The non-Remotion engine. Typographic, with audio.
CHECKS
Read-only engine reports.
JOBS — 0
No jobs this session. Start one above.
RUNTIME
- Renders are CPU heavy. Expect 2 to 8 minutes per clip.
- The brag engine is not Remotion. It stays a renderAt(t) HTML renderer with NumPy audio and a two-pass FFmpeg encode.
- Stage plate generation needs FAL_KEY in the engine .env. It is a one-time step, not part of a render.