ContentRoofLab

LabNote 05Visual selection

A wrong picture is worse than none

An explainer video makes a promise: what you see illustrates what you hear. We measured how often an automatically illustrated video keeps that promise, in nine languages, and found it broken in about one scene in four.

Abstract

ContentRoof illustrates each scene of a video with a drawing chosen from a library of about 11,700, to match what the narrator says. We rated the leading picture of 11,751 scenes in nine languages as matching, wrong or absent. The common approach, matching a sentence's key words to the closest drawing, produced a wrong picture in 23% of scenes, and no language did better than 18%. A new selection step that judges each candidate against the whole sentence raised matching pictures from 62% to 76% and lowered wrong ones from 23% to 17%, with gains of 11 to 17 points in every language. Along the way we found that a single text-cleaning bug had disabled picture matching for Hindi, that short function words cause most errors in languages without grammatical analysis, and that improving the main picture can make a scene worse.

Prefer to watch? The same findings as a 79-second video, made with ContentRoof.
23% → 17%scenes showing a wrong picture, nine languages
+11 to +17points of matching pictures in every language
16% → 70%matching pictures in Hindi after one bug fix
A frame of a ContentRoof video: the words 'Tectonic plates' above a drawing of dinner plates, a wrong pick
A frame of a ContentRoof video: two plates of the Earth's crust colliding and pushing up a mountain
A frame of a ContentRoof video: the words 'A boy' above a drawing of a barn, a wrong pick
Specimens. Left and right: two wrong picks of the kind this note measures. Centre: what "tectonic plates" draws now. All three are frames of ContentRoof videos.

The problem

An explainer works when the picture and the narration say the same thing. When they don't, viewers notice at once: a scene about "the seat of the soul" that shows a car seat tells the viewer that nobody checked.

ContentRoof illustrates every scene automatically, choosing from a library of about 11,700 drawings. Its rule is that a wrong picture is worse than none: when nothing fits, the scene shows the narration as moving type instead. That rule is only as good as our ability to tell right from wrong, so we set out to measure it.

How we measured

We took 11,751 scenes from about 960 explainer scripts in nine languages and rated the picture leading each one against what the narrator says in that scene. Each picture was rated as matching, wrong, or absent, by the same strict rubric everywhere. Improvements were measured on scripts held out from development.

One scene in four was wrong

The common way to illustrate a sentence is to find its key words and pick the closest drawing for each. That approach gave this:

Figure 1The starting point

Matches · 62%Wrong · 23%10%No picture 10%
Matches · 62%Wrong · 23%10%No picture 10%
The picture leading each of 11,751 scenes, rated against its sentence, with key-word matching. "No picture" means the scene showed the narration as moving type. The remaining few percent could not be rated.
Data
PartCountShare
Matches6265%
Wrong2324%
No picture1011%

The errors were remarkably even across languages: between 18% and 27% wrong in every one. German was the weakest, with 52% matching. Most errors were plausible to a computer and absurd to a person: tectonic plates drawn as a dinner plate, space suit as playing-card suits, a boy as a barn.

Finding 1: one bug disabled an entire language

On Hindi scripts, 64% of scenes received no picture at all, and only 16% of the pictures shown matched.

The cause was a single text-cleaning step that kept only "letters and digits". In Hindi's script, vowel signs are encoded as marks rather than letters, so the step removed them: अस्पताल (hospital) became असपतल, a string with no meaning. Meaningless strings then matched unrelated drawings: a heart, a ghost, a light bulb. Keeping the marks raised matching pictures in Hindi from 16% to 70%, with no other change.

The lesson is general: a text pipeline built and tested in English can fail silently in another writing system. Every language needs to be tested on its own real text.

Finding 2: small words cause big errors

For languages without detailed grammatical analysis, every word in a sentence is a candidate for a picture, and short function words were frequently chosen. Spanish más (more) was drawn as a plus sign, todo (all) as a keyboard key, Hindi हैं (are) as a light bulb and Arabic كانت (was) as gravity.

Excluding each language's function words cut wrong pictures in French scripts from 26% to 12%. Some of those scenes received no picture instead, which is the intended trade-off.

Finding 3: judging the whole sentence works in every language

Key-word matching looks at words one at a time. Our new selection step judges each candidate picture against the meaning of the whole sentence. Its effect on matching pictures, by language:

Figure 2Matching pictures, before and after, by language

BeforeAfter0%25%50%75%100%Arabic63%80%Spanish64%80%Hindi66%80%Portuguese64%77%English64%75%Urdu58%73%Italian56%73%French57%71%German52%68%
BeforeAfter0%25%50%75%100%Arabic63%80%Spanish64%80%Hindi66%80%Portuguese64%77%English64%75%Urdu58%73%Italian56%73%French57%71%German52%68%
Share of scenes whose leading picture matches the narration, measured on scripts that were not used during development. Every language gained 11 to 17 points.
Data
BeforeAfter
Arabic63%80%
Spanish64%80%
Hindi66%80%
Portuguese64%77%
English64%75%
Urdu58%73%
Italian56%73%
French57%71%
German52%68%

Every language improved by 11 to 17 points. Arabic, Spanish and Hindi now lead at 80%, ahead of English at 75%. Wrong pictures fell in every language:

Figure 3Wrong pictures, before and after

BeforeAfter0%10%20%30%All nine languages17%23%German18%27%Urdu19%26%English18%25%French21%25%Arabic14%23%
BeforeAfter0%10%20%30%All nine languages17%23%German18%27%Urdu19%26%English18%25%French21%25%Arabic14%23%
Share of scenes led by a picture the narration does not mean. Lower is better.
Data
BeforeAfter
All nine languages23%17%
German27%18%
Urdu26%19%
English25%18%
French25%21%
Arabic23%14%

Finding 4: a better main picture can make a worse scene

A scene often shows a main picture with one or two smaller ones beside it. When we let the new step choose the smaller pictures as well, the main pictures improved but the scenes got worse. It added 4.6 times as many secondary pictures, and enough of them were wrong to crowd the screen with mistakes: "ten" drawn as a "dozen" sign, "woke up" as a sleep icon, "job" as a barbell.

The step now chooses only the main picture, and a secondary picture is kept only when the evidence for it is very strong. A single quality score can rise while what the viewer sees gets worse, so the whole scene has to be evaluated, not one part of it.

Finding 5: a larger library can lose pictures

We added 104 animated illustrations, such as two plates of the Earth's crust pushing up a mountain and a caravan crossing a desert. The next measurement showed 380 scenes that had lost their picture.

The new illustrations' descriptions changed the overall distribution of match scores. The threshold for a confident match is set relative to that distribution, so it moved, and exact matches such as scroll and temple fell below it. Setting the threshold from the drawings alone restored them.

Growing a library changes the statistics every threshold depends on. Each addition needs to be re-measured, not assumed to help.

What's next

One wrong picture in six is better than one in four, but it is still too many. Our next work is on the secondary pictures, which are wrong more often than the main one, and on drawing the ideas that scripts ask for and our library does not yet contain.

Method

Scenes
11,751 ratable scenes from about 960 explainer scripts in English, Arabic, Spanish, Urdu, Portuguese, French, Italian, Hindi and German, on everyday topics: history, science, health, food, travel, business.
Rating
The picture leading each scene was rated against the scene's narration and headline as matching, wrong, or absent, with one fixed, strict rubric for every scene and language.
Held out
Every after figure is measured on scripts that were not used while the new step was developed, split by whole script so no script informed its own result.
Checked by eye
Seventeen scripts covering all nine languages were drafted before and after the change, and every scene whose picture changed was rendered side by side and inspected.

Limits

  • Ratings were made automatically against a fixed rubric, not by a panel of people, and from the drawings' names rather than their images. They are consistent, but not the same as asking viewers.
  • About one leading picture in six is still wrong. The problem is smaller, not solved.
  • Only the leading picture of each scene is measured. The smaller pictures placed beside it are wrong more often and are the next problem.
  • Scripts that name their own pictures are not affected by this work, and many translated scripts do.

Make an explainer →

04 Translation5 Nov 20264 min A billion is not a billion in Spanish Spanish billón, German Billion and French billion mean a million million. How we check every number when a video is rebuilt in another language: 8 of 8 planted errors caught. 8 of 8planted number errors caught 03 Speech5 Nov 20263 min Sixty seconds is a different length in every language Asked for 60 s, our videos came out 44–105 s. Measuring each language's voice per letter now lands 43–62 s in eleven languages, and a cloned voice took Arabic errors from 10% to 0. 44–105 s → 43–62 sasked for 60 s, in eleven languages 02 Evaluation5 Nov 20264 min Balanced benchmarks hid a 95% error rate Our sentence classifier scored 79–95% on balanced tests. On real narration it gave 95% of plain statements a shape they don't have. What we measured and what fixed it. 5% → 88%plain statements left alone 01 Rendering5 Nov 20264 min We took the browser out of video export Our exports spent 80% of every frame waiting for Chrome's screenshot. We draw the same React components with Skia instead: 2.4× faster on a server, 5× on a laptop GPU. 2.4×faster export, the same frames