(SOLVED) yabridge/wine vst ui bug

[asbak]

I guess it is a problem with the current versions, I will try using dxvk and a version of wine prior to 9.22 since, ironically I upgraded to wine 10 and it was even worse. if it works I might post it here in case someone else has the same problem

anyway, as they said, it's not worth wasting time on this. in the end the only real option would be to have a dual-boot

Or a second Doze VST box. You can always netjack into it from the Linux box.

And another guy who posted on here ended up running his Doze VSTs in a Doze VM on his Linux box, he seemed to be happy enough with the results.

[Linuxmusician01]

I guess it is a problem with the current versions, I will try using dxvk and a version of wine prior to 9.22 since, ironically I upgraded to wine 10 and it was even worse. if it works I might post it here in case someone else has the same problem

anyway, as they said, it's not worth wasting time on this. in the end the only real option would be to have a dual-boot

Or a second Doze VST box. You can always netjack into it from the Linux box.

And another guy who posted on here ended up running his Doze VSTs in a Doze VM on his Linux box, he seemed to be happy enough with the results.

Hmmmm. Say you're making music in a Linux DAW on Linux. How would running VT's on a Windows machine (virtual or real) help? I wouldn't know how to use/sync/start/stop VST's that are on another computer from my DAW...

Another solution: buy real synths and stomp-boxes and go DAW-less. But that sorta would make this forum obsolete wouldn't it...?

[asbak]

Hmmmm. Say you're making music in a Linux DAW on Linux. How would running VT's on a Windows machine (virtual or real) help? I wouldn't know how to use/sync/start/stop VST's that are on another computer from my DAW...

Another solution: buy real synths and stomp-boxes and go DAW-less. But that sorta would make this forum obsolete wouldn't it...?

Yes the Doze route is not really for me either, I just pointed out which methods are possibly more reliable.

Haha no man the forum wouldn't be obsolete, DAW recording is the main driver for most people and for that Linux Audio is relevant.

[tavasti]

Hmmmm. Say you're making music in a Linux DAW on Linux. How would running VT's on a Windows machine (virtual or real) help? I wouldn't know how to use/sync/start/stop VST's that are on another computer from my DAW...

Audiogridder is solution for that. Another solution would be running audio and midi over netjack (not sure does it include midi also?), and handle UI on windows.

[Linuxmusician01]

Hmmmm. Say you're making music in a Linux DAW on Linux. How would running VT's on a Windows machine (virtual or real) help? I wouldn't know how to use/sync/start/stop VST's that are on another computer from my DAW...

Audiogridder is solution for that. Another solution would be running audio and midi over netjack (not sure does it include midi also?), and handle UI on windows.

[off topic?] Thank you for those tips! Netjack seems not to be developed anymore and does not support Midi. However, Audiogridder supports Midi and audio. I think it has been developed for usage on Linux to solve the VST problem, am I right? I'm a bit confused because the server is only available for Windows and MacOS, not Linux.

Do you think Audiogridder will work with Windows in a virtual machine (Virtualbox)?

I might have to start a separate topic on this...

[tavasti]

I think it has been developed for usage on Linux to solve the VST problem, am I right? I'm a bit confused because the server is only available for Windows and MacOS, not Linux.

Do you think Audiogridder will work with Windows in a virtual machine (Virtualbox)?

I might have to start a separate topic on this...

Yeah, audiogridder is for using plugins from windows or mac in linux. And 'server' is the part that hosts plugins. So with linux-server, you could even use plugins from another linux computer (load sharing). IMHO, windows server is most important.

Most likely audiogridder would work also in VM, but performance is another question. And I think there is already few threads about Audiogridder already, but pick your poison are you starting new or continuing old.

[Kott]

I'm a bit confused because the server is only available for Windows and MacOS, not Linux.

COMPATIBILITY
Server: macOS 10.7+ (Intel/Apple), Windows 7+, Linux 64bit (experimental)

[GMaq]

We can't keep using Wine 9 for ever.

No not forever, but literally for years.. I don't get all the angst and hand-wringing about these topics.. Get a version that works with your most vital Plugins and forget the notion that all of them are EVER going to work with ANY version of Wine then pin it and use it as long as you need to. On my Studio Box I install a tested working version from WineHQ and using 'apt-download' I download all the relevant Wine Packages of that version and archive them somewhere so I know I have them on hand. If I unpin and try a newer version and it doesn't work with the WineHQ Repo you can always roll back and worst case I have my archived working version I can install and get back to business.

Next if your Win Plugs are working completely as you expect then don't be trigger happy to update to the latest versions because it's possible the Plugins themselves may stop working or their installers and licensing schemes will stop working. If it works just leave it alone I also don't understand what the problem with "if it ain't broke don't fix it" is with people.

Wine is a self-standing thing that doesn't need to be blanket upgraded with every other Package on the system at all especially on Stable and LTS Distros, you could literally never update Wine and it won't break over the whole service life of the Distro which for most LTS/Stable Distros is like 5 years..

[tavasti]

Wine is a self-standing thing that doesn't need to be blanket upgraded with every other Package on the system at all especially on Stable and LTS Distros, you could literally never update Wine and it won't break over the whole service life of the Distro which for most LTS/Stable Distros is like 5 years..

Yeah, true. Then have to compile 9.21 to new distro when updating.

Debian release coming next summer, so most likely I am upgrading next fall. Half years still, then time to find solution for myself...

[Linuxmusician01]

1. About Audiogridder. Linux support of its server is experimental which makes me think that the server part isn't meant for Linux. Is the rest?

2. About not upgrading. Alas, not an option because at a certain point (new) software won't work on an old system. They don't update Wine for nothing.

[GMaq]

Wine is a self-standing thing that doesn't need to be blanket upgraded with every other Package on the system at all especially on Stable and LTS Distros, you could literally never update Wine and it won't break over the whole service life of the Distro which for most LTS/Stable Distros is like 5 years..

Yeah, true. Then have to compile 9.21 to new distro when updating.

Debian release coming next summer, so most likely I am upgrading next fall. Half years still, then time to find solution for myself...

WineHQ usually also packages for Debian Testing, I haven't checked but there may already be a 9.21 package for Debian Testing which would be viable to use In next Debian Trixie release.

[GMaq]

@tavasti and others who may care..

For proof of concept I tried this (I'm currently based on Debian Bookworm):

I added the Debian Trixie repo from winehq.org:

https://gitlab.winehq.org/wine/wine/-/w ... ian-Ubuntu

I ran sudo apt update to reflect the new Repo change

Then I ran this command to download the Trixie version of Wine-Staging 9.21 into a folder:

Code: Select all

sudo apt download winehq-staging=9.21~trixie-1 wine-staging=9.21~trixie-1 wine-staging-amd64=9.21~trixie-1 wine-staging-i386=9.21~trixie-1 wine-staging-dev=9.21~trixie-1

shot-2025-02-26_17-27-46.jpg (173.05 KiB) Viewed 6674 times

Then I reverted to the WineHQ Bookworm Repos (which I have pinned at 9.21 Bookworm version)

Now if Trixie is released and they don't archive 9.21 I have a known-working version archived for many more years of Win Plugin enjoyment.. It is unlikely that the archived 9.21 will be removed from WineHQ but in my mind better to have it and know where it is..

[up3]

viewtopic.php?p=173353#p173353

[glowrak guy]

@asbak: Thank you for clearing that up. So it's not me. Not gonna waste my time on it anymore. The worst part is that it works one year w/ a certain version of Wine and next year it doesn't. We can't keep using Wine 9 for ever. What a SNAFU.

My best windows setup is an older AVLinux, with wine-staging 6.22, and kernel 5.15 that were preinstalled defaults. No pipewire anywhere!
I use the almost-newest Reaper for daw, letting Reaper experts prove the newest release for a couple weeks.[...]

Using a daw other than Reaper is a core problem for using windows plugins in linux.[...]

About Reaper and Windows VST's. Doesn't Linux native Reaper need bridging software like Carla or Yabridge? Or do you use Windows Reaper via Wine for Windows VST's?

I use both Reaper versions depending on what works. A few things work in windows Reaper via wine, that don't yet work in the linux Reaper.

The windows Reaper needs wineasio for the chosen asio driver. Choosing wasapi for me rarely works. I've also had little luck with recent versions of wine working correctly with wineasio, so I stick with older things that work OK.
Cheers

[Castle Studios]

The current common reason is that plugin GUI controls don't work with wine releases after 9.21

meaning

One possible way to work around this issue is to downgrade to wine 9.21 and Windows plugin GUI controls will typically work

There is a quick fix in wine, just start winecfg, choose the graphics rider and select "emulate virtual desktop" .
That helped to correct the mouse offset which makes it nearly impossible to operate any plugin.
I used the fix with yabridge and it worked fine.
Another issue i had with fabfilter plugin menuś could be fixed by using winetricks , change the settings graphics to X11 and renderer to no3d

I hope someone will take care of this soon, because its affecting nearly everybody who wants to do music production in Linux. With all the "nice" win11 stuff happening ( screenrecorder, KI stuff etc ) many many creatives are switching now, but even as Linux to me is the best way to go in audio production, this error is frustrating not only for Newbees and ex Windows users ...

It is really sad that this problem is not resolved since wine staging reached 10.5 until now.