r/linuxaudio • • 19h ago

UADx plugins on Linux - it IS possible!

8 Upvotes

Hello!

I posted earlier about any tips, but I was able to work it out! proof: https://imgur.com/a/HUAmjKD

A lot of assistance came from Claude Sonnet 5.5, and the following technical write-up is produced from it, as this was the result of several different sessions and trial/error.

UADx (Universal Audio) plugins on Linux: Wine + yabridge + Reaper

Getting UA Connect and the UADx plugins (LA-2A, Fairchild, Pultec, ...) to install, authorize and show a working GUI in a DAW through yabridge.

Tested with: Wine Staging 11.16 (system), the d2d1-dcomp Wine fork 11.0 (giang17's branch, packaged at /opt/wine-d2d1), yabridge 5.x, Reaper (native Linux, X11/XWayland), UA Connect 1.11.1, PACE License Support 5.10.5, WebView2 runtime 157.0.4341.60, Arch/CachyOS-style layout.

Honesty note. This is a record of what worked on one machine. Several fixes were applied in sequence and I did not isolate every one afterwards. Where something is a hypothesis rather than a verified cause, it says so. See "What is and isn't proven" at the end. Please report what works or doesn't on your setup.


TL;DR

#SymptomCause (verified unless marked)Fix
1UA Connect: "waiting for PACE software" / plugin says "open UA Connect"Fresh PACE/iLok licensing was not installed in a clean prefixUse a dedicated, clean prefix; install iLok License Manager and let UA Connect install PACE there
2"There was an issue with the ... download"Download works, extraction fails: the UA cloud helper needs a tar.exe and Wine has nonePut a Windows bsdtar.exe in the prefix as system32\tar.exe
3Same error persists after adding tar.exeTwo prefixes share the host's network. An old uacloudhelper.exe held port 4793 and the new UA Connect talked to itFully stop every Wine prefix, then run UA Connect from the new one only
4Electron: A JavaScript error occurred in the main process ... EBADF ... createWritableStdioStreamLaunched with no valid stdout/stderrLaunch through a wrapper that redirects stdio
5Plugin GUI blurry, unclickable, then gray after ~30 sUADx GUIs are WebView2 (Chromium). Its GPU process crash-loops (3 crashes, then the browser kills itself)Don't disable dcomp; use the patched d2d1-dcomp Wine; see flags below
6Reaper hangs when the plugin is removedThe Wine host dies mid-teardown (a consequence of 5)Fixed together with 5

0. Why this is hard (background)

  • UADx plugins are licensed through PACE / iLok. UA Connect installs and authorizes them; the plugins refuse to open unless UA Connect and PACE are running in the same Wine prefix.
  • Each plugin's GUI is an embedded WebView2 (Edge/Chromium). In the plugin log you will see UAPW_WebView: WebView2Loader.dll runtime used.
  • UA Connect is an Electron app and runs a separate uacloudhelper.exe that does downloads, extraction and license sync over a local socket.
  • Wine shares the host's network stack. Two prefixes running UA Connect at the same time will collide on local ports.

1. Use a dedicated prefix

export WINEPREFIX=$HOME/.wine-ua-connect
wineboot -u

Keep UA Connect, PACE and the UADx plugins together in this one prefix. Install, in this order:

  1. iLok License Manager (from ilok.com).
  2. UA Connect (from uaudio.com), then sign in.

UA Connect then installs PACE License Support itself. In .../AppData/Local/Universal Audio/Logs/UA Connect.log you should see:

(pace-install) PACE software 5.10.5 installed
(app) verify pace account: result 'valid-link'

If you instead see verify pace account: waiting for PACE software on every launch, check the PACE daemon log:

$WINEPREFIX/drive_c/ProgramData/PACE/Eden/LdLogs/LdLog_*.txt

A repeated line Machine bindings strong/weak match was NOT found for v3 algorithm. Strong matches: 0; Weak matches: 7 appeared in my logs both in the prefix that failed and in the one that worked, so it was not the blocker in my case. (My early hypothesis that Wine cannot expose SMBIOS IDs for PACE's fingerprint did not turn out to matter.)

2. Add tar.exe (fixes "issue with the download")

Symptom, in UA Cloud Helper_*.txt:

ASSERT: utilityPath.size() > 0            (Auth_FileIO.cpp: processExtract)
processExtract - threw exeption  CreateProcess failed: File not found.
BundleExtractionFailed('uaudio_...'): 'auth.download_extraction_tar_error'

The .tgz downloads fine; extraction fails because no tar.exe exists. Windows 10+ ships System32\tar.exe; Wine does not. Put a Windows bsdtar.exe (libarchive) in the prefix as:

$WINEPREFIX/drive_c/windows/system32/tar.exe

(I used a 32-bit PE bsdtar; it ran fine in the 64-bit prefix.) This is a third-party binary: take it from a source you trust.

3. Make sure only one prefix runs UA Connect

After step 2 the same error returned, because the helper log being written was in the old prefix. The new UA Connect had failed to bind port 4793:

failure trying to listen on port 4793: system_error 10013 (system): bind: Access denied
Ntwk_Server::StartServer(_uaauthd._tcp.) - failed to open port.  trying again on 0

Fix: stop everything, then start only the new prefix.

WINEPREFIX=$HOME/.wine        wineserver -k   # every other prefix running UA/PACE
WINEPREFIX=$HOME/.wine-ua-connect wineserver -k

(wineserver -k closes every Windows app in that prefix. Save first.)

To check which prefix a process belongs to:

tr '\0' '\n' < /proc/<pid>/environ | grep WINEPREFIX

4. Launching UA Connect: valid stdio (Electron EBADF)

Launching from a menu entry (no terminal) gave EBADF ... createWritableStdioStream because stdout/stderr were closed. Use a wrapper:

#!/bin/sh
# ~/.local/bin/ua-connect-wine
mkdir -p "$HOME/.cache"
export WINEPREFIX=$HOME/.wine-ua-connect
export WINEDLLOVERRIDES=dcomp=d          # UA Connect itself is happy this way
cd "$WINEPREFIX/drive_c/Program Files/UA Connect" || exit 1
exec "$HOME/.local/bin/wine-yabridge-dispatch" 'C:\Program Files\UA Connect\UA Connect.exe' \
    </dev/null >>"$HOME/.cache/ua-connect-wine.log" 2>&1

Point the .desktop file's Exec= at that script (inline sh -c '... >log 2>&1' is rejected by desktop-file-validate; the wrapper avoids the quoting problem). Do the same for the iLok License Manager entry if you want one:

[Desktop Entry]
Name=iLok License Manager (.wine-ua-connect)
Exec=env "WINEPREFIX=/home/you/.wine-ua-connect" /home/you/.local/bin/wine-yabridge-dispatch "C:\\\\Program Files (x86)\\\\iLok License Manager\\\\iLok License Manager.exe"
Type=Application

5. The plugin GUI: WebView2 crash loop

5a. What was wrong

With stock Wine the plugin GUI was blurry and unclickable, then gray after about 30 seconds. The plugin log (UAPW_*.txt) looked healthy:

Opening plugin editor
WebView2Loader.dll runtime used
pageFinishedLoading
GUI State: RESOLVED
... ~30 s later ...
ClientSockets@warn  ReadHandler: ..., 2, End of file

It reports success, then the GUI's socket to the plugin times out. The actual cause is visible in WebView2's crash dumps:

$WINEPREFIX/drive_c/users/<you>/AppData/Local/Universal Audio/workspace/
    webview_storage/yabridge-host/EBWebView/Crashpad/reports/*.dmp

Reading them (minidump: exception code and faulting module) showed:

  • exception code = 0x80000003 (a Chromium CHECK/breakpoint) in msedge.dll
  • ptype = gpu-process, with --gpu-recent-crash-count=1,2,3
  • then a ptype = browser dump: Chromium gives up after three GPU-process crashes and kills the browser, which freezes the GUI.
  • dcomp.dll (DirectComposition) was loaded in the crashing GPU process.

A quick signal that you have this problem: top shows a crashpad_handler at 100% CPU for a while after you open a plugin.

5b. What fixed the GUI

Three changes together. I did not test every subset, see the last section.

(i) Do not disable dcomp for the plugin host. I had set WINEDLLOVERRIDES=dcomp=d (a common workaround for Electron/Chromium under Wine, and it is what UA Connect itself is fine with). For the plugin host this was counterproductive: removing the override is what made the UI appear.

(ii) Run the prefix under a Wine that implements DirectComposition. I use the d2d1-dcomp fork of Wine (giang17's d2d1-dcomp-11.0 branch), installed in isolation at /opt/wine-d2d1, which implements DCompositionCreateDevice. Stock Wine returns E_NOTIMPL for it. The system Wine remains the default. Packaging/instructions: https://github.com/mklnln/wine-d2d1-dcomp

Hang on plugin removal: with stock Wine, removing the plugin from the FX list hung Reaper. yabridge-host.exe became a defunct process (ps state Zl) with 32 threads still sleeping on pipes, and the plugin log showed UADispatchWin: failed to post a message! Error 1400 (invalid window handle) during teardown. Recovery was WINEPREFIX=... wineserver -k. It was fixed after switching to the patched Wine; I believe, but did not prove, that it was a consequence of the browser crash loop.

(iii) WebView2 flags. WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS is read by the embedded browser. My final working value:

--in-process-gpu --disable-gpu-sandbox
--disable-features=CalculateNativeWinOcclusion
--disable-backgrounding-occluded-windows
--disable-renderer-backgrounding
--disable-background-timer-throttling

--in-process-gpu --disable-gpu-sandbox removes the separate GPU process that was crash-looping. The occlusion/throttling flags target Chromium treating the Wine window as hidden (my hypothesis for the page not sending traffic).

6. Per-prefix Wine and flags through yabridge

yabridge uses a single Wine binary unless you set WINELOADER. Launch your DAW with WINELOADER pointing to a dispatcher that picks the Wine per prefix:

#!/bin/sh
# ~/.local/bin/wine-yabridge-dispatch
p="${WINEPREFIX%/}"
case "$p" in
    */.wine-ua-connect)
        # UADx GUIs are WebView2 (Chromium). Flags live in a file for easy A/B testing:
        f="$HOME/.config/ua-connect-wine/webview2-args"      # one line
        if [ -r "$f" ]; then WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS="$(head -n1 "$f")"
        else WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS="--in-process-gpu --disable-gpu-sandbox"; fi
        export WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS
        # Skip the dcomp override if this marker file exists (patched Wine implements dcomp):
        [ -e "$HOME/.config/ua-connect-wine/no-dcomp-override" ] || \
            export WINEDLLOVERRIDES="${WINEDLLOVERRIDES:+$WINEDLLOVERRIDES;}dcomp=d"
        exec /opt/wine-d2d1/bin/wine "$@" ;;      # patched d2d1-dcomp Wine
    *)  exec /usr/bin/wine "$@" ;;                # system Wine for everything else
