[ANN] yabridge 5.0.3, fully functional with all Wine versions again (for now)

[robbert-vdh]

The latest release posts can be found here:

[ANN] yabridge 5.0, now with Windows CLAP plugin bridging support - 5.0.1, 5.0.2, 5.0.3
[ANN] yabridge 4.0, with chainloading, overhauled backend, and many UX improvements - 4.0.1, 4.0.2
[ANN] yabridge 3.8.0 - 3.8.1
[ANN] yabridge 3.7.0
[ANN] yabridge 3.6.0, October '21 edition
[ANN] yabridge 3.5.0, with lots of small fixes and a rewritten embedding implementation - 3.5.1, 3.5.2
[ANN] yabridge 3.4.0, with the first-ever Wine->X11 drag-and-drop support, a completely rewritten audio implementation, and many usability improvements
[ANN] yabridge 3.3.0, gotta go fast edition - 3.3.1
[ANN] yabridge 3.2.0, with greatly reduced VST2 bridging overhead and a lot of compatibility improvements and bug fixes

[ANN] yabridge 3.1.0, with 32-bit bitbridging for Windows VST3 plugins

yabridge is a modern and transparent way to use both 32- and 64-bit Windows VST2 and VST3 plugins on Linux as if they were native Linux VST2 and VST3 plugins.

I realize I've never done a proper release announcement for yabridge here outside of the call for testers before yabridge 3.0's release, so here is one! This is mostly a bugfix update, but this release does add a few small features and it also adds support for using 32-bit Windows VST3 plugins. The other important fix is a workaround for a bug present in Wine 6.5 and Wine 6.6 that would prevent yabridge from exiting.

A full changelog with an exhaustive list of changes, improvements and fixes can be found here:

https://github.com/robbert-vdh/yabridge/releases

[Soli Deo Gloria]

A fabulous work you're doing with this, Robbert! I'll update it... Thanks for the reminder.

[robbert-vdh]

Originally Posted by Soli Deo Gloria

A fabulous work you're doing with this, Robbert! I'll update it... Thanks for the reminder.

Apparently this change, which was meant as a workaround for a bug in the Algonaut Atlas 2.0 beta, also ended up fixing the loading and saving in Reason Rack. I don't think you've tried using Reason Rack but I know a few others that have, so it's good to know that that now also works! (I don't own the plugin, so I haven't checked it out myself yet)

[Soli Deo Gloria]

Yes, indeed I haven't been affected by the recent Wine bugs since I was on v6.0 for some months and only recently switched to 6.4 after I wrote to you.



One thing : in the AUR repo, the "normal" yabridge is still 3.02. Version 3.1 is yabridge-bin... Is it the same to update with yabridge or yabridge-bin?

[robbert-vdh]

Originally Posted by Soli Deo Gloria

Yes, indeed I haven't been affected by the recent Wine bugs since I was on v6.0 for some months and only recently switched to 6.4 after I wrote to you.



One thing : in the AUR repo, the "normal" yabridge is still 3.02. Version 3.1 is yabridge-bin... Is it the same to update with yabridge or yabridge-bin?

The yabridge and yabridgectl packages are at version 3.1.0!

[Soli Deo Gloria]

Alright... me and my insistence with pamac! Back to yay, then...

[Glennbo]

So I messed with Yabridge a little bit today, and while I've locked my WINE at 6.0 stable, it appeared to work. I did see it toss out a message that it didn't like me deciding what WINE I'm running.

Anyway, all my projects with Windows plugins seemed to load up and play fine, so I decided to try a plugin that has never worked with LinVST which is the Leslie FX portion of Native Instruments B4 Organ.

To my surprise, it loaded up with it's interface, and clicking the onscreen Fast/Slow switch worked, so I then linked the switch to midi CC64 which is damper pedal, and again it worked.

Lastly I recorded a short test playing guitar through the Leslie, and switching from slow to fast several times through the recording.

This is where there might be some kind of issue because it is a VST audio plugin that can be controlled by midi. On playback the midi CC64 is not seen at all by the plugin. It sees it when I press the pedal, and I see CC64 in the recorded data, but the plugin only sees live pedal presses and not recorded ones.

Using the VSTi which is The Leslie and the organ as an instrument plugin, the pedal works as do sliders I have assigned to the drawbars, so I know Yabridge can see recorded midi CC data, but evidently not with the VST audio FX Leslie section of the B4. One other item I noticed is that there is a hesitation between hitting play and the counter to start running when using this audio plug that also uses midi data.

[robbert-vdh]

I'm not a REAPER expert, but maybe that Leslie FX MIDI CC thing is related to how REAPER normally prebuffers audio processing? If it works with live MIDI then it should work with recorded MIDI, and it could just be that the plugin just has some compatibility issues with the way REAPER handles processing (since REAPER did not even exist yet when the plugin came out).

As for FM7, it seems like the plugin expects the last played MIDI event to stay alive indefinitely. I can't think of a reason why this could be, but the plugin segfaults during an audio processing cycle if there have not been any new MIDI events and the last sent MIDI event (from a previous processing cycle) has already been deallocated. I added a fix for this bug in FM7 in this commit. If you're on Arch or Manjaro, then you can build yabridge from this commit using the yabridge-git AUR package. Otherwise you can grab a binary from the automated builds page. Don't forget to rerun `yabridgectl sync` to finish the upgrade!

[Glennbo]

Originally Posted by robbert-vdh

I'm not a REAPER expert, but maybe that Leslie FX MIDI CC thing is related to how REAPER normally prebuffers audio processing? If it works with live MIDI then it should work with recorded MIDI, and it could just be that the plugin just has some compatibility issues with the way REAPER handles processing (since REAPER did not even exist yet when the plugin came out).

As for FM7, it seems like the plugin expects the last played MIDI event to stay alive indefinitely. I can't think of a reason why this could be, but the plugin segfaults during an audio processing cycle if there have not been any new MIDI events and the last sent MIDI event (from a previous processing cycle) has already been deallocated. I added a fix for this bug in FM7 in this commit. If you're on Arch or Manjaro, then you can build yabridge from this commit using the yabridge-git AUR package. Otherwise you can grab a binary from the automated builds page. Don't forget to rerun `yabridgectl sync` to finish the upgrade!

Thanks Robbert. I'm running Xubuntu 20.04. I went to this page,

https://github.com/robbert-vdh/yabri...ranch%3Amaster

but couldn't find the link to the zipped up binary.

Edit: I see this, "yabridge-3.1.0-10-gafefb72.tar.gz 4.6 MB"

after clicking into the Postpone Clearing link, but it is only text on the screen and not a clickable link to the file.

[robbert-vdh]

Originally Posted by Glennbo

Thanks Robbert. I'm running Xubuntu 20.04. I went to this page,

https://github.com/robbert-vdh/yabri...ranch%3Amaster

but couldn't find the link to the zipped up binary.

On that page you just have to select the latest commit, scroll down to the build artifacts, and download the correct binary (which would be yabridge-3.1.0-10-gafefb72.tar.gz at the time of writing). GitHub does require you to log in in order to download build artifacts like this. If you're not logged in to GitHub and don't want to create an account, then I can also upload the archive here.

[Glennbo]

Originally Posted by robbert-vdh

On that page you just have to select the latest commit, scroll down to the build artifacts, and download the correct binary (which would be yabridge-3.1.0-10-gafefb72.tar.gz at the time of writing). GitHub does require you to log in in order to download build artifacts like this. If you're not logged in to GitHub and don't want to create an account, then I can also upload the archive here.

Thanks Robbert. I have no account at GitHub and don't really want to give them any of my contact info. If it's a small enough archive to upload here, I'd be happy to grab it and verify that it fixes the issue.

[robbert-vdh]

Originally Posted by Glennbo

Native Instruments FM7 crashes Yabridge, but not LinVST.

Try the latest commit! It should work there (or at least it does on my machine). Links and instructions are in my last post.

[Glennbo]

Doesn't affect the bridging of plugins, they are all working fine, but I was getting an error at the end of running "yabridgectl sync" with winhq-stable so I installed winehq-staging.

Running it now with winehq-staging, I get this message which I believe is the same message as before, but now saying wine 6.7 (staging) instead of 6.0 (stable).

Finished setting up 47 plugins using copies (0 new), skipped 0 non-plugin .dll files

Warning: Could not run 'yabridge-host.exe'. Wine reported the following error:

00a4:err:rpc:I_RpcReceive we got fault packet with status 0x1c010003

This can happen when using a version of Wine that is much older than the version that has been used to compile yabridge with. Your current Wine version is '6.7 (Staging)'. See the troubleshooting section of the readme for more information on how to upgrade your installation of Wine

[robbert-vdh]

Originally Posted by Glennbo

Doesn't affect the bridging of plugins, they are all working fine, but I was getting an error at the end of running "yabridgectl sync" with winhq-stable so I installed winehq-staging.

Running it now with winehq-staging, I get this message which I believe is the same message as before, but now saying wine 6.7 (staging) instead of 6.0 (stable).

Are you by any chance using PipeWire? Yabridgectl will warn you when running ~/.local/share/yabridge/yabridge-host.exe fails, and it will print the warning you're seeing along with the last line of Wine's output. That's the warning you're seeing right now. It seems weird that running yabridge-host.exe would fail when running standalone when it runs just fine during actual plugin bridging though. Can you try running just ~/.local/share/yabridge/yabridge-host.exe (without wine in front of it) to see if that prints any errors? If everything's working correctly, the output should contain a line starting with 'Usage: yabridge-host.exe '. The reason I asked if you were using PipeWire is because I've only seen these 00a4:err:rpc:I_RpcReceive errors from PipeWire users. PipeWire/rtkit sets a limit on the amount of time a real time thread may spend without yielding to the scheduler, and certain plugins will thus get killed by the scheduler when they take too long to initialize from the audio thread. This is probably not what's happening here, but I've only ever seen those particular errors in the context of PipeWire. So I'd just try running yabridge-host.exe in a terminal to see if that prints the usage string as expected, and if you're using PipeWire then you could also try to see what happens when you disable that.

[Glennbo]

Originally Posted by robbert-vdh

Are you by any chance using PipeWire? Yabridgectl will warn you when running ~/.local/share/yabridge/yabridge-host.exe fails, and it will print the warning you're seeing along with the last line of Wine's output. That's the warning you're seeing right now. It seems weird that running yabridge-host.exe would fail when running standalone when it runs just fine during actual plugin bridging though. Can you try running just ~/.local/share/yabridge/yabridge-host.exe (without wine in front of it) to see if that prints any errors? If everything's working correctly, the output should contain a line starting with 'Usage: yabridge-host.exe '. The reason I asked if you were using PipeWire is because I've only seen these 00a4:err:rpc:I_RpcReceive errors from PipeWire users. PipeWire/rtkit sets a limit on the amount of time a real time thread may spend without yielding to the scheduler, and certain plugins will thus get killed by the scheduler when they take too long to initialize from the audio thread. This is probably not what's happening here, but I've only ever seen those particular errors in the context of PipeWire. So I'd just try running yabridge-host.exe in a terminal to see if that prints the usage string as expected, and if you're using PipeWire then you could also try to see what happens when you disable that.

No PipeWire installed here. Running yabridge-host.exe by itself is producing the following. I am on Xubuntu 20.04.2 and WineHQ's 6.7 staging.

002c:fixme:winediag:LdrInitializeThunk wine-staging is a testing version containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org.
0034:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0034:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0068:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0068:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0084:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0084:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
007c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
007c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
00a8:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
00a8:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
002c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
002c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
002c:fixme:actctxarse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
002c:fixme:ntdll:EtwRegisterTraceGuidsA (01B8379F, 01BC1CF8, {0cfe0455-93ba-440d-a3fe-553973d0b723}, 1, 0066E918, (null), (null), 01BC1D00): stub
002c:fixme:ntdll:EtwRegisterTraceGuidsA (01B8379F, 01BC1D18, {797fabac-7b58-4796-b924-d51178a59ce4}, 1, 0066E918, (null), (null), 01BC1D20): stub
002c:fixme:ntdll:EtwEventRegister ({43d1a55c-76d6-4f7e-995c-64c711e5cafe}, 01BACE28, 00000000, 01BC1500) stub.
002c:fixme:ntdll:EtwEventRegister ({9e3b3947-ca5d-4614-91a2-7b624e0e7244}, 01B83C41, 01BC3258, 01BC3180) stub.
002c:fixme:ntdll:EtwEventEnabled (deadbeef, 01B3B3C0): stub
002c:fixme:ntdll:EtwEventEnabled (deadbeef, 01B30688): stub
002c:fixme:ver:GetCurrentPackageId (0066FEA4 00000000): stub
002c:fixme:ntdll:EtwEventUnregister (deadbeef) stub.
0024:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0024:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0104:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0104:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0024:errrocess:NtCreateUserProcess 64-bit application L"\\??\\H:\\.local\\share\\yabridge\\yabridge-host.exe.so" not supported in 32-bit prefix
Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: File not found.

