Code-First Video Engine With Perceptual Colour and Quality Gates

Developer tools · Creator, sole engineer · active

Product demo videos are made in a GUI editor, which means they cannot be version-controlled, diffed, reviewed, regenerated when the product changes, or produced programmatically from real data.

The detail

This treats video as React components with typed, validated inputs, so a video is a function of data and a malformed input fails at the boundary instead of rendering something subtly wrong.

Two things make it more than a wrapper. First, a perceptual colour system with contrast checking using the modern accessibility model rather than the older ratio formula, which is known to misjudge legibility on dark backgrounds - so generated palettes are verifiably readable instead of eyeballed. Second, an automated quality gate that rejects the generic template look before rendering.

A pipeline can point at a repository and generate a demo video from real repository data, and captions are transcribed locally rather than through a paid API.

Remotion, React, TypeScript, Three.js, GSAP, D3.

What I did

  • Built a data-driven video engine where videos are typed functions of validated input
  • Implemented a perceptual colour system with modern contrast checking rather than the legacy ratio formula
  • Built an automated quality gate rejecting generic template output before render
  • Built a repository-to-video pipeline generating demos from real project data
  • Integrated local transcription for captions instead of a paid API

Stack

React, TypeScript, Three.js, Motion Graphics, Remotion, GSAP, OKLCH, APCA, Color Science, D3.js

Case study: https://www.siddhvasudev.com/projects/code-first-video-engine-with-perceptual