Have you tried running Ardour in a terminal and checking the output there yet? 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. 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). Windows VSTs could be anywhere, just had to point DAW to them.Ĭonfusing 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? I never had this issue with airwave or linvst. So that why I had everything in /usr/lib/vst. It starts with the ZAM plugins so I removed them but then it starts with the dRowAudio Plugins and crashes. vst path to Ardour or Mixbus32c, the scanner crashes the DAW when scanning lv2. Think that's the right path but anyways, when added the. Opened up Reaper and there it is but I use mostly ardour and mixbus. I've only noticed it where I had a song that used a VST choir plugin and I went to commit it because I usually commit that when I'm using a non Linux plugin due to the instability of or the unsureness of a wine update then I noticed the plug-in wasn't there. started to use Yabridge And that's when scanning for plugins would crash once it started the LV2 so that's why I moved to the system wide and it worked perfectly but since the latest version of Yabridge where all windows VSTs should be under ~/.best, I could only use them all now under Reaper. I used to keep all my VST plugins in the ~/.vst. In fact the windows VST plugins used to be in there using Airwave and linvst. I have VSTs in the system wide setting under /use/lib/vst And I have no issues with that. As soon as I remove the VST path, there's no problem. Thanks for the correction Glenn but still why when that's in the path on where the DAWs searches for plugins, it's crashes scanner the lv2. I've got some really old but nice Windows VST's that are a sigle file dll. home/your_name/.wine/drive_c/program files/something. Windows VST's (and a lot of stuff they need) go into e.g. so files that Yabridge created, hence the error message.Īnd then there's the ever confusing Windows VST versus Linux (i.e. so is dependent on the Yabridge version it is meant to work with. A Windows VST is a file that has the extension. a Linux library) with the same name as your Windows VST. I mistakenly assumed that you exactly knew how Yabridge works and also removed /usr/lib/vst/MT-PowerDrumKit.so. dll's too!Įvery living step you mentioned about there I've tried.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |