Autonomous Video Studios
HomePART II · The original programme
CHAPTER 5 · NEW SINCE THE FIRST EDITION

Blender episodes: a second kind of picture

Since 10 November the live channels also post Blender episodes: photoreal 3D scenes rendered in Blender, the open-source studio tool, from free CC0 models, textures and skies, with real street maps where a place matters. Today they fill two of every live channel's daily slots. 117 have been made so far, in seven of the ten projects, with an average critic score of 8.0.

Why a second picture#

Code-rendered scenes are exact and distinctive, but they look like diagrams that move. The bar the owner set for this format was a professional engineering explainer: real materials, real light, real machinery at human scale, labels in the scene and every spoken word captioned. Blender is how a studio would make that, and the system now makes it the same way a studio would — by building a 3D scene, not by asking a model to imagine footage.

A Blender episode, end to end — the same planner, voice, captions and publishing as a code episode
1Topic

the channel's planner, as for code episodes

2Scene build

the agent writes a Python build of the scene for Blender

3Render

Blender 4.5 LTS on an NVIDIA L4, headless: 1.5–5 GPU-hours

4Voice, words

Chirp 3 HD narration; each word heard back and timed

5Gates

critic, caption sync, in-scene labels clear, the 90-second edit

6Review, slots

a channel's first two Pass or Reject; then 2 slots a day

Free CC0 assets, real maps

Poly Haven models, textures and skies, cached on every box and checksummed; OpenStreetMap streets

feeds step 2, the scene build
The opening line

“Animated and rendered in Blender with open-source tools and free CC0 assets. No AI-generated video.”

Figure 8. How a Blender episode is made. The topic planner, the narration, the word-timed captions, the review and the publishing are the code episodes' own; what differs is the scene and its render.

How it works#

  • The scene is written, then built. The episode agent writes a Python build of the scene against the system's own Blender toolkit: physically based materials, high-dynamic-range skies, models placed and instanced, a camera language and a colour grade. Nothing is hand-modelled per video. Blender agents run on Claude Opus 5.5: measured on the launch, it scored the same as Fable at a third to a half of the cost.
  • Real assets, legally. Models, textures and skies come from Poly Haven's CC0 library — free for any use, no attribution owed; a searchable catalogue of 997 skies, 869 textures and 521 models — cached on the boxes and checked by checksum. Where a real place matters, its streets, rivers and rail lines are built from OpenStreetMap.
  • Rendered on the same GPUs. Blender 4.5 LTS renders headless on an NVIDIA L4 at about 0.8 seconds a frame — an hour of frames per round, one and a half to five GPU-hours an episode with its fix rounds — in Blender pools of their own, one per project, which give way to the live projects' code work when GPUs are scarce.
  • Captions that are the voice. Every spoken word is on screen, lit as it is said; labels sit in the scene itself, and a check makes sure no label is hidden behind geometry.
  • Nothing toy-like. The critic holds Blender episodes to a professional explainer's look: since 13 November it blocks anything that reads as a toy — a storm drawn as a disc, a town of white boxes, a few primitives standing in for a machine — and the fix round replaces it.
  • Honest about what it is. Each Blender episode opens with one line: Animated and rendered in Blender with open-source tools and free CC0 assets. No AI-generated video. The script is written with an AI model and the voice is synthesized; the line says exactly what is true of the picture.
  • Reviewed before it is scheduled. A channel's first two Blender episodes wait for the owner's Pass or Reject in the portal; after that, Blender takes two of the channel's daily slots and code the rest.
  • Every asset is visible. An episode's page lists every model, texture, sky and map it was built from, with its source and licence.
Blender episodesCode episodes
Made1171,898
Average critic score8.018.09
Model time per episode$11.39$10.79
GPU time per episode1.5–5 L4-hours, fix rounds includedunder an L4-hour, two episodes to a box
PictureBlender 4.5 LTS: CC0 assets, real mapsWebGL2: the channel's own renderer kit
Model time is measured per call: code episodes since 12 October, Blender episodes since 10 November.

What they look like#

Colossal Scale · 29,009 views
This 7 km train has engines in the middle, run by radio
Fracture Atlas · 11,360 views
Why engineers cut half this beam's flange away. On purpose
Inside The Machine · 5,036 views
How does a fuel nozzle know your tank is full? No electronics
Inside The Machine · 4,763 views
How does a tower crane get taller? It jacks up its own head
Into The Deep · 3,421 views
3,000 m under the Gulf of Mexico, a volcano erupts asphalt
Into The Deep · 3,111 views
Health-check a whale without touching it? Catch its snot
Inside The Machine · 2,942 views
How does a train climb a 48 % slope? It grips the rail sideways
Fracture Atlas · 2,402 views
Why is aircraft skin allowed to wrinkle under load?
Fracture Atlas · 2,355 views
Why are gas cylinders tested with water, not gas?
Into The Deep · 2,253 views
The 8 m 'sea serpent' that swims standing up
Upright Robots · 1,784 views
To stop a swinging load, the drone moves twice
Figure 9. Eleven of the most watched Blender episodes, at most three of a channel, by their real thumbnails: the scene, its in-scene labels and the word being spoken lit in gold (views on their best platform).