Streamer

This is a lightweight framebuffer streamer. It continuously captures framebuffer with 60 fps rate, converts it into YUV colorspace using GLSL shader, compresses resulting buffers into HEVC bitstream using VA-API, and sends the resulting bitstream to a connected client over tcp connection. Everything is done hardware-accelerated and zero-copy. Streamer receives input events from a connected client over the same tcp connection, and forwards those to kernel using uhid api. This streaming server is accompanied by a lightweight receiver client.

When built with Wayland, can also capture the screen in wlroots-based compositors by means of wlr-export-dmabuf-unstable-v1 protocol. I found this useful on my AMD system where capturing framebuffer no longer works.

When built with Pipewire, can capture the audio by exposing an arbitrary-configured audio sink. Audio is forwarded over the same connection to the client uncompressed.

Building on Linux

Streamer depends on following libraries:

• egl
• gbm
• glesv2
• libdrm
• libva
• libva-drm
• pipewire-0.3 (optional)
• wayland-client (optional)

Once you have these installed, just

make

In case you want to build with pipewire and/or wayland-client,

make USE_PIPEWIRE=1 USE_WAYLAND=1

Building anywhere else

I don't care about any other platforms except Linux, so you are on your own. Moreover, I don't really expect it would work anywhere else.

Running

There are couple of things streamer implies. I.e. that the system supports KMS and that it's actually possible to access framebuffers via libdrm. This is certainly the case with Intel and AMD when using opensource drivers. This is certainly not the case with Nvidia and proprietary drivers. Same stands for hardware-accelerated colorspace conversion. I don't really expect Nvidia to support EGL_EXT_image_dma_buf_import and related infrastructure. Hardware-accelerated video encoding is achieved by means of VA-API, and Nvidia does not support the latter. I guess you got the point already - no Nvidia please.

Streamer requires read-write access to the uhid device and a read access to framebuffer if you go with framebuffer capturing. Make sure to provide necessary permissions. Running as root is one option. Provide listening port number on commandline as a single argument:

sudo ./streamer 1337

In case you go with Wayland capturing (and you built with Wayland support), run as an unprevileged user. Make sure you have the read-write permissions on uhid device. I.e. add the user to the input group, and make sure it has read-write permissions on uhid. The latter could be achieved by adding the following snippet to /etc/udev/rules.d/99-streamer-input.rules:

KERNEL=="uhid", GROUP="input", MODE="0660"

If you want to capture audio (and you built with Pipewire support), provide audio channels configuration on the commandline. You must specify sample rate and the channels layout, i.e.:

./streamer 1337 --audio 48000:FL,FR

After starting, streamer would wait for incoming connections from receiver on the specified port. Streamer does not do capturing until receiver is conencted.

What about Steam Link?

For a long time I was suffering from various issues with Steam Link:

• client builtin into usual desktop steam client does not support hardware-accelerated video decoding,
• decicated steam link application is redistributed as a flatpak, and requires to install related bloatware,
• streaming occasionally crashes on server-side bringing down Steam together with streamed game,
• using a mouse wheel makes server-side Steam to crash immediately together with streamed game,
• only back screen is streamed unless server-side Steam is running in big picture mode,
• one of recent updates broke streaming entirely, producing black screen even when running server-side in big picture mode,
• many other minor issues...

What about Sunshine/Moonlight?

I tried this one too. Issues there are not as severe as with Steam Link, but still:

• relies on Qt, boost and other questionable technologies,
• does not properly propagate mouse wheel events making it pretty much unusable,
• video quality occasionally degrades into a blurry brownish mess and never recovers,
• extremely thin Moonlight video-related configuration options are seem to be ignored entirely by Sunshine,
• Sunshine crashed on me when I attempted to stream a game running with Proton.

Fancy features support status

There are no fancy features in streamer. There's no bitrate control - VA-API configuration selects constant image quality over constant bitrate. There's no frame pacing - because I personally consider it useless for low-latency realtime streaming. There's no network discovery. There's no automatic reconnection. There's no codec selection. There's no fancy configuration interface. I might consider implementing some of that in the future - or might not, because it works perfectly fine for my use-case in its current state.

At the same time, it addresses all of the issues listed above for Steam Link and Sunshine/Moonlight. No issues with controls, no issue with video quality, no issues with screen capturing. On top of that instant startup and shutdown both on server- and client-side.

Where is toolbox?

Note, that I don't use github for actual development anymore - it's just a mirror these days. Instead, I self-host git repos on https://burakov.eu. Read-only access is provided via cgit, i.e.: https://burakov.eu/streamer.git. Same stands for toolbox submodule, which is fetched via https using git commandline. You can as well access the code of toolbox directly using your browser: https://burakov.eu/toolbox.git.