[ANN] yabridge 5.1.0, a long-awaited maintenance release

[pax-eterna]

Nope, no go...ran sync and it worked ok, then when I opened Reaper it saw the plugs and tried to scan, but every one of them reported an issue!

[robbert-vdh]

Originally Posted by pax-eterna

Not sure yet...just checking before I start installing...I too have 6.16 in yet to run sync so we'll see what happens

Wine Staging 6.16 won't work with yabridge because of the Undefined Behaviour Wine bug linked in the readme and on the Discord. Because UB is, well, undefined, the 32-bit version did still work, but the 64-bit version did not. Wine Staging 6.17 is for some reason still not in either Arch's or Manjaro's repos yet, so you'll need to either downgrade to Wine Staging 6.14 (instructions are in yabridge's readme) or use the wine-tkg 6.17 build from a week ago.

[pax-eterna]

Thanks Robbert - I was sorta trying 6.16 based on info above, but successfully downgraded and synced the folder.

Sadly, Reaper scanned the vst's ok but none are appearing in the list when I go to try and run one!

Isn't there supposed to be a .so file in the synced folder?

[robbert-vdh]

Originally Posted by pax-eterna

Thanks Robbert - I was sorta trying 6.16 based on info above, but successfully downgraded and synced the folder.

Sadly, Reaper scanned the vst's ok but none are appearing in the list when I go to try and run one!

Isn't there supposed to be a .so file in the synced folder?

For VST2 plugins you'll find a .so file next to the Windows VST2 plugin's .dll file. VST3 plugins are set up in ~/.vst3/yabridge as per the spec. Run

yabridgectl status

to get a list of all plugins known to yabridgectl.

[pax-eterna]

Originally Posted by robbert-vdh

For VST2 plugins you'll find a .so file next to the Windows VST2 plugin's .dll file. VST3 plugins are set up in ~/.vst3/yabridge as per the spec. Run

yabridgectl status

to get a list of all plugins known to yabridgectl.

Not running any VST2 versions : all VST 3 only, so I assumed I just add the Common Files folder as a source?

That command shows:
yabridge path: <auto>
libyabridge-vst2.so: '/usr/lib/libyabridge-vst2.so'
libyabridge-vst3.so: '/usr/lib/libyabridge-vst3.so' (64-bit)

yabridge-host.exe: '/usr/bin/yabridge-host.exe'
yabridge-host-32.exe: '/usr/bin/yabridge-host-32.exe'

installation method: copy

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

/home/denzoid/.wine/drive_c/Program_Files/VstPlugIns/
AmpliTube 4.vst3 :: VST3, legacy, 64-bit, copy
GSiRotary.vst3 :: VST3, legacy, 64-bit, copy
SampleTank 3.vst3 :: VST3, legacy, 64-bit, copy
SampleTank 4.vst3 :: VST3, legacy, 64-bit, copy
VB3-II.vst3 :: VST3, legacy, 64-bit, copy

[SmajjL]

Originally Posted by Glennbo

I'm running wine-staging 6.16-1 and not seeing any issues with Yabridge and the few Windows plugins I still use. Is it specific plugins that are having issues, or functions of Yabridge, like setting its paths or running sync, neither of which I ever do coz I never add more Windows plugins. The few I need are already setup.

It is Yabridge itself that spell out error/information and i thought 6.16-1 would have a special patch for this and still got same text in my eye anyway, so i was *confused and thought stuff, ohh yes i thought stuff
It is when i yabridgectl (add) or (sync) i think errors/loveletters shows up, i think.

I am on my way back to Linux now after my coffee/buns and can try 6.16-1 again *sure* so i can be more specific of the errors i get (from Yabridge) or find out, I was an oopsie-donkey

Tempted to go Deb/UB just because those things are easy there aka SmajjL can do it and update the kernel and apps manually

[robbert-vdh]

Originally Posted by pax-eterna

Not running any VST2 versions : all VST 3 only, so I assumed I just add the Common Files folder as a source?

That command shows:
yabridge path: <auto>
libyabridge-vst2.so: '/usr/lib/libyabridge-vst2.so'
libyabridge-vst3.so: '/usr/lib/libyabridge-vst3.so' (64-bit)

yabridge-host.exe: '/usr/bin/yabridge-host.exe'
yabridge-host-32.exe: '/usr/bin/yabridge-host-32.exe'

installation method: copy

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

/home/denzoid/.wine/drive_c/Program_Files/VstPlugIns/
AmpliTube 4.vst3 :: VST3, legacy, 64-bit, copy
GSiRotary.vst3 :: VST3, legacy, 64-bit, copy
SampleTank 3.vst3 :: VST3, legacy, 64-bit, copy
SampleTank 4.vst3 :: VST3, legacy, 64-bit, copy
VB3-II.vst3 :: VST3, legacy, 64-bit, copy

I don't know how those VST3 plugins ended up there, but they're in the wrong directory. VST3 plugins won't let you choose a different installation directory for a reason. If you moved them yourself, then move those .vst3 files back to "/home/denzoid/.wine/drive_c/Program Files/Common Files/VST3/", rerun yabridgectl sync, make sure ~/.vst3 is in REAPER's plugin search locations, clear the blacklist, and rescan. Because with this setup it sounds like the plugins got blacklisted because REAPER is also scanning that VstPlugIns directory.

[Glennbo]

Originally Posted by SmajjL

It is Yabridge itself that spell out error/information and i thought 6.16-1 would have a special patch for this and still got same text in my eye anyway, so i was *confused and thought stuff, ohh yes i thought stuff
It is when i yabridgectl (add) or (sync) i think errors/loveletters shows up, i think.

I am on my way back to Linux now after my coffee/buns and can try 6.16-1 again *sure* so i can be more specific of the errors i get (from Yabridge) or find out, I was an oopsie-donkey

Tempted to go Deb/UB just because those things are easy there aka SmajjL can do it and update the kernel and apps manually

One thing that might have some bearing on it working for me is that I setup all my Windows plugins over three years ago when it was general consensus to use a 32 bit prefix for WINE. I have *never* re-installed any of my Windows plugins since then, since they all work and don't need fixing.

If I were setting it all up from scratch I'd go 64-bit, but since all the authorizations and registrations are setup and there's no advantage for me to switch, I'm keeping it setup as 32-bit, which only limits things like Superior Drummer or Kontakt to 4GB worth of samples per instance. I use separate instances of Kontakt with no instruments even close to 4GB, so it's much less of an issue than reinstalling and re-authorizing all my Windows plugins.

[pax-eterna]

Originally Posted by robbert-vdh

I don't know how those VST3 plugins ended up there, but they're in the wrong directory. VST3 plugins won't let you choose a different installation directory for a reason. If you moved them yourself, then move those .vst3 files back to "/home/denzoid/.wine/drive_c/Program Files/Common Files/VST3/", rerun yabridgectl sync, make sure ~/.vst3 is in REAPER's plugin search locations, clear the blacklist, and rescan. Because with this setup it sounds like the plugins got blacklisted because REAPER is also scanning that VstPlugIns directory.

So I did all of that, also ran the RM to clear, re-ran add and got:
error: Found argument 'Files/Common' which wasn't expected, or isn't valid in this context

If you tried to supply `Files/Common` as a PATTERN use `-- Files/Common`

USAGE:
yabridgectl add <path>

[Glennbo]

Originally Posted by pax-eterna

So I did all of that, also ran the RM to clear, re-ran add and got:
error: Found argument 'Files/Common' which wasn't expected, or isn't valid in this context

If you tried to supply `Files/Common` as a PATTERN use `-- Files/Common`

USAGE:
yabridgectl add <path>

Maybe put quotes around the full path so spaces don't mess with how it's seen by yabridgectl.

Like: "~/.wine/drive_c/Program Files/Common Files/VST3/"

[robbert-vdh]

Originally Posted by pax-eterna

So I did all of that, also ran the RM to clear, re-ran add and got:
error: Found argument 'Files/Common' which wasn't expected, or isn't valid in this context

If you tried to supply `Files/Common` as a PATTERN use `-- Files/Common`

USAGE:
yabridgectl add <path>

Command line arguments in Bash and basically every other shell are split on spaces. So two words separated by a space are turned into two separate arguments. You need to either use double quotes around the path (just like in my previous message), or escape the spaces in the path by putting a backlash before them.

[robbert-vdh]

Originally Posted by Glennbo

Maybe put quotes around the full path so spaces don't mess with how it's seen by yabridgectl.

Like: "~/.wine/drive_c/Program Files/Common Files/VST3/"

No, that won't work. That's a relative path starting at some directory called ~ inside of the current directory. The full correct path was in my message (but there wasn't any reason to add and remove paths in yabridgectl to begin with).

[robbert-vdh]

Originally Posted by SmajjL

or just or just yabridgectl add ~/.wine/drive_c/
But then ALL your stuff in there will be discovered, but hey

Don't actually do that of course.

[SmajjL]

Originally Posted by robbert-vdh

Don't actually do that of course.

Don't actually do that of course! *confirmed*

[pax-eterna]

Originally Posted by Glennbo

Maybe put quotes around the full path so spaces don't mess with how it's seen by yabridgectl.

Like: "~/.wine/drive_c/Program Files/Common Files/VST3/"

yeah, I think when I did the copy and paste one may have been left off, or both???

Anyhoo, as I am OCD about "clean and smooth" installs, and as I hadn't gone very far in with this one, I fully re-installed the distro ...THEN went to Robberts Git page and made doubly sure I followed, in sequence, every step!

All installed nice and easy all working - haha still got the issue with BT Midi in Reaper, but everything else is so far so good - nearly ready to make an image file....once I get BT Midi working in Reaper, I'll be good to go I reckon! sooooo glad I didn't bail (on Linux) when I wanted to and stuck it out for one more go!!!

[SmajjL]

I don't know what i'm talking about but (so?) Don't have BlueTeeth
Was just thinking that i've seen comments somewhere during pipewire development so i am curious if you nowdays are better of using that bundle of pipewire-install-way instead of the old X-way.
Grain of salt me or find an ah-ha! your choice and if noone understands me, it's ok hehe

Pipewire is spanking new, new can be good, or not, for bluez? *theory*

[heda]

Just to inform I tested yabridge on MX Linux 21 beta and it works well. MX21 comes with the 6.17 version of Wine by default.

[Pinknoise]

Originally Posted by heda

Just to inform I tested yabridge on MX Linux 21 beta and it works well. MX21 comes with the 6.17 version of Wine by default.

Is the old Ubuntu 18.04 still needed or is the 'official' one good to go ?

EDIT: the official seems to work here

[lucas_LCS]

Is this anything to be concerned about?
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...

it came at the end of this:

(1/1) checking keys in keyring                     [######################] 100%
(1/1) checking package integrity                   [######################] 100%
(1/1) loading package files                        [######################] 100%
(1/1) checking for file conflicts                  [######################] 100%
(1/1) checking available disk space                [######################] 100%
:: Processing package changes...
(1/1) installing yabridge-bin                      [######################] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...

::

[robbert-vdh]

If you're curious about how Pacman hooks work, then there's this page in the Arch wiki: https://wiki.archlinux.org/title/Pacman#Hooks

That particular hook is 30-systemd-update.hook from the systemd package, which runs systemd-hook every time pacman installs, updates, or removes something in /usr.

[lucas_LCS]

Not sure what to do with the message I get after running:
yay -S yabridge-git yabridgectl-git

:: There are 2 providers available for cargo:
:: Repositoryextra
    1) rust :: Repositorycommunity
    2) rustup 

Enter a number (default=1):

::

[lucas_LCS]

I made some .SO files.
Where do I point Reaper to look for them?
It doesn't appear to see the wine C drive.
yabridgectl status returns this:

]$ yabridgectl status
yabridge path: <auto>
libyabridge-vst2.so: '/usr/lib/libyabridge-vst2.so'
libyabridge-vst3.so: '/usr/lib/libyabridge-vst3.so' (64-bit)

yabridge-host.exe: '/usr/bin/yabridge-host.exe'
yabridge-host-32.exe: '/usr/bin/yabridge-host-32.exe'

installation method: copy

/home/lcs/.wine/drive_c/Program Files/VST/
  BlueCat/BC Chorus 4 VST(Mono).dll :: VST2, 64-bit, copy
  BlueCat/BC Chorus 4 VST(Stereo).dll :: VST2, 64-bit, copy
  BlueCat/BC Flanger 3 VST(Mono).dll :: VST2, 64-bit, copy
  BlueCat/BC Flanger 3 VST(Stereo).dll :: VST2, 64-bit, copy
  BlueCat/BC FreqAnalyst 2 VST(Mono).dll :: VST2, 64-bit, copy
  BlueCat/BC FreqAnalyst 2 VST(Stereo).dll :: VST2, 64-bit, copy
  BlueCat/BC Gain 3 VST(Dual).dll :: VST2, 64-bit, copy
  BlueCat/BC Gain 3 VST(Mono).dll :: VST2, 64-bit, copy
  BlueCat/BC Gain 3 VST(Stereo).dll :: VST2, 64-bit, copy

I added the ~/.vst path to Reaper's plugin scan, but Reaper doesn't see the new plugins.
::

[Glennbo]

Originally Posted by lucas_LCS

I made some .SO files.
Where do I point Reaper to look for them?
It doesn't appear to see the wine C drive.

I added the ~/.vst path to Reaper's plugin scan, but Reaper doesn't see the new plugins.
::

In REAPER go to the "Add Path" function in the VST section and navigate to this path.

/home/lcs/.wine/drive_c/Program Files/VST/

If you don't see the .wine folder right click and tell REAPER to show files and folders beginning with a . which makes them hidden in Linux.

The /home/lcs/.vst is for native Linux plugins only. The converted .dll Windows plugins should also now have .so files of the same names in the same folders. For instance, if I navigate to my .wine/drive_c/Program Files/VSTPlugins/Toontrack/ I see this.

ezdrummer.dll EZkeys.dll 'Superior Drummer.dll'
ezdrummer.so EZkeys.so 'Superior Drummer.so'

[lucas_LCS]

YES!
Working now, thanks!

Yabridge does not like the Melda plugins it seems, but the rest area loading fine.

now I can move on to the IK Multimedia stuff.

::

[Glennbo]

Originally Posted by lucas_LCS

YES!
Working now, thanks!

Yabridge does not like the Melda plugins it seems, but the rest area loading fine.

now I can move on to the IK Multimedia stuff.

::

Cool! I have SampleTank 1.1.9 Free Edition, but it only has a handful of demo instruments, and I just copied it to my VST folder.

[robbert-vdh]

Originally Posted by lucas_LCS

YES!
Working now, thanks!

Yabridge does not like the Melda plugins it seems, but the rest area loading fine.

now I can move on to the IK Multimedia stuff.

::

MeldaProduction plugins run absolutely fine under Wine. There weren't any Melda plugins in the yabridgectl status output you posted earlier, if you haven't tried adding them since. Oh and if you have the choice, pick the VST3 version of a plugin as it will both perform and scale better while in some cases also having some additional features.

[SmajjL]

https://www.phoronix.com/scan.php?pa...e-Staging-6.18
"Wine-Staging 6.18 Released With 616 Patches"

[pax-eterna]

Originally Posted by SmajjL

https://www.phoronix.com/scan.php?pa...e-Staging-6.18
"Wine-Staging 6.18 Released With 616 Patches"

STILL only 6.16 on AUR

[lucas_LCS]

Originally Posted by robbert-vdh

MeldaProduction plugins run absolutely fine under Wine. There weren't any Melda plugins in the yabridgectl status output you posted earlier, if you haven't tried adding them since. Oh and if you have the choice, pick the VST3 version of a plugin as it will both perform and scale better while in some cases also having some additional features.

Yeah, I worded that badly, I don't think it's actually an issue with Yabridge.
I didn't do a normal install, so I will try that later when I have time.

Here is the message in case you're interested:



Yabridge is working pretty well so far, now that I have my 'user' errors out of the way.

[robbert-vdh]

Originally Posted by lucas_LCS

Yeah, I worded that badly, I don't think it's actually an issue with Yabridge.
I didn't do a normal install, so I will try that later when I have time.

Here is the message in case you're interested:

<snip>

Yabridge is working pretty well so far, now that I have my 'user' errors out of the way.

Check the log like the message suggests. Does this happen during REAPER's initial scan, or when inserting the plugin on a track after the scan is done? If it's the latter, then launch REAPER from a terminal, insert the plugin, and check the output printed when you do that for any errors or warnings.

If it happens during the scan, then you'll need to have yabridge write the output to another file because REAPER sometimes likes to hide it from you. In that case, you'll need to launch REAPER with

rm -f /tmp/yabridge.log; env YABRIDGE_DEBUG_FILE=/tmp/yabridge.log YABRIDGE_DEBUG_LEVEL=1 reaper

, rescan the plugin, and then check the log file at /tmp/yabridge.log.

[SmajjL]

Originally Posted by pax-eterna

STILL only 6.16 on AUR

Don't know what's up, it is flagged as out of date so, the world knows about it

wine-ge-custom 6.18.GE.1-2 also works if you wanna give your CPU a workout, works great, tried it with Kontakt/Yabridge
Will take a while to build, but hey

[heda]

I thought Manjaro was good with maintaining latest versions of the packages.

I'm having a crash when using dpmeter vst3 plugin, but maybe it is because I'm using Wine 6.4 staging in Manjaro... I don't know if it is possible to debug the error.. maybe I'll try that Wine 6.18 and see if it works better.

[robbert-vdh]

Originally Posted by heda

I thought Manjaro was good with maintaining latest versions of the packages.

I'm having a crash when using dpmeter vst3 plugin, but maybe it is because I'm using Wine 6.4 staging in Manjaro... I don't know if it is possible to debug the error.. maybe I'll try that Wine 6.18 and see if it works better.

Did the plugin work before, or did it suddenly start crashing? Take a look at yabridge's output when you run REAPER in a terminal, there's probably something obvious in there.

[heda]

Originally Posted by robbert-vdh

Did the plugin work before, or did it suddenly start crashing? Take a look at yabridge's output when you run REAPER in a terminal, there's probably something obvious in there.

[dpMeter4 x64-EJMTZirx] [Wine STDERR] 002c:fixme:winediag:LdrInitializeThunk wine-staging 6.4 is a testing version containing experimental patches.

it doesn't print any error in the terminal after [Wine STDERR] Finished initializing

a Wine Error window appears
title: Microsoft Visual c++ run...
message: Runtime Error. Program: Z:\usr\bin\yabridge-host.exe R6025 - pure virtual function call

Then REAPER hangs and I have to Kill it

[robbert-vdh]

Originally Posted by heda

[dpMeter4 x64-EJMTZirx] [Wine STDERR] 002c:fixme:winediag:LdrInitializeThunk wine-staging 6.4 is a testing version containing experimental patches.

it doesn't print any error in the terminal after [Wine STDERR] Finished initializing

a Wine Error window appears
title: Microsoft Visual c++ run...
message: Runtime Error. Program: Z:\usr\bin\yabridge-host.exe R6025 - pure virtual function call

Then REAPER hangs and I have to Kill it

So, did the plugin work before? (never used it myself, but it should work fine) Try running the plugin in a clean prefix, without the MSVC++ runtime you have installed in your main Wine prefix.

[heda]

I thought it was working before... but because I didn't test it enough... at first it works... but then it fails sometimes when removing the plugin

I have installed in a new prefix, removed previous version and added new path and resync

now I see the errors in the terminal
22:00:51 [dpMeter4 x64-5GHMSTYx] [Wine STDERR] wine: Unhandled exception 0x40000015 in thread 6c4 at address 00000001801CD55D (thread 06c4), starting debugger...
22:00:53 [dpMeter4 x64-5GHMSTYx] [Wine STDERR] 0524:fixme:dbghelp:elf_search_auxv can't find symbol in module
22:00:53 [dpMeter4 x64-5GHMSTYx] [Wine STDERR] 0524:fixme:dbghelp:elf_search_auxv can't find symbol in module
22:00:53 [dpMeter4 x64-5GHMSTYx] [Wine STDERR] 0524:fixme:dbghelp:elf_search_auxv can't find symbol in module
...

[robbert-vdh]

Originally Posted by heda

I thought it was working before... but because I didn't test it enough... at first it works... but then it fails sometimes when removing the plugin

I have installed in a new prefix, removed previous version and added new path and resync

now I see the errors in the terminal
22:00:51 [dpMeter4 x64-5GHMSTYx] [Wine STDERR] wine: Unhandled exception 0x40000015 in thread 6c4 at address 00000001801CD55D (thread 06c4), starting debugger...
22:00:53 [dpMeter4 x64-5GHMSTYx] [Wine STDERR] 0524:fixme:dbghelp:elf_search_auxv can't find symbol in module
22:00:53 [dpMeter4 x64-5GHMSTYx] [Wine STDERR] 0524:fixme:dbghelp:elf_search_auxv can't find symbol in module
22:00:53 [dpMeter4 x64-5GHMSTYx] [Wine STDERR] 0524:fixme:dbghelp:elf_search_auxv can't find symbol in module
...

You'll need to check the logs (from the beginning up until that Unhandled exception) for any errors or warnings. The both the 64-bit VST2 and VST3 versions work perfectly fine for me with both wine-tkg 6.18 and regular Wine Staging 6.4 in a clean Wine prefix.

[lucas_LCS]

Originally Posted by robbert-vdh

Check the log like the message suggests. Does this happen during REAPER's initial scan, or when inserting the plugin on a track after the scan is done? If it's the latter, then launch REAPER from a terminal, insert the plugin, and check the output printed when you do that for any errors or warnings.

If it happens during the scan, then you'll need to have yabridge write the output to another file because REAPER sometimes likes to hide it from you. In that case, you'll need to launch REAPER with

rm -f /tmp/yabridge.log; env YABRIDGE_DEBUG_FILE=/tmp/yabridge.log YABRIDGE_DEBUG_LEVEL=1 reaper

, rescan the plugin, and then check the log file at /tmp/yabridge.log.

this is the error:
0400:err:module:import_dll Library MeldaProductionAudioPluginKernel64.dll

The number at the beginning is different for each plugin, but they all say they're missing that DLL file.
I'll see if I can find it on my Windows drive and copy it to the VST folder to see if that fixes it before trying a normal install.

::

[robbert-vdh]

Originally Posted by lucas_LCS

this is the error:
0400:err:module:import_dll Library MeldaProductionAudioPluginKernel64.dll

The number at the beginning is different for each plugin, but they all say they're missing that DLL file.
I'll see if I can find it on my Windows drive and copy it to the VST folder to see if that fixes it before trying a normal install.

::

The plugin tries to load MeldaProductionAudioPluginKernel64.dll but fails presumably because it couldn't be found. Which Melda installer did you use? (well they should all be the same) That shouldn't be possible unless you manually moved some files around. I'd just try reinstalling the plugins, and if that somehow still doesn't work just try it again in a new Wine prefix.

[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?