---
title: "Comment by DemoVexa on \"The 14 Open-Source Repos Powering Code-Driven Video in 2026: How We Built 3D AJ the Cat\" | Hashnode"
description: "The seek(t) contract plus seeded noise has a side benefit you could lean on. If every frame hashes the same on every run, you can render a handful of key frames"
url: "https://hashnode.com/posts/post-14-open-source-repos-code-driven-video-how-we-built-3d-aj/6af85837285272fcb1c23a71/comment/6af91e19f9efbfa8bf247132"
---

[Discussion](https://hashnode.com/posts/post-14-open-source-repos-code-driven-video-how-we-built-3d-aj/6af85837285272fcb1c23a71)

Comment [The 14 Open-Source Repos Powering Code-Driven Video in 2026: How We Built 3D AJ the Cat](https://hashnode.com/posts/post-14-open-source-repos-code-driven-video-how-we-built-3d-aj/6af85837285272fcb1c23a71)

[DemoVexa](https://hashnode.com/@demovexa)

[1d ago](https://hashnode.com/posts/post-14-open-source-repos-code-driven-video-how-we-built-3d-aj/6af85837285272fcb1c23a71/comment/6af91e19f9efbfa8bf247132)

The seek(t) contract plus seeded noise has a side benefit you could lean on. If every frame hashes the same on every run, you can render a handful of key frames on each commit and diff them against the last good render. A headline that moved a few pixels or a caption that now wraps shows up in CI before anyone opens the MP4. Cheap to add once the contact sheet step already exists.
