Skip to content

LinVst 4.9

Latest
Compare
Choose a tag to compare
@osxmidi osxmidi released this 09 Aug 06:07
· 26 commits to master since this release
7f47312

LinVst-4.9 made using MX Linux, will probably run on other distros.

32 bit vst's running under the 64bit LinVst versions need a distros multiarch to be enabled (sudo apt-get install gcc-multilib g++-multilib for Ubuntu/Debian).

A Gtk utility is included (linvstconvert) that can automatically batch rename linvst.so to mutiple windows vst dll names that are in a folder/directory, so that a Daw can then load the vst plugins.

After installing the LinVst 4.9 lin-vst-server files to /usr/bin, run linvstconvert and select the LinVst 4.9 linvst.so file and also the folder where the vst plugins are installed and then hit the "Update All Plugins (Upgrade All Plugins)" button to upgrade to LinVst 4.9.

After upgrading to the LinVst 4.9 version (like the above), then any additional vst installs only need the linvstconvert "Update Newly Added Plugins" option.


Hyperthreading

For Reaper, in Options/Preferences/Buffering uncheck Auto-detect the number of needed audio processing threads and set
Audio reading/processing threads to the amount of physical cores of the cpu (not virtual cores such as hyperthreading cores).

This can help with stutters and rough audio response.

Other Daws might have similar settings.


For Waveform, (maybe) disable sandbox option for plugins.

For Renoise, choose the sandbox option for plugins.

For Bitwig, in Settings->Plug-ins choose "Individually" plugin setting and check all of the LinVst plugins.
For Bitwig 2.4.3, In Settings->Plug-ins choose Independent plug-in host process for "Each plug-in" setting and check all of the LinVst plugins.

Flatpak Daw installations might not work with LinVst.

For the LinVst Debian package usage, see the Readme in /usr/share/LinVst

The Debian package installs linvst.so into /usr/share/LinVst/64bit-32bit and installs linvstconvert into /usr/bin

To remove the package use sudo dpkg -r linvst-64bit-32bit

TestVst is a standalone utility for testing how a vst plugin might run under Wine.


Quick Start Guide

(See the Wiki page for a visual guide https://github.com/osxmidi/LinVst/wiki)

Copy all of the lin-vst-serverxxxx files (files with lin-vst-server in their names) to /usr/bin.

Install the vst's.

The vst's will probably be installed by default to a Wine folder, something like ~/.wine/drive_c/Program Files/Steinberg/VSTPlugins (which is similar to where they are installed on Windows).

It's also possible with most plugins to make a folder and install the windows vst's into it.

Start linvstconvert and then select the linvst.so file.

Point linvstconvert to the folder containing the windows vst's and hit the Start (Convert) button.

Start up the linux DAW and point it to scan the folder containing the windows vst's.

linvstconvert can be used to convert multiple vst folders after linvst.so is loaded.
Wait for the button to turn back to "Start" (from "Done") and then choose another folder and then hit "Start".

If new vst plugins are added to a folder, then just run linvstconvert again on that folder.


Install instructions are included in the Readme file.

Different LinVst versions are not compatible with each other and the windows dll's need to be name converted again using linvst.so from the new version.

On some systems, some versions of Wine may initially take a long time to load properly which may cause some initial startup problems when using LinVst.
The solution is to initialise Wine first by running winecfg or any other Wine based program, so that Wine has been initialised before LinVst is used.

Upgrading to the latest wine-stable version from WineHQ is recommended.

For recommended Linux kernel and audio setup info see https://github.com/osxmidi/LinVst/blob/master/Detailed-Guide/README.md