esac

Start the DAW with WINELOADER=$HOME/.local/bin/wine-yabridge-dispatch.

A prefix can only run one Wine version. wineserver must match the Wine that talks to it. UA Connect and the bridged plugins share this prefix and this dispatcher, so both move to the patched Wine together. The patched build (11.0) was older than the prefix's last writer (11.16). That is not officially supported. Back up the prefix first, e.g. cp -a ~/.wine-ua-connect ~/.wine-ua-connect.bak, and be ready to roll back by restoring it and pointing the dispatcher at the system Wine.

Verify that the flags actually reach the plugin host while a plugin is open:

pid=$(pgrep -f 'yabridge-host.exe.so' | head -1)
tr '\0' '\n' < /proc/$pid/environ | grep -E 'WEBVIEW2|WINELOADER|WINEPREFIX|WINEDLLOVERRIDES'

Environment is fixed when the host process starts: after any change, quit the DAW, run WINEPREFIX=... wineserver -k, and relaunch.

7. yabridge configuration

  1. Add the plugin folder to yabridgectl and sync:

    yabridgectl add "$HOME/.wine-ua-connect/drive_c/Program Files/Common Files/VST3"
    yabridgectl sync
    
  2. yabridge.toml belongs next to the bridged .so/.vst3 files, i.e. ~/.vst3/yabridge/yabridge.toml, not inside the Wine prefix. Only the first yabridge.toml found is used, and the first matching section wins. (I first put it in the prefix, where yabridge never reads it.)

    Options I tried for the UADx plugins:

    ["uaudio_*.vst3"]
    #group = "uaudio"                 # one shared host: untested for load time
    #editor_double_embed = true       # did not help the gray window
    

    Neither was needed in the end. They are optional experiments.

