Case Study — 2026

Automating Devotion

Three hundred devotional songs, each needing its own visual treatment — too many to animate by hand, so I built a system that renders them from code.

  • Animation
  • Made with Code
  • Remotion

One system, shown three ways — a composed film, and two generations of the library it was built from.

The composed piece — library effects sequenced and scored into a single film.

Three hundred devotional songs, each one wanting its own visual treatment. By hand, that’s a year of work I didn’t have — so I built the treatment as a system instead. Every effect is generated from code: parameters in, rendered frames out. Because the pipeline is parametric (built in Remotion), the whole library re-renders, tweaks, and expands without redoing anything by hand. That’s the only reason a better three hundred was even possible — I improved the code and re-ran it, instead of remaking three hundred clips one at a time.

The film at the top isn’t a separate thing sitting beside the libraries — it’s the library put to use. The same effects you see as raw vocabulary in v1 and v2 are the ones sequenced, timed, and scored into the finished piece. The library is the raw material; the film is that material composed.

The Library, Two Ways

Same pipeline, rebuilt.

Two passes at the same system. What matters is the jump from the first to the second: same pipeline, better output.

Version 1 — the first 300. The effect vocabulary, rendered at scale.
Version 2 — the same pipeline, rebuilt. 300 refined effects showing how the system evolves.