Is this project still alive? Last release was 11/'24 - wine compatibility stands still on wine v 9.21

[BMuXBeats]

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

Do you still maintain this project? Is it still active? 🤔

I ask, because the wine compatibility hangs since more than over a year at wine v 9.21.

Are there any updates planned for the near future?

What did you expect to happen?

I expect this should be answered by the developer. 😉

What actually happened?

n/a

Operating system

Arch Linux

How did you install yabridge?

AUR package

yabridge version

5.1.1-5

yabridgectl version

5.1.1-5

Wine version

wine-9.21 (Staging)

Plugin

every

Plugin type

every

Plugin architecture

64-bit

Host

every

Desktop environment or WM

KDE Plasma 6.5.2

GPU model

NVIDIA RTX 3050

GPU drivers and kernel

No response

Debug log

No response

Anything else?

No response

[ArtikusHG]

From my understanding the author doesn't have enough time to work out a solution to using newer wine versions, because it requires quite a lot of effort and debugging to get right. There is a development branch for this, but it's been contributed by rbernon of CodeWeavers and Asahi Lina. It fixes some of the issues and makes new wine versions usable, but not completely - some daws have random issues and you have to move the window at least once before it becomes interactive again. There is also the possibility of compiling a patched wine version commenting some code that prevents yabridge from working properly. Point is, some stuff is happening, but it's not much. Maybe eventually someone will come and contribute the final, production-ready fix, or maybe the author will find time for it. As of right now, you can either use an older wine version, the development build of yabridge, or a patched version of wine.

[QXR9]

As a Fedora user, Wine-TkG COPR was the ultimate solution for us but with fedora 43 all of the solutions are just trashed. I have completely dissolved from my music workflow, I want to contribute to project soooo much but I have no time too. Thats why I understand developer so much and I appreciate him. If somebody thinks of contributing this project, then it's time. Maybe AI helps, who knows.

[robbert-vdh]

From my understanding the author doesn't have enough time to work out a solution to using newer wine versions, because it requires quite a lot of effort and debugging to get right. There is a development branch for this, but it's been contributed by rbernon of CodeWeavers and Asahi Lina. It fixes some of the issues and makes new wine versions usable, but not completely - some daws have random issues and you have to move the window at least once before it becomes interactive again. There is also the possibility of compiling a patched wine version commenting some code that prevents yabridge from working properly. Point is, some stuff is happening, but it's not much. Maybe eventually someone will come and contribute the final, production-ready fix, or maybe the author will find time for it. As of right now, you can either use an older wine version, the development build of yabridge, or a patched version of wine.

Yeah pretty much exactly this! Despite Rémi's and Lina's best efforts to try and help out with the alternative edittor embedding mode used in the wine-10-embedding branch, it still doesn't work nearly as well as the old style of embedding with Wine 9.21 and below did. I was silently hoping Wine would roll back some of the x11drv changes that broke the old approach, but this didn't happen. And I just haven't had a ton of time and motivation to try and polish this new approach further.

But yeah, it's been so long at this point that it's probably better to compromise on a worse experience that works with the latest Wine version over a better version that does not. I'll try find some time to iron out some of the biggest glitches and issues with the new embedding approach before finally merging it, but it's been an uphill battle last time I spend a considerable amount of time on this, so any help trying to get this to a better state would be very much appreciated!

[ArtikusHG]

it still doesn't work nearly as well as the old style of embedding with Wine 9.21 and below did

I've been using the experimental branch for the past 5 months or so and it's working great, except for the fact you have to move the window to get it to apply the correct coordinates, so I wouldn't call it particularly bad. Also releasing this new embedding option might attract contributors! (I wish I could help since I use this software basically daily and semi-professionally, but I don't have enough knowledge :/)

[bidinou]

Hi ! Just tried "yabridge-win10-git" (AUR/Archlinux) and it does work under Bitwig 5.x. I didn't have to move my windows first. (only have alien Arturia plugins, the rest is native).

What is annoying though, is the VST windows remain above the Bitwig window. I can move them to a secondary virtual desktop (KDE) but each time a new window pops up, it brings back all VST windows back to the Bitwig virtual desktop.

Well, we're almost there it seems ! (the other remaining issue being my Keylab screen doesn't receive the data from the Arturia VST (in standalone mode, it displays various information), probably because Bitwig has some kind of exclusive access to it)

Thanks again, Robbert ! :)