0104:fixme:ver:GetCurrentPackageId (0068FEA4 00000000): stub

[robbert-vdh]

Originally Posted by Glennbo

No PipeWire installed here. Running yabridge-host.exe by itself is producing the following. I am on Xubuntu 20.04.2 and WineHQ's 6.7 staging.

Ah, yes, that was the other possibility haha. You've (accidentally) set WINEARCH=win32 when you created your default Wine prefix over at ~/.wine. WINEARCH=win32 should not be needed anymore in recent years, but it forces your prefix to behave as if it was a 32-bit installation of Windows and you thus cannot run 64-bit applications, like yabridge-host.exe. Do you actively use the 32-bit applications/plugins installed in ~/.wine? If not, then you can move/remove it and Wine will create a fresh 64-bit prefix there. Otherwise you can just ignore the warning for now (or alternatively, run yabridgectl with WINEPREFIX pointing to a 64-bit prefix).

[Glennbo]

Originally Posted by robbert-vdh

Ah, yes, that was the other possibility haha. You've (accidentally) set WINEARCH=win32 when you created your default Wine prefix over at ~/.wine. WINEARCH=win32 should not be needed anymore in recent years, but it forces your prefix to behave as if it was a 32-bit installation of Windows and you thus cannot run 64-bit applications, like yabridge-host.exe.

It was no accident. When I setup Kontakt, Superior Drummer and all my other Windows plugins almost three years ago, 64 bit WINE was buggy and not recommended.

Do you actively use the 32-bit applications/plugins installed in ~/.wine? If not, then you can move/remove it and Wine will create a fresh 64-bit prefix there. Otherwise you can just ignore the warning for now (or alternatively, run yabridgectl with WINEPREFIX pointing to a 64-bit prefix).

Every plugin and the two actual Windows apps I run are all 32 bit. There is not one 64 bit Windows thing on my machine. Sounds like I should just leave it alone since it is working. I don't want to trip the triggers on copy protection which evidently happened to my copy of EZ-Drummer after switching to Yabridge.

I tested every Windows plugin I have and they all work but EZ-Drummer needed to re-authorize, and Toontrack only lets you do that 4 times before you have to contact them.

[fsynth]

Thanks for the work on this, after learning that I can get WinVst plugins to run on Linux with LinVst and Ubuntu Studio 18.04. Was about to do a fresh install with v20 so it will be fun to try Yabridge

Big thanks to all who make our lives much better as a musician, damn wish I was 40 years younger

[robbert-vdh]

This is just a small bugfix release. The most important fixes in this release are for compatibility issues with Shattered Glass Audio plugins, as well as mouse clicks being offset vertically for VST2 plugins in Tracktion Waveform.

A full list of changes and fixes can be found here:

https://github.com/robbert-vdh/yabri...ases/tag/3.3.1

[MusoBob]

I got a VirtulBox Ubuntu image to try this and I'm just trying to work it all out.
I don't use Linux but getting there with it, but I get this error:
Could not find yabridge's files files: Could not locate 'yabridge-host.exe'
If someone could give me a Dummy's Guide

[robbert-vdh]

Originally Posted by MusoBob

I got a VirtulBox Ubuntu image to try this and I'm just trying to work it all out.
I don't use Linux but getting there with it, but I get this error:
Could not find yabridge's files files: Could not locate 'yabridge-host.exe'
If someone could give me a Dummy's Guide

