robbert-vdh wrote: ↑Thu Aug 18, 2022 1:07 pm
funkmuscle wrote: ↑Thu Jul 28, 2022 8:04 pm
Hey guys, ianyone here experiencing any issues with Ardour and Mixbus32c using yabridge?
If I add this
Think that's the right path but anyways, when added the ./vst path to Ardour or Mixbus32c, the scanner crashes the DAW when scanning lv2. Weird yes. It starts with the ZAM plugins so I removed them but then it starts with the dRowAudio Plugins and crashes.
So that why I had everything in /usr/lib/vst.
I never had this issue with airwave or linvst. Windows VSTs could be anywhere, just had to point DAW to them.
Confusing thing is why would scanning lv2 plugins when ~.vst path is added crash the DAWs and when the path is removed, these DAWs have no issues scanning for plugins?
That sounds like an issue with your copy of Ardour, and it's likely unrelated to yabridge (I haven't heard anyone else about this either). Ardour's plugin scanning shouldn't be able to take down Ardour even if a plugin crashes because it shells out to a ardour-X-scanner binary to do the actual scanning. Have you tried running Ardour in a terminal and checking the output there yet?
Man sorry I think I clicked the wrong thing I hope this doesn't get reported. I'm doing this on my phone and my fat finger clicked the wrong thing to reply so hopefully I'm praying that I didn't mess this threat up.
Ok maybe Ardour And how it's built on Arch but I'm also having the same issue with mix bus 32c.
Never had the issue with airwaves or linvst.
I'm the weird thing is that when the VST path is added, it's not the VSTs that are crashing the scan but when it's doing the lv2.
Then I would just go remove the VST path and everything scans.
That was the reason why I put all of the VST plugins under /usr/lib/vst
I never thought anything of it until I guess version 4 of Yabridge where you had to help me get things going again because I didn't read the instructions and that's when you suggested or mentioned that it all needs to be in the home directory VST path. Then it brought that issue back because as we know, Yabridge used to work with whatever directory you pointed it to where the VST was. Well at least it worked for me until that recent change.
It's not a big issue because I can do everything I need to do in Reaper and commit it but I just thought that it may be an issue that should be reported. If it's only me it's not a problem to go try to rectify it but if anyone else is having that issue then yes.
Ardour and mixbus32c are basically the same thing except one is from the distros repo and the other one comes with an installer and installs into a completely different directory and I think the mix bus is more of a binary. Again I could be completely wrong I'm just trying to figure out what the heck happened or why is that happening that's all..