Linux update
-
- KVRer
- 18 posts since 4 Dec, 2014
And also, there is another option with Yabridge and VST2 (i didn't tried yet).
https://github.com/robbert-vdh/yabridge#plugin-groups
https://github.com/robbert-vdh/yabridge#plugin-groups
Some plugins have the ability to communicate with other instances of that same plugin or even with other plugins made by the same manufacturer. This is often used in mixing plugins to allow different tracks to reference each other without having to route audio between them. Examples of plugins that do this are FabFilter Pro-Q 3, MMultiAnalyzer and the iZotope mixing plugins. In order for this to work, all instances of a particular plugin will have to be hosted in the same process.
Yabridge has the concept of plugin groups, which are user defined groups of plugins that will all be hosted inside of a single process. Plugins groups can be configured for a plugin by setting the group option of that plugin to some name. All plugins with the same group name will be hosted within a single process. Of course, plugin groups with the same name but in different Wine prefixes and with different architectures will be run independently of each other. See below for an example of how these groups can be set up.
Note that because of the way VST3 and CLAP work, multiple instances of a single VST3 or CLAP plugin will always be hosted in a single process regardless of whether you have enabled plugin groups or not. The only reason to use plugin groups with those plugins is to get slightly lower loading times the first time you load a new plugin.
-
- KVRAF
- Topic Starter
- 3729 posts since 3 Nov, 2015
Yes, it's possible to create groups. I haven't tried it yet mostly because the need is not there yet. For the time bei8ng I'm OK with the plugins being able to communicate between themselves out of the box in a simple way.
It's nice that it solved your issue. I was wondering if I should post the comment, if it was relevant to MAutoAlign at all
It's nice that it solved your issue. I was wondering if I should post the comment, if it was relevant to MAutoAlign at all
-
- KVRAF
- Topic Starter
- 3729 posts since 3 Nov, 2015
There are no problems at all with VST3 or anything else using :
Bitwig 4.4.x
yabridge and the proper wine staging version
However, from what I have seen with another line of plugins, an upgrade to support Apple M1 made the GUI toolkit used for that line of plugins totally unresponsive on Linux. All updates from that line of plugins will receive eventually the same treatment, making all of them unresponsive. That is, if nothing is done on the wine side to cope with that. I have no idea at the moment what the problem could be. I can only see that wine complains about the Vulkan support not being complete - does it have anything to do with this ? I don't know.
That is to say that I wouldn't be surprised if eventually plugin developers update their GUI toolkit to support some new features and in doing so breaking the Linux/wine/yabridge/linvst compatibility.
Bitwig 4.4.x
yabridge and the proper wine staging version
However, from what I have seen with another line of plugins, an upgrade to support Apple M1 made the GUI toolkit used for that line of plugins totally unresponsive on Linux. All updates from that line of plugins will receive eventually the same treatment, making all of them unresponsive. That is, if nothing is done on the wine side to cope with that. I have no idea at the moment what the problem could be. I can only see that wine complains about the Vulkan support not being complete - does it have anything to do with this ? I don't know.
That is to say that I wouldn't be surprised if eventually plugin developers update their GUI toolkit to support some new features and in doing so breaking the Linux/wine/yabridge/linvst compatibility.
-
- KVRAF
- Topic Starter
- 3729 posts since 3 Nov, 2015
A tip I got some time ago from the developer of linvst, and which I use since then :
I launch winecfg before the DAW, from a terminal. Simply launching it then pressing OK. It will 'preload' all wine related data saving the DAW from doing it when it loads the first Windows plugin. Depending on the CPU and RAM (i5 and 16GB here) this allows the DAW to do other important stuff more readily.
Cheers.
I launch winecfg before the DAW, from a terminal. Simply launching it then pressing OK. It will 'preload' all wine related data saving the DAW from doing it when it loads the first Windows plugin. Depending on the CPU and RAM (i5 and 16GB here) this allows the DAW to do other important stuff more readily.
Cheers.