Videos: the tempo of a recording not in real time is a speed

The log line and the notice give seconds of video per second the
recording took, 0.20x for one five times slower than real time. The
page says what the figure means and that it can go above 1x.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Videos.md

@@ -268,8 +268,10 @@ back through pixel buffers with a fence. The encoders, the sound and the file ar
 With **Real time** off (#423) the game moves on by exactly one frame of the recording at a time,
 1/60 or 1/30 s, however long the computer takes for it, and only once the frame before is taken.
 So the file has every frame, 4K at 60 fps too. The game view runs slower meanwhile, and the notice
-line says how far it has got, such as `Recording "Trailer" not in real time: 4.2 s of video, 2.6x
-real time`.
+line says how far it has got, such as `Recording "Trailer" not in real time: 4.2 s of video, 0.38x
+real time`. The speed is seconds of video per second it took: 0.38x is a little under three times
+slower than real time. It can go above 1x, when the scene is cheap and the editor draws more
+frames a second than the recording has, on a 144 Hz screen say.
 
 - **The sound is made apart**, in an offline audio context: while it records, what the run plays
   (sounds, instruments, patterns, songs, the audio items of a composition) goes there instead of
@@ -286,7 +288,7 @@ real time`.
 - **At most ten minutes:** the offline context holds all of its sound in memory, 230 MB for ten
   minutes. A recording that gets there stops and says so in the log.
 - **When it is saved**, the log says how long it took, such as `Recording "Trailer" took 35.2 s
-  for 13.8 s of video, 2.6x real time, and has every frame`. The start line ends with
+  for 13.8 s of video, 0.39x real time, and has every frame`. The start line ends with
   `not in real time`.
 - Only the node records so. **Start recording…** in the main menu records the editor in real time.