yabridge plugins fail to load after update to wine 9.5-9.7 #320
Comments
|
I have had a very similar issue running BitWig 5.1.6 - after running from the terminal and attempting to load a VST or CLAP onto an audio track I get the following:
|
|
Same here. I was in production (using UbuntuStudio 23.10) and yabridge stopped working. So I downgraded to Wine Staging 9.4 and will uphold until any news about the issue. |
|
@rolodoom: Just so you know, one of the current wine-staging patches prevents some VST plugins from working, including Plogue sforzando and ARIA Engine. This was broken in wine-staging 9.3, but I'm not sure if it's been fixed yet in 9.4. Anyway, you may wish to downgrade to 9.2 if any of your plugins are affected. Wine-devel is not affected. |
|
Also seeing the same problem on Kubuntu 23.10 / Wine Staging 9.5 (was working prior to today's update). Using Cheery Audio plugins as an example, I can run their stand-alone app via the 'wine directory fine, but when loaded as a VST the same plugin will crash the VST host or plugin sandbox (confirmed with Reaper, Waveform, Studio One, and Bitwig). |
|
Same issue here with Wine Staging 9.5. It was working fine with Wine Staging 9.4. |
Update:x86 plugins are loading fine. |
|
Wine 9.5 seems to have broken Winelibs, at least on 64-bit Wine. You'll need to downgrade to an earlier version of Wine for now. I'll do some digging and create a Wine bug report if there's not one already. Last time this has happened has been a while ago, but Winelib isn't a very widely used Wine version and it usually not tested, so these things happen from time to time. |
|
Another temporary solution would be to edit wine-mirror/wine@85d029e is the relevant Wine commit that caused this to break. EDIT: Created a bug report here: https://bugs.winehq.org/show_bug.cgi?id=56483 |
|
I found a similar issue with wine-staging 9.5 after the latest update. When I update Yabridge at the end I receive a message: Reading the entire thread I decided to rollback Wine to 9.4 and now everything works really nicely. I'm actually on Debian 12 Stable with Xfce4. To downgrade Wine to a previous version is pretty much simple on Debian. Just remember that a full wine-staging install include these four packages:
To downgrade the Wine Staging version, all the files necessary for the downgrade must be listed in the installation command like this in a single line:
Hope that helps. Thanks for Yabridge, I love it |
Thanks for the info. I finally installed winehq-stable v9.0 'cause some other software won't work with staging. As far as I checked, the plugins I used are working. |
|
@robbert-vdh I'd recommend pinning this issue and making the current incompatible version displayed more prominently on the Github page. For Debian users, I recommend holding the packages back until a new WINE version is available.
|
|
Having with same issue with wine-staging 9.6. Had to revert back to 9.4. |
robbert-vdh
changed the title
|
Just a note to say that wine 9.7 is out, and still appears to be broken. |
|
Yes, the MR that would fix it again has still not been merged. There doesn't seem to be a clear time frame on when that will happen because there's still some concerns that need to be addressed. |
what concerns:? |
|
I'm completely baffled by this, but I "accidentally" tried running a VST that has been crashing since this issue was reported after updating to the ArchLinux wine 9.7-1 package. (Long story, but I had done a full Well, I'm somewhat glad I did... The problem plugin (Thimeo StereoTool) which was full on crashing Reaper on ArchLinux now loads against wine 9.7-1 at least for my specific use case on my specific machine. However, I still have another laptop at home that the plugin still crashes on (it's on ArchLinux as well and on that machine I'm forced to re-compile wine 9.4-1). Maybe it's the specific plugin that I'm using that is not so much dependent on the problem code, but I figured I would share my experience. Hopefully this is helpful and not just a spam comment (let me know if it is and I'll delete it). HUGE Thank you to the yabridge development team! This project/code is AMAZING! Letting us use windows VSTs/VSTi's on Linux! |
Doesn't winehq-stable affect Yabridge? |
|
Hi, thanks for this thread.
How can i do it? Can i edit the single file from source and recompile only this? Or i will wait for the MR. Thanks! |
robbert-vdh
changed the title
|
With the merge of https://gitlab.winehq.org/wine/wine/-/merge_requests/5400 this issue is now resolved again for Wine 9.8 onwards. |
|
Tested on wine 9.8, this is fixed now. Thanks for the update |
|
Wine 9.9 KDE Neon, still same issue. IDK it is only me or not. Edit: In the KDE Neon, libpoppler-glib8 packages are still damaged and you have to execute I still getting the error and I really sick of this, I think maybe I should develop something too. |
Thanks for giving yabridge a shot!
Problem description
After upgrading from wine-devel 9.4 to version 9.5, trying to use a plugin through yabridge crashes REAPER. Running REAPER from the terminal, I get the following output when it crashes:
Running yabridge in debug mode doesn't generate any more info than what is above, so I have not included it.
Running
yabridgectl syncgenerates the following output:Workaround
Downgrading wine-devel packages to version 9.4 solves the issue.
What did you expect to happen?
The plugin should load and produce audio.
What actually happened?
REAPER crashes.
Operating system
KDE neon User Edition 6.0
How did you install yabridge?
from the releases page
yabridge version
5.1.0
yabridgectl version
5.1.0
Wine version
Wine Development 9.5
Plugin
any
Plugin type
both VST2 and VST3
Plugin architecture
64-bit
Host
REAPER v7.11
Desktop environment or WM
No response
GPU model
No response
GPU drivers and kernel
No response
Debug log
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: