After Effects took 6 hours to render. Opus 5.5 did it in 30 seconds. But that's only the beginning

An 18-second 3D animation took After Effects 6 hours to render. Switched to Claude Opus 5.5, it took only 30 seconds. This isn't a joke—it's what m4lka just did.

The animation m4lka made is called “Claude vs Grok.” Two voxel mascots climb out of an X post card, fight, and end up exchanging hearts. 18 seconds, 60fps, one continuous shot, with all visuals and sound generated by code. The comparison he showed in his tweet: After Effects takes 6 hours to render this clip, while Opus 5.5 generated the code and rendered it in only 30 seconds.

But in a long post he published afterward, he poured cold water on it: Opus 5.5 can produce a beautiful first frame, but fixing a frame is the real skill.

The first render looks “finished,” but it doesn't hold up to close inspection. The text in the post is gray placeholder bars, the orange mascot has turned peach, the card should be black but looks blue, and the reference room has been replaced by an ordinary desk. These problems can't be spotted by looking at a single frame; they all reveal themselves in a contact sheet.

He breaks the workflow into five layers: director, reference, timeline, renderer, and critic. Each layer has to produce something verifiable, rather than stopping at “a feeling.”

The most counterintuitive layer is the “critic.” Put simply: the model cannot score its own work; checks must rely on evidence. He divides all conclusions into three categories: observed (visible in a specific frame), inferred (multiple observations point to it but it is unconfirmed), and unknown. Then, use the contact sheet to look at more frames and use color probes to measure, rather than relying on your eyes.

For example, “Claude is too peach” is not valid feedback. Valid feedback is: use probe.py to measure the main subject in the highlights; the target hex is #D97757, and the measured value is #E2A276. Only after changing it to #D97757 can you be sure you fixed it correctly.

He even deliberately plants defects in the render to test whether his inspection process can catch them. If it can't, that means the inspection is just a ritual, not a process.

Someone in the comments added a key detail: those 30 seconds are code generation time, not the final video file. To get a clean MP4, you still have to capture frame by frame under a locked clock. For a 13-second 3D clip, capturing at 30fps takes about 2.5 minutes. m4lka admits this is true. But compared with After Effects' 6 hours, it is still an order-of-magnitude crushing victory.

So when you see someone showing off AI animation, don't rush to be amazed. First ask: if frame 148 has a problem, do you know which line of code to change?

If you don't know, then it's just good luck. Real directors and engineers make every frame stand up to scrutiny.

m4lka's complete guide is here: https://x.com/i/article/2112529635778965505