examples: README — measured capture costs, v3 window rules, hyprctl IPC caveat
This commit is contained in:
1 parent
1664ccf710
commit
2b32153c8b
1 file changed
+8
-5
+8
-5
@@ -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
|
||||
|
||||
|
||||
Reference in new issue
Block a user