It somehow took me longer to spot the error from the screenshot than it should have taken, but the issue is that you're running yabridgectl under sudo. That means you're running yabridgectl as root, and not as your own user. Never ever run things as root unless you know what you're doing or why it needs to be run as root! Depending on your distro's configuration there could now be some files in your home directory that your user is not able to modify. If running `~/.local/share/yabridge/yabridgectl sync` as your own user (so running just that, no sudo) gives any errors complaining about permissions then that would be the case here.

And thanks to your screenshot I also spotted a typo in an error message, so thanks!

[MusoBob]

Thanks !
I think I missed a step as I get this now and still no Plugs in Reaper

ubuntu@ubuntu2104:~/Desktop$ '/home/ubuntu/.local/share/yabridge/yabridgectl' sync

Setting up VST2 and VST3 plugins using:

- /usr/lib/libyabridge-vst2.so

- /usr/lib/libyabridge-vst3.so



Found 1 leftover file, rerun with the '--prune' option to remove them:

- /home/ubuntu/.wine/drive_c/Program Files/Common Files/VST3/Band-in-a-Box DAW VST3 Plugin.so



Finished setting up 2 plugins using copies (1 new), skipped 0 non-plugin .dll files

ubuntu@ubuntu2104:~/Desktop$ '/home/ubuntu/.local/share/yabridge/yabridgectl' status

yabridge path: <auto>

libyabridge-vst2.so: '/usr/lib/libyabridge-vst2.so'

libyabridge-vst3.so: '/usr/lib/libyabridge-vst3.so'



installation method: copy



/home/ubuntu/.wine/drive_c/Program Files/Common Files/VST3/

Band-in-a-Box DAW VST3 Plugin.vst3 :: VST3, legacy, 64-bit, copy



/home/ubuntu/.wine/drive_c/Program Files/VSTplugins64/

Band-in-a-Box DAW VST Plugin.dll :: VST2, 64-bit, copy



/home/ubuntu/.wine/drive_c/Program Files (x86)/VSTplugins/

ubuntu@ubuntu2104:~/Desktop$

[robbert-vdh]

Did you add `~/.vst3` and `~/.wine/drive_c/Program Files/VSTplugins64` to REAPER's plugin search paths and rescanned for plugins? (~/.vst3 should be a default in every Linux DAW, but perhaps not in REAPER)

[4duhwinnn]

Very happily, with 3.4, I can now load multiple sounds in SampleTank4.
In SampleTank3, this always worked, but in V4, it would crash if I tried to load a 2nd instrument. And the mousepointer would hide most of the time in V4, also fixed by your new release. Another reason to start windows...
...bites the dust...another one bites the dust...
I set up a donation thru liberapay, and suffice it to say that I wish you had coaded their website! Thanks for the hard and successful work on the 3.4 release.
Cheers

[pax-eterna]

Maybe OT here a bit, but should installing Yabridge using pamac take a long time?

It's been installing now for about 8 minutes requiring user intervention every so often to proceed and even to enter the root password to continue...it's still running as I type this...

And it seems to be re-isntalling the same thing over and over....one I noticed was Ninja??? soemthing or other then saying some fatal error, then running through installin 35 packages...This his appeard about 6 times now?

I am starting to thing this has/is doing something very wrong...

All selected from within pamac (add/remove) so it's not like I have done something random here, just whatever the program said to select

[robbert-vdh]

Originally Posted by pax-eterna

Maybe OT here a bit, but should installing Yabridge using pamac take a long time?

It's been installing now for about 8 minutes requiring user intervention every so often to proceed and even to enter the root password to continue...it's still running as I type this...

Depends on how fast your PC is. Pamac would need to compile lib32-boost-libs first, and then it needs to compile both yabridge and yabridgectl. Compiling the 32-bit Boost libraries is probably going to take the longest time here. I think on my system doing all of this for the first time should only take two minutes at most, but it will very much depend on your system. You can also install the yabridge-bin package instead of the yabridge and yabridgectl packages to use the prebuilt version from GitHub.

[pax-eterna]

it's a very fast system...I now know that yabridgectl has tried to install 6 times...I scolled back up the list....I pressed the cancel and and the end of each attempt it said failed, along with all the fatal messages, so as this whole process has now been running for about 15 minutes I am guessing something very wrong and bad has gone on, and I really do not know how bad it has affected the system.

I am thinking I now need to re-install the whole OS again and start from scratch as I do not know what has been compromised! And I do not know enough about Linux to try and fix it!

I'll be avoiding yabridge in the future though! I was only installing on the off-chance I MIGHT use a windows plug - I am not going to risk it again.

[robbert-vdh]

Originally Posted by pax-eterna

it's a very fast system...I now know that yabridgectl has tried to install 6 times...I scolled back up the list....I pressed the cancel and and the end of each attempt it said failed, along with all the fatal messages, so as this whole process has now been running for about 15 minutes I am guessing something very wrong and bad has gone on, and I really do not know how bad it has affected the system.

I am thinking I now need to re-install the whole OS again and start from scratch as I do not know what has been compromised! And I do not know enough about Linux to try and fix it!

I'll be avoiding yabridge in the future though! I was only installing on the off-chance I MIGHT use a windows plug - I am not going to risk it again.

You mean that you tried installing the yabridgectl AUR package, the compilation failed on an error message, and you tried compiling the same package six more times (each time resulting in the same error message)? I'm not quite sure what happened here. Can you post the compilation error? Your system is not compromised, you were just compiling a Rust application. My best guess is that you installed the wrong Rust toolchain in the process.

[JamesPeters]

Your system is fine. Let it do its thing. The first time, as Robbert says, takes a few minutes. On my system it took longer than on his...maybe 5 minutes? I don't recall. It seemed like a long time. I have a Ryzen 7 3700X and I've disabled the super-turbo-boost-whatever (to keep the CPU fan from spinning up, and I don't need that extra power) so my max speed is 3.6 GHz.

You can always click that arrow on the bottom of the package manager (to the right) to see what's going on, by the way. It may not give much feedback while it's doing something other than show the last thing that it was starting to do. But that's probably enough to reassure you that your OS isn't "broken".

If you are saying it has taken a total of 15 minutes including all the times you cancelled it and started over (and presumably cancelling takes a minute or two, depending on what it's doing...it would have to walk back some stuff)...yeah, that's understandable. And yes if you cancel an operation involving bringing in multiple packages/dependencies, if you try again it'll just bring those in again. You're doing the same thing over and over lol.

But yeah the binary version of Yabridge, as Robbert mentioned, should be fine.

[pax-eterna]

Originally Posted by robbert-vdh

You mean that you tried installing the yabridgectl AUR package, the compilation failed on an error message, and you tried compiling the same package six more times (each time resulting in the same error message)? I'm not quite sure what happened here. Can you post the compilation error? Your system is not compromised, you were just compiling a Rust application. My best guess is that you installed the wrong Rust toolchain in the process.

Yes I really had no choice with the rust, it would not proceed without selecting either one...which is the correct one? And as it is an automatic install thing...(I didn't manually choose anything, other than the rust option) - shouldn't there be an advice somehwere to say which one should be used, if there is a chance a wrong one will create these issues?

And no I did not manually compile anything multiple times, it was the installer doing it! I somehow managed to get a scrolling display of the processes going on which is how come I could see these things happening...in the end I canceled the install and closed pamac - it ws obviously in some sort of cycle.

All I did was search for yabridge in the pamac, found it and clicked on the down arrow on the right. That was it. I then just followed the instuctions as they appeared!

[robbert-vdh]

This release addresses an important regression in yabridge 3.5.0 where using multiple instances of a single VST3 plugin in Ardour and Bitwig Studio could cause the plugin's editors to not work at all until you open every instance's editor at least once. Other than that, there have been a lot of tweaks and refinements to yabridge's editor handling. There's a new feature that allows you temporarily directly focus the plugin's GUI to prevent the host from stealing key presses (as Bitwig Studio for instance normally allows you to still press Space to pause and resume the transport while interacting with plugins), and there have also been a lot of refinements to how and when yabridge grabs and releases input focus.

The full changelog with a complete list of fixes and improvements can be found here:

https://github.com/robbert-vdh/yabri...ases/tag/3.5.1

[robbert-vdh]

Yet Another small bugfix release. This fixes a regression in yabridge 3.5.1 where a small number of VST3 plugins (including the new Kontakt VST3 plugin) would not resize their editor correctly. And technically SysEx support for VST2 plugins is a new feature in this release, but the only reason it wasn't implemented earlier is because I was sure nothing needed it (I was wrong).

The full changelog can be found here:

https://github.com/robbert-vdh/yabri...ases/tag/3.5.2

[pax-eterna]

Originally Posted by robbert-vdh

Yet Another small bugfix release. This fixes a regression in yabridge 3.5.1 where a small number of VST3 plugins (including the new Kontakt VST3 plugin) would not resize their editor correctly. And technically SysEx support for VST2 plugins is a new feature in this release, but the only reason it wasn't implemented earlier is because I was sure nothing needed it (I was wrong).

The full changelog can be found here:

https://github.com/robbert-vdh/yabri...ases/tag/3.5.2

Robert, can I update also via Pacman in Manjaro?

[robbert-vdh]

Originally Posted by pax-eterna

Robert, can I update also via Pacman in Manjaro?

Yes. Just update your yabridge package(s) and rerun `yabridgectl sync`.

[pax-eterna]

Originally Posted by robbert-vdh

Yes. Just update your yabridge package(s) and rerun `yabridgectl sync`.

cooly cool, thanks Robbert

[reapercurious]

its funny how the least amount of effort seems to have gone into describing what yabridge is and how to use it, as if it should be second nature to just start using it. shouldn't there be a little walkthrough? a link to a walkthrough? some promo stuff? a webpage other than github? I would like to run windows vst's on linux natively but I also want to find some stacks of cash in a duffel bag. I'm just saying from where I am, my computing life is something like "wish in one hand, crap in the other, see what happens first" I have heard of this software before, but to find out if it is for me I am going to have to put on my detective hat and start looking for clues, know what I mean?

[pax-eterna]

Originally Posted by reapercurious

its funny how the least amount of effort seems to have gone into describing what yabridge is and how to use it, as if it should be second nature to just start using it. shouldn't there be a little walkthrough? a link to a walkthrough? some promo stuff? a webpage other than github? I would like to run windows vst's on linux natively but I also want to find some stacks of cash in a duffel bag. I'm just saying from where I am, my computing life is something like "wish in one hand, crap in the other, see what happens first" I have heard of this software before, but to find out if it is for me I am going to have to put on my detective hat and start looking for clues, know what I mean?

Full instructions (IE walkthrough) ARE on the github page. Rather extensive and easy to follow I'd say.

Where we go wrong is when WE miss a step (intentionally or deliberately) or vary an instruction to "suit" a personal methodology - that is hardly the fault of the developer

[reapercurious]

I'm trying to do a high volume of things and missed the introduction page, i stupidly followed some other link to one of the releases and not the main one. It's because of time. And just switched to Linux, Arch no less, and for a month still not fully situated, but I do industrial designy stuff in addition to "music when i'm lucky"

thanks for the correction.

[robbert-vdh]

Yet Another yabridge update, just in time for the quarterly release pact. This update is mostly about quality of life improvements and small bug fixes for obscure plugins. The Wine->X11 drag-and-drop implementation has been made even more robust so it can handle more curve balls thrown at it, like the nonstandard drag-and-drop implementation in Samplab. The warnings for incorrect system configuration have also been made more visible through desktop notifications, so it should no longer be possible to miss these and run into weird issues later. We also added a workaround for a bug in an underlying library that would cause yabridge to crash when using an invalid system locale, which can happen on Arch (btw) after skipping part of the installation process. And finally, the real reason for the bump to 3.6.0 (which is definitely not just to be able to reach yabridge for Workgroups 3.11), we replaced an old yabridge.toml compatibility option intended to fix window sizing issues in PSPaudioware E27 with a better version that also fixes similar GUI issues in SoundToys Crystallizer.

The full changelog with all fixes and improvements can be found here:

https://github.com/robbert-vdh/yabri...ases/tag/3.6.0

[pax-eterna]

Robbert did you see my question immediately above your post?