From 2b32153c8bf33abdb93b4eeec149b6815e0d5530 Mon Sep 17 00:00:00 2001 From: Hermenix Date: Wed, 30 Sep 2026 19:43:32 +0000 Subject: [PATCH] =?UTF-8?q?examples:=20README=20=E2=80=94=20measured=20cap?= =?UTF-8?q?ture=20costs,=20v3=20window=20rules,=20hyprctl=20IPC=20caveat?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- examples/README.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/examples/README.md b/examples/README.md index 67f0f06..223163c 100644 --- a/examples/README.md +++ b/examples/README.md @@ -39,11 +39,14 @@ accurate. 2. **Google rate-limits you.** The first search from a fresh profile usually passes; the third in a minute gets `unusual traffic`. It is the IP, not the browser. Wait a few minutes and re-run. -3. **The frame server tops out around 12 fps** on a software-rendered VM - (`grim` plus a PNG encode per frame, competing with the browser for two - cores). Leave `--capture-fps` at its default of 30 so nothing is thrown away: - the encoder uses the *measured* rate, so the video plays at real speed either - way, and decimating only makes it choppier. +3. **The frame server was the bottleneck, and it was PNG.** Measured with `grim` + at 1280×720 on this software-rendered VM: PNG ~326 ms/frame (a ~3 fps + ceiling), PNG `-l 1` ~105 ms, **JPEG q80 46 ms**. The session therefore + streams JPEG and the demo records ~22 fps. The script never assumes the + format — it takes the extension from the Hello and hands it to ffmpeg — so + either setting works. Leave `--capture-fps` at its default of 30 so nothing + is thrown away: the encoder uses the *measured* rate, so the video plays at + real speed either way, and decimating only makes it choppier. ### It films a desktop, not a browser