yabridge
yabridge copied to clipboard
robbert-vdh
Plugin Scan Failing in REAPER
Thanks for giving yabridge a shot!
- [X] I read through both the troubleshooting and the known issues sections, and my issue wasn't listed there
Problem description
Plugin scan is failing in REAPER.
What did you expect to happen?
On hitting Clear Cache and Rescan Plugins in REAPER I expected the plugin scan to complete succesfully and find the plugins I had converted.
What actually happened?
plugin scan fails. I get a System notification saying: "Failed to start the Wine plugin host. Check yabridge's output for more information on what went wrong." and the converted plugins do not show up in the FX list. I re-ran REAPER with debug level 2. Debug output below
Operating system
Gentoo
How did you install yabridge?
directly from release page
yabridge version
4.0.2
yabridgectl version
4.0.2
Wine version
Wine Staging 7.14
Plugin
TDR Molot and FabFilter Pro Q3
Plugin type
VST2
Plugin architecture
64-bit
Host
REAPER v6.66
Desktop environment or WM
No response
GPU model
No response
GPU drivers and kernel
No response
Debug log
Anything else?
one question i have that is not clear from the README - is WINE-ASIO required for yabridge to work?
This is an awesome project that works great in AV Linux. Just trying to get it set up in Gentoo as well.
Have you tried a clean Wine prefix (move ~/.wine and install a single plugin like ValhallaSupermassive)? And do things like winecfg work? There's nothing obvious in that log output.
one question i have that is not clear from the README - is WINE-ASIO required for yabridge to work?
No, you don't need wineasio.
Yes I have tried a fresh wine prefix, using the method you describe. winecfg works as well with no errors or abnormal output. I have the same issue with Supermassive, and the log looks the same.
Thank you for the clarification on wineasio.
I have also tried some of the troubleshooting steps like running yabridge-host.exe directly and the output shows just like the README says it should so I don't think it is a yabridge issue?
Do you think it is worth trying a different release of wine-staging?
I am installing another daw (ardour) to see if it is a REAPER issue.
I appreciate your time!
And you get similar output with a new Wine prefix? The Failed to resolve your host name IP error is also kind of suspect because I've never seen that error before. Presumably the issue happens when either loading the library or connecting to the sockets, but there's nothing in the log that points to anything in particular.
Yeah you can try another Wine release, and make sure you have all optional dependencies for Wine installed (except for things like dosbox and zapcc).
Since 1 week I have been experiencing a similar problem on my home computer running latest Arch. I suspect the switch from pipewire-media-session to wireplumber to be the problem.
In my case, Reaper succeeds to scan plugins when I switch its audio device from Jack to Pulse. That is not a viable solution for me but it may give us a hint. So, could you please try it with Pulse?
@fd-sd Are you sure you get the exact same output? Preparing to load XXX plugin at 'YYY', followed by a million fixme:unwind:virtual_unwind calling personality routine in system library not supported yet fixmes? There's probably something else going on. REAPER's audio backend has zero impact on how it interacts with plugins/yabridge, and a large chunk of yabridge users use PipeWire with Wireplumber (including myself).