Laggy plugin UI editors (arch+wayland+pipewire+bitwig)

[crsaracco]

Thanks for giving yabridge a shot!

• I read through both the troubleshooting and the known issues sections, and my issue wasn't listed there

Problem description

Tried with two demo plugins: Phase Plant and Chromaphone 3. Plugins load fine and produce sound.

However, there seems to be a few UI (editor) related issues while working with the VSTs. Every once in a while, my entire computer hangs for ~2sec (I've seen as little as ~0.5sec up to ~1.25min(!) though), usually when trying to work with the UI editor of the plugins.

• I notice this tends to happen frequently when I move my mouse between the VST and some other window (or vice-versa).
• It also happens frequently when I'm messing around with UI knobs.
• My entire computer will become graphically unresponsive, but I've noticed that audio still plays assuming it doesn't come from the qwerty keyboard (eg. MIDI clips from the arranger while Bitwig is in play mode, and a USB MIDI piano keyboard, both will still produce sounds when the graphics are hanging).
• Note: on Sway, hovering over a window also focuses it, so maybe it's some weirdness with switching window focus?

What did you expect to happen?

No graphical hanging

What actually happened?

Graphical hanging :(

Operating system

Arch Linux

How did you install yabridge?

AUR

yabridge version

aur/yabridge-bin 5.1.0-1

yabridgectl version

aur/yabridge-bin 5.1.0-1

Wine version

wine-8.21 (Staging)

Plugin

various

Plugin type

VST3

Plugin architecture

64-bit

Host

Bitwig Studio 5.1.3

Desktop environment or WM

Sway

GPU model

AMD Radeon RX 7900 XTX

GPU drivers and kernel

extra/mesa 1:24.0.1-1

Debug log

No response

Anything else?

• I produced a yabridge.log, but it's ginormous (504k lines of text, ~50MB, too big for Github to handle). I uploaded it to my own web server instead: https://crs.io/yabridge.log. I don't even know if graphics hanging would show up there, lol.
• I checked out the "troubleshooting common issues" and "known issues and fixes" sections, but nothing stands out as fixing my particular issue. I'd be kinda surprised if nobody else has ever seen this issue before, though, because I don't think I've done anything particularly crazy with my setup.
  • I installed DXVK, but I honestly don't know if I set it up right. This seems like not quite my issue anyway since the GUI often updates fine.
  • "Hide Wine version from applications" sounds like my issue, but following that didn't fix my problem.
  • I've tried the hide_daw option for Chromaphone 3; doesn't seem to have helped.
  • Everything listed on this bug report is from a clean Wine prefix.
  • I appear to have set up realtime privileges correctly.
  • I didn't try out anything with kernel parameters or custom wine forks yet because that seems like a lot of effort for something that I don't know will fix my issue. LMK if you think something there will help and I'll try it out.
• Just in case it's useful: whenever I delete a Chromaphone 3 device/track, I always get a popup saying "The program start.exe has encountered a serious problem and needs to close." -- some Wine-related issue.
• I tried real quick in Gnome (wayland) and Gnome (x11) and had some other issues (seemingly to do with mouse pointer location incorrectness), but I don't think I saw lagginess issues. I'll try again after posting this and report back, but I'd rather not have to change my entire setup if it turns out Sway is the issue :(
• [edit: findings from Gnome]
  • Now when I try on Gnome again, I get different results than what I tried before. Results below.
  • With Gnome on Wayland, I see the "Low RTTIME limit detected" issue and the plugin crashes immediately. This doesn't happen on Sway, so I don't know what the difference is between that and Sway. If I wanted to switch to Gnome I could consider looking into this.
  • With Gnome on X11, the plugins seemingly work fine now after testing them for ~10 mins (except I still get the start.exe crash messages whenever I close Chromaphone). I guess I could just switch back to Gnome+X11, but I'm interested in if there are any fixes for Sway.