Featured image of post OpenXLR: Elgato Wave Link replacement released in version 0.9.2

OpenXLR: Elgato Wave Link replacement released in version 0.9.2

OpenXLR has been released in version 0.9.2.

The open-source tool is a Linux replacement for Elgato’s Wave Link, offering a PipeWire-based mixer with effects and an OpenDeck plugin. This hardening release follows version 0.9.1 from the same day.

New are hardening fixes against crashing plugin bundles, skins and audio clients, a separate LV2 scan process, a verified control socket directory, and Windows plugin editors that take clicks again on KWin 6.8.3. Release assets are now built and attested before publication, and releases are immutable.

OpenXLR 0.9.2 is a hardening release. It closes ways for a plugin bundle, a skin, an audio client or another user on the machine to crash or stall OpenXLR or reach files it should not, builds the plugin host with hardening flags, and puts every release asset on the release before it is published. It also makes Windows plugin editors take clicks again on KWin 6.8.3.

Plugins

  • Windows plugin editors take clicks again on KWin 6.8.3. With KWin 6.8.3 under XWayland, the Wine window that draws a Windows plugin stayed hidden inside its editor: the picture showed, but every click landed on the window around it. The plugin host now shows that window again whenever it finds it hidden, for CLAP and VST3 editors, and the daemon’s log says so once per opening. It was not a change in OpenXLR: 0.9.1 and Wine 11.21 behave the same on that desktop.
  • The LV2 catalogue is read in a process of its own. The daemon used to read every installed LV2 bundle’s files itself, so a broken bundle could crash or stall the process that runs the audio graph. The plugin host now reads them in a scan with a one-minute deadline and bounded output, and a failed scan keeps the last good catalogue. When one bundle crashes or stalls the scan, the daemon runs it again without that bundle, remembers it until its files change, and lists it with the other skipped bundles. Rescan reads it again.
  • An LV2 port declared as more than one kind (audio, control, atom) now refuses the plugin at load instead of crashing the plugin host.
  • A CLAP plugin that reports a different channel count for a port the second time it is asked can no longer write past the host’s buffers.
  • CLAP editor resize, show and hide requests made from a plugin thread are carried out on the host’s main thread, and a plugin that reports its editor destroyed gets the destroy call CLAP asks for.
  • An X connection error on a plugin’s own thread now ends the plugin host, as Xlib would, instead of jumping onto the main thread’s stack.
  • Plugin and helper search paths (CLAP_PATH, VST3_PATH, LV2_PATH, LADSPA_PATH, PATH) keep only absolute entries. An empty or relative entry used to be read from whatever directory the daemon started in. Each dropped entry is logged once.
  • The plugin host is built with the stack protector, _FORTIFY_SOURCE, a position-independent executable, full RELRO with immediate binding and a non-executable stack. The Nix build no longer links an executable stack.
  • The Windows bridge companion moves to 5.1.1.54 revision 4. Same yabridge commit and the same disk identity patch, with the plugin libraries the plugin host loads now built with the stack protector, _FORTIFY_SOURCE, full RELRO with immediate binding and a non-executable stack. Until now no package hardened them, because the packagers’ flags reach only the Wine side of the build. Checked on the desk with TDR Kotelnikov, editor included. Options shows the version in use.

Daemon

  • The control socket’s directory is checked before it is used: a real directory owned by you, mode 0700, in a runtime directory that no other user can rename it out of. The daemon refuses to start its control socket otherwise and logs why, and the UI runs without its single-instance guard instead of using such a directory.
  • The icon of a Windows game is read only from a regular file and off the stream sweep. An audio client could name a pipe as its program and stall the sweep for good.

UI, Deck and browser

  • Skins can’t reach outside their folder. A skin.json that is a link to a device or a pipe no longer stalls or crashes the UI at start; Options reports the skin as broken. A skin’s image is resolved through every linked folder and refused when its real path is outside the skin. Links that stay inside the skin, and a skin folder linked to a working copy, still work.
  • The browser companion captures only tabs you activated. A request from OpenXLR starts capture only on a tab where you pressed Activate this tab in the popup, while it stays on the same site. For any other tab it brings the tab forward and opens the popup. Stop routing, closing the tab or moving it to another site forgets it.
  • The Deck plugin drops a message it cannot use, such as a hand-edited key whose target is a number, instead of exiting and blanking every key and dial.

Project

  • Release assets are built and attested before the release is published. The .deb, .rpm, deck plugin zip and browser companion are built by workflows from the tag and attached to a draft release, each with a checksum file and a build provenance attestation, and the release is published only once every asset is on it. Releases are now immutable. The deck plugin zip and the browser companion build reproducibly from the tag. docs/releases.md lists every asset and how to check it, and the attestation check now names the repository, the workflow and the tag.
  • A security policy, SECURITY.md, says how to report a vulnerability privately.
  • The Windows bridge companion’s build instructions build in a directory you own instead of a fixed path under /tmp, and build.py refuses a source or output directory someone else could write.
  • A startup test that timed out on busy build machines gets the time a whole graph build takes.

OpenXLR mixer

Source: GitHub

PlayingTux – Playing Games on Linux - since 1995.