Record your screen, ship a demo. Free and open-source, GPU-accelerated, no watermarks, no subscriptions. Windows, macOS, Linux. Actively maintained.
TypeScript cross-platformelectronffmpegopen-sourceproduct-demorustscreen-capturescreen-recorderscreen-recordingscreen-studioscreencastspeech-to-texttypescriptvideo-editingvideo-editorwaylandwgpuwhisper
type CommandLine = Pick<Electron.CommandLine, "appendSwitch" | "hasSwitch" | "getSwitchValue">;
type Env = Readonly<Record<string, string | undefined>>;
export function isWaylandSession(env: Env): boolean {
return env.XDG_SESSION_TYPE === "wayland" || env.WAYLAND_DISPLAY !== undefined;
}
/**
* Whether Chromium draws this process's windows through its Wayland backend: a Linux Wayland
* session, unless an explicit `--ozone-platform=x11` sent it to Xwayland, which
* configureWaylandSupport leaves alone.
*/
export function usesWaylandBackend(
platform: NodeJS.Platform,
commandLine: Pick<Electron.CommandLine, "getSwitchValue">,
env: Env,
): boolean {
return (
platform === "linux" &&
isWaylandSession(env) &&
commandLine.getSwitchValue("ozone-platform") !== "x11"
);
}
/** Prefer Wayland in a Wayland session, while respecting an explicit backend. */
export function configureWaylandSupport(commandLine: CommandLine, env: Env): void {
if (!isWaylandSession(env)) return;
if (!commandLine.hasSwitch("ozone-platform")) {
commandLine.appendSwitch("ozone-platform", "wayland");
}
// Enable WebRTCPipeWireCapturer for screen capture on Wayland
appendFeatures(commandLine, "enable-features", "WaylandWindowDrag,WebRTCPipeWireCapturer");
// Chromium's Wayland Ozone backend can't use Vulkan. When it tries, the WebRTC
// PipeWire capturer fails to import DMA-BUF frames into EGL (EGL_BAD_MATCH), the
// stream renegotiates, and screen recording yields no usable frames. Force the
// GL/EGL path so DMA-BUF import works. (Chromium itself logs this suggestion:
// "'--ozone-platform=wayland' is not compatible with Vulkan ... disabling Vulkan".)
appendFeatures(commandLine, "disable-features", "Vulkan");
}
/**
* Add to a feature list instead of replacing it. Chromium keeps only the last value of a
* repeated switch, so a bare appendSwitch silently dropped whatever the user passed as
* `--enable-features=` or `--disable-features=` on the command line.
*/
function appendFeatures(commandLine: CommandLine, name: string, features: string): void {
const existing = commandLine.getSwitchValue(name);
commandLine.appendSwitch(name, existing ? `${existing},${features}` : features);
}