robbert-vdh / yabridge

A modern and transparent way to use Windows VST2, VST3 and CLAP plugins on Linux
GNU General Public License v3.0
2.45k stars 64 forks source link

Yabridge doesn't work in Kubuntu 24.10 in Ardour, Bitwig Studio and Presonus Studio One #377

Open Skygge666 opened 1 week ago

Skygge666 commented 1 week ago

Thanks for giving yabridge a shot!

Problem description

In the new (K)ubuntu 24.10 (Oracular oriole) all plugins I have (MTPower Drumkit, EZDrummer 3) cause these DAWs to crash: Ardour, Bitwig Studio and Studio One. Before system upgrade, under 24.04 everything was fine. Now If I add one of these plugins or try to rescan plugins, these DAWs take whole RAM (32G in my case) then crash. What's strange, under Reaper or Tracktion Waveform the plugins are working ok. Idk what happened. I waited for new wine release and proper Oracular repo, what happened today, but it changed nothing. Attached screenshot from Studio One but it looks the same for Ardour and Bitwig Studio.

obraz

What did you expect to happen?

I expected to load and run the plugins

What actually happened?

Ardour, Bitwig and Studio One start to consume all RAM available then crash.

Operating system

Kubuntu 24.10 (Oracular oriole)

How did you install yabridge?

binary from releases page

yabridge version

5.1.0

yabridgectl version

5.1.0

Wine version

winehq-staging 9.20~oracular-1

Plugin

MT Power Drumkit, EZDrummer 3 (demo)

Plugin type

VST3

Plugin architecture

64-bit

Host

Bitwig Studio, Ardour 8.10, Presonus Studio One 6.6

Desktop environment or WM

KDE Plasma 6.1 (Wayland)

GPU model

NVidia RTX 3060

GPU drivers and kernel

Nvidia drivers 555, Kernel 6.11-lowlatency

Debug log

No response

Anything else?

No response

vudone commented 6 days ago

Same problem here, in ubuntu 24.10.

I have just updated last night.. The wine-hq repositories (for oracular, the name of ubuntu24.10) installs winehq-9.20. I tried to downgrade winehq but it does not repair the problem.

In my case when i launch Ardour (with any yabridge plugin) it keep freezie. If i launch a new ardour project, ir works fine. In any moment I load a yabridge plugin, Ardour freezie.

I tried Ardour 8.6 and ardour 8.10, same issue

vudone commented 6 days ago

I tried to debug the code with gdb. This is whats gdb shows when the software keep Freezie. Seems like is the moment when i load Melodyne with yabridge. I dont know if this screenshots are usefull.

Captura desde 2024-10-21 10-12-56

Captura desde 2024-10-21 10-15-21

Captura desde 2024-10-21 10-16-16

vudone commented 4 days ago

The yabridge binary release didnt work in my ubuntu 24.10. I have compiled it in my computer (with winehq-9.20) and now seems to work

Skygge666 commented 4 days ago

Self-compiled Yabridge seems to work. Thanks @vudone for your tip.

mahlonsmith commented 4 days ago

Also just updated to Ubuntu 24.10, with the same problem under Ardour.

Another interesting note: Everything seemed fine using Carla as the plugin host. Memory bloat and scanning timeouts in Ardour.

Building yabridge from source, all good in both environments.

paulopinheiro commented 4 days ago

I confirm the bug in Ubuntu 24.10. The problem does not occur on Carla, Reaper, Muse, Waveform13 or even Audacity. It happens with Ardour and Mixbus. When you try to load the plugin, Yabridge isn't even called. Ardour is probably in a loop trying to load somehow, which increases memory and CPU use. That also happens when you try to scan the plugin as a new one to add to the Ardour cache list. But there's one more piece of information about it: if you try to scan the same plugin in the command line with ardour-vst-scanner it adds to the Ardour cache with no issues. So maybe it's something about the shell environment?

paulopinheiro commented 4 days ago

Unfortunately, I was unable to compile yabridge from source. The process ends without errors, but at the end I don't have all the expected generated files (there is no yabridgectl, for example).

vudone commented 3 days ago

Hi @paulopinheiro. Im not in home now, but i think that yabridge works for u. Yesterday when I compiled yabridge i had to compile 2 packages really.

In the root folder, with meson and ninja, u compile some files. thats ok, its part of the project.

In order to compile the yabridgectl bin u need to access to the YABDRIGEFOLDER/tools/yabridgectl folder.

and there launch:

$ cargo run --release

yabdrigectl will be compiled. Copy it with the rest of yabridge files (probably ~/.local/share/yabridge)

And thats all.

eugenialoli commented 3 days ago

I hope the developer provides us with a new ubuntu binary package soon. There isn't one for the latest released version and compiling it from source is a big complicated on my system.

Skygge666 commented 3 days ago

As a temporary workaround you can download working yabridge for 24.10 (64-bit only!) compiled by me from my homepage. I will remove this link as soon as developer makes new release. https://www.skygge.com/pliki-do-pobrania

Skygge666 commented 3 days ago

List of files included:


libyabridge-chainloader-clap.so
libyabridge-chainloader-vst2.so
libyabridge-chainloader-vst3.so
libyabridge-clap.so
libyabridge-vst2.so
libyabridge-vst3.so
README.md
yabridgectl
yabridge-host.exe
yabridge-host.exe.so

You can install this the same way as usual binary release. If you have installed yabridge already - just replace these files and run yabridgectl sync

paulopinheiro commented 3 days ago

Hi @paulopinheiro. Im not in home now, but i think that yabridge works for u. Yesterday when I compiled yabridge i had to compile 2 packages really.

In the root folder, with meson and ninja, u compile some files. thats ok, its part of the project.

In order to compile the yabridgectl bin u need to access to the YABDRIGEFOLDER/tools/yabridgectl folder.

and there launch:

$ cargo run --release

yabdrigectl will be compiled. Copy it with the rest of yabridge files (probably ~/.local/share/yabridge)

And thats all.

Thank you very much. That's the missing part. I didn't find those steps on README. I'll still have to compile the 32 bits modules but the 64 bits based plugins are already working.