← Commit history

docs/recording.md: root-relative image paths so crops render

John Lauer ·80e95afd4e ·1mo ago ·parent 9989cc4
1 file changed +3−3
docs/recording.md+3−3
@@ -7,7 +7,7 @@ with a **hardware encoder** (NVENC / Quick Sync / AMD) doing the work and the frames staying on the GPU end to end. No browser, no screenshot loop, no extra capture app. -![A frame from a desktop recording made by Adom Bridge](recording/scene.png)+![A frame from a desktop recording made by Adom Bridge](docs/recording/scene.png)  *Every image on this page is a real frame from a recording Adom Bridge made itself, driving an idle test PC.*@@ -65,7 +65,7 @@ gradients on fast motion hold together a little better.  | A — H.264 @ 3.8 Mbps (11 MB) | B — H.265 @ 3.8 Mbps (11 MB) | |---|---|-| ![H.264 at 3.8 Mbps](recording/crop-h264-3_8mbps.png) | ![H.265 at 3.8 Mbps](recording/crop-h265-3_8mbps.png) |+| ![H.264 at 3.8 Mbps](docs/recording/crop-h264-3_8mbps.png) | ![H.265 at 3.8 Mbps](docs/recording/crop-h265-3_8mbps.png) |  **A vs C — the size win.** This H.265 take is at half the bitrate and is **half the size of the H.264 file** — yet on the same scene it still holds its@@ -74,7 +74,7 @@ bytes to store and move.  | A — H.264, 11 MB | C — H.265, 5.6 MB (half the size) | |---|---|-| ![H.264 11 MB](recording/crop-h264-3_8mbps.png) | ![H.265 5.6 MB](recording/crop-h265-1_9mbps.png) |+| ![H.264 11 MB](docs/recording/crop-h264-3_8mbps.png) | ![H.265 5.6 MB](docs/recording/crop-h265-1_9mbps.png) |  (Honest note: at a generous bitrate H.264 and H.265 both look great — the codec gap is widest at low bitrates and, above all, in file size. Pick H.265 when you