screen_capture_lite
cross platform screen/window capturing library
Runssource: GitHubCMITcommit 0c5beb0e3c5e
C, MIT licensed. The project labels itself: c plus plus, cross platform, desktop duplication api, linux, mac, screen capture, screen reader and screen recorder.
screen_capture_lite runs. An Argusic agent installed it in 12 minutes and hit 5 errors on a clean machine with no GPU, and the whole session was recorded.
screen_capture_lite shared library and both C++ examples build and install; on Xvfb :99 the C++ example streams 1280x800 frames at ~10fps, SCL_GetMonitors returns the 1280x800 virtual monitor with non-zero frame pixels, and SCL_GetWindows enumerates the EWMH-mocked window.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Could NOT find X11: libx11-dev/libxtst-dev/libxinerama-dev/libxfixes-dev absent and no root to apt-get install2 minutes
- GLFW and core lib missing XShm.h/Xrender.h/Xcursor/Xrandr/XInput headers2 minutes
- SCL_GetWindows hit BadAtom on bare Xvfb because no window manager sets _NET_CLIENT_LIST2 minutes
- X11/X.h and other core protocol headers missing from libx11-dev (split into x11proto-dev on Ubuntu 24.04)1 minute
- C# bindings cannot build: no dotnet SDK in container1 minute
- Install time
- 12 minutes
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 5 hit, 4 fixed with no human help
- How the result was proved
- LD_LIBRARY_PATH=build ./screen_capture_example_cpp_shared printed 'Application Allowed to Capture the screen!' and 'onNewFrame fps10' repeatedly; custom C API test printed 'SCL_GetMonitors -> 1 monitor 1280x800' and 'RESULT frames=30 first_frame=1280x800 stride=5120 nonzero=1'; with EWMH mock 'SCL_GetWindows -> 1 window name=scl mock window size=200x100'; ctest printed 'No tests were found!!!'
- Model tokens used
- 1,051,875
- Exact commit tested
- 0c5beb0e3c5e
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- `SCL_GetWindows` returned the mock window (`name=scl mock window size=200x100`) when a schema-cor… - `ctest` reports "No tests were found!!!" — the repo ships no test suite. - Errors fixed: missing X11 dev packages/headers (staged from distro `.debs` into `/tmp/x11-extract… tokens used 1,051,875 All verification is complete. Final report: - Built `libscreen_capture_lite_shared.so`, `screen_capture_example_cpp_shared`, and `screen_captur… - `screen_capture_example_cpp_shared` ran on Xvfb `:99`, enumerated the virtual monitor (`Id=0 Inde… - C API exercised directly: `SCL_GetMonitors` returned 1 monitor; with a red-filled window painted … - `SCL_GetWindows` returned the mock window (`name=scl mock window size=200x100`) when a schema-cor… - `ctest` reports "No tests were found!!!" — the repo ships no test suite. - Errors fixed: missing X11 dev packages/headers (staged from distro `.debs` into `/tmp/x11-extract…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 12 minutes, faster than the median of the 8 comparable projects Argusic has measured.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Hit 5 errors during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 9 c-plus-plus projects Argusic has installed and timed, screen_capture_lite was the 4th fastest to reach a running state, and 8 of 9 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
c-plus-pluscross-platformdesktop-duplication-apilinuxmacscreen-capturescreen-readerscreen-recorderscreencastscreenshotscreenshot-utilityscreenshotswindows
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/screen-capture-lite)Questions
- Does screen_capture_lite run?
- Yes. screen_capture_lite runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test screen_capture_lite?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0c5beb0e3c5e. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test screen_capture_lite?
- The run that produced this verdict cost $0.30: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does screen_capture_lite take to install?
- 12 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does screen_capture_lite need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing screen_capture_lite?
- 5 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does screen_capture_lite compare with the alternatives?
- Of the 9 c-plus-plus projects Argusic has installed and timed, screen_capture_lite was the 4th fastest to reach a running state, and 8 of 9 reached one at all.
- Where is the evidence for screen_capture_lite?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.