A piano piece drawn in code, then rebuilt in 3D
Kevin Ngo had Claude write a piano score and draw every 2D frame in JavaScript. A second Claude read that code as choreography and rebuilt the piece in 3D, in Blender.
Kevin Ngo started in 2D. Claude wrote the piano score and drew every frame in JavaScript. Then he handed that film to another Claude, as reference, and because the whole thing was code, the second model could read the choreography exactly and rebuild it in 3D in Blender.
A picture of a performance is a bad reference. A program of a performance is a perfect one. Timing, notes and positions were already numbers, so the 3D version did not have to guess what the 2D version meant. It had to interpret a score that happened to be runnable.
The post is a quiet argument for making the first version in code, even when the first version is not the one you want to keep.

Made with
Kevin Ngo
@kevin_t_ngo
Initially, I had Claude make this animation in 2D. It wrote the piano score and drew every frame in JavaScript. I gave this 2D version as reference to another Claude. Because the whole film was code, Claude was able to use its exact choreography and make the 3D one in Blender. https://t.co/XAb8XZgQG3
916 likes
- likes
- 916
- replies
- 51
Captured when this was curated, not live. —