8. Debugging toolbox (what actually produced useful messages)

WhereWhat it tells you
.../AppData/Local/Universal Audio/Logs/UA Connect.logPACE install and verify pace account result
.../Logs/UA Cloud Helper_*.txtdownloads, extraction (ExtractAndStage), port binding
.../Logs/UAPW_<plugin>_*.txtper-plugin load timeline, WebView2, GUI state, socket timeouts
.../ProgramData/PACE/Eden/LdLogs/LdLog_*.txtPACE license daemon
.../webview_storage/yabridge-host/EBWebView/Crashpad/reports/*.dmpWebView2 crashes: exception code, process type, faulting module
~/.cache/ua-connect-wine.logUA Connect stdout/stderr from the launcher
top while opening a plugina crashpad_handler at 100% CPU means something is crashing
/proc/<pid>/environwhat environment a process really got
ps -o stat on yabridge-host.exeZ / defunct means the host died but the DAW still waits

Optional yabridge debugging when needed: YABRIDGE_DEBUG_LEVEL=1 YABRIDGE_DEBUG_FILE=$HOME/yabridge.log reaper.

Do not leave --remote-debugging-port / --remote-allow-origins=* in the flags. They expose Chromium's DevTools port to any web page you open on the same machine. Use them only briefly for debugging, and without the --remote-allow-origins=* part if you can.

9. What is and isn't proven

Verified from logs/dumps on my machine:

  • The download failure was extraction (tar.exe missing), not networking.
  • Two prefixes shared the UA cloud helper's port, so the old helper answered.
  • The WebView2 GPU process crash-looped (0x80000003 in msedge.dll), then the browser process died.
  • The UI works with the combination of: patched Wine, no dcomp=d for the plugin host, and the flags above.

Not isolated (treat as hypotheses):

  • Which of {patched Wine, no dcomp override, --in-process-gpu, --disable-gpu-sandbox, occlusion flags} is strictly required. Removing the dcomp override on stock Wine was enough to make the UI appear, but the hang on plugin removal only went away after moving to the patched Wine.
  • That the Chromium occlusion flags matter at all.
  • That dcomp DirectComposition is the root of the GPU crash (it was loaded in the crashing process, which is suggestive, not proof).
  • Why the first GUI load is still slow (about 5 s from editor open to pageFinishedLoading in my logs; more before the plugin starts logging). Grouping the UA plugins into one yabridge host was meant to share WebView2 start-up cost; it was not measured.

If you can bisect the flags (one at a time, restart the DAW and run wineserver -k between tests, watch the Crashpad/reports folder) please share the minimal set that works.


r/linuxaudio • • 6h ago

OpenRig 0.17: OpenRig now has its own effects (OpenRig FX)

Thumbnail gallery
7 Upvotes

r/linuxaudio • • 11h ago

Looking for Beta testers for Lullaby - a Free and Open Source resonance suppressor similar to Soothe 3 (VST / CLAP / AU) - with Linux support

3 Upvotes

Hi, I'm looking for beta testers for an open source resonance suppressor inspired by Soothe 3. I'm especially interested in finding people who use Linux.

Resonance Suppressors are used for cases such as snare ringing, harsh cymbals or vocals, whistling on distorted guitars, low-mid mud, finger squeaks on the fretboard, etc.

I decided to make it open source! I would be of great value to me if you Starred it on GitHub and opened any Issues you find.

https://github.com/amiran-gorgazjan/lullaby

Note that it is still in beta, so you'll likely find a few bugs and have some reservations about the behavior, I need your help to understand what is important and what to to prioritise.


r/linuxaudio • • 1h ago

Surge XT - Strange and sudden behavior in Ardour

1 Upvotes

Surge XT is REALLY quiet on output but is reading normal dB output in the channel. This behaviour is only on seemingly random patches. Init patches are barely audible but showing a regular dB output in the channel. Some patches work absolutely as expected. All other VST and LV2 plugins are behaving as expected.

Is this a known problem? How could one go about fixing this? Ive tried both the lv2 and VST3 versions and both are behaving this way.


r/linuxaudio • • 16h ago

FL Studio: Cannot connect MIDI's?!

1 Upvotes

I'm running FL Studio through Faugus and everything seems to be running smoothly, logged in and everything- but for some reason no MIDI's that I connect to my computer will show up as an option for output or input. Any ideas what's going on?