overthinkos/wl-record-pixelflux

wl-record-pixelflux -- Desktop video recording via selkies capture bridge

Layer Properties

| Property | Value | |----------|-------| | Install files | layer.yml, tasks:, pixelflux-record (Python script) | | Depends | selkies (capture bridge + WebSocket stream), ffmpeg (MP4 muxing) |

What It Does

Provides pixelflux-record for recording desktop video on selkies-desktop. Connects to the capture bridge at /tmp/ov-capture.sock which relays the same H.264 frames that the browser sees via the selkies WebSocket stream. No direct ScreenCapture API access -- taps into the existing selkies streaming pipeline to avoid creating a second capture instance (the Rust backend only supports one active capture at a time).

Why not wf-recorder? labwc running nested inside pixelflux can't deliver wlr-screencopy frames. The capture bridge bypasses this by tapping into the selkies WebSocket stream directly.

How It Works

1. Connects to Unix socket at /tmp/ov-capture.sock (started by selkies-capture-server)
2. Sends STREAM\n to request continuous H.264 frame data
3. Receives frames as 4-byte length + raw H.264 data pairs
4. Pipes raw H.264 data to ffmpeg with -use_wallclock_as_timestamps 1
5. ffmpeg re-encodes to MP4 with correct wall-clock timing
6. SIGINT/SIGTERM triggers graceful shutdown: closes socket, waits for ffmpeg to finalize MP4

Key Properties

| Property | Value | |----------|-------| | Depends | selkies (capture bridge + stream), ffmpeg (muxing) | | Install | ~/.local/bin/pixelflux-record (Python script) | | Capture | Via /tmp/ov-capture.sock (selkies WebSocket bridge) | | Output | MP4 (H.264 video + optional AAC audio) | | Audio | PulseAudio monitor source via ffmpeg |

CLI Usage

# Direct usage
pixelflux-record output.mp4                  # 30fps, video only
pixelflux-record output.mp4 --fps 60         # 60fps
pixelflux-record output.mp4 --audio          # video + audio
pixelflux-record output.mp4 --fps 60 --audio # 60fps + audio
# Stop with Ctrl-C

Integration with ov eval record

# Start desktop video recording (auto-detects pixelflux-record)
ov eval record start selkies-desktop -n demo --mode desktop --audio

# Run commands (visible in recording)
ov eval record cmd selkies-desktop "echo hello" -n demo

# Interact with desktop
ov eval cdp open selkies-desktop "https://example.com"
ov eval wl click selkies-desktop 640 360

# Stop and copy to host
ov eval record stop selkies-desktop -n demo -o demo.mp4

Architecture

selkies process (single ScreenCapture singleton — process-wide)
    ├── ScreenCapture (captures full composited desktop)
    ├── WebSocket server :8081 (broadcasts H.264 frames)
    └── Capture bridge thread (internal WebSocket client)
        └── Unix socket /tmp/ov-capture.sock
            └── pixelflux-record connects here (STREAM mode)
                └── pipes H.264 frames to ffmpeg

Singleton note: The ScreenCapture instance is process-wide and lives inside the selkies Python process. pixelflux-record never spawns its own capture; it only attaches to the existing STREAM socket. This is architecturally important because pixelflux's WaylandBackend construction is expensive (EGL context + dmabuf allocators + GPU texture pools) and was the subject of a memory leak fix in commits 6be85eb (singleton enforcement) and 7977b91 (per-frame cleanup_texture_cache()). If you ever see two selkies-capture processes inside the container, that's a regression — see /ov-selkies:selkies (Pixelflux Memory Management) for the diagnostic recipe.

Included In

• selkies-desktop metalayer

Used In Images

• /ov-selkies:selkies-desktop (via selkies-desktop metalayer)
• /ov-selkies:selkies-desktop-nvidia (via selkies-desktop metalayer)

Cross-References

• /ov-advanced:record -- ov eval record start --mode desktop auto-detects pixelflux-record
• /ov-core:update -- Per-instance update pattern used to roll out the per-frame cleanup_texture_cache() fix across live instances
• /ov-selkies:wl-screenshot-pixelflux -- Screenshot companion (same capture bridge, same singleton)
• /ov-selkies:wf-recorder -- Alternative for sway-desktop (wlr-screencopy)
• /ov-selkies:selkies -- Parent layer (provides capture bridge, WebSocket stream, and the ScreenCapture singleton — see Pixelflux Memory Management)
• /ov-selkies:selkies-desktop -- Metalayer that composes this recorder into the full browser-accessible desktop
• /ov-selkies:ffmpeg -- Required dependency (MP4 muxing)

When to Use This Skill

Use when the user asks about:

• Desktop video recording on selkies-desktop
• The pixelflux recording pipeline
• The wl-record-pixelflux layer

Related

• /ov-build:layer — layer authoring reference (layer.yml schema, task verbs, service declarations)
• /ov-build:eval — declarative testing (eval: block, ov eval image, ov eval live)