Skip to content

Desktop Integration

jrdnjhnstn edited this page May 31, 2022 · 6 revisions

Desktop Integration

The first step towrads having Desktop Integration, meaning; being able to launch applications with Wine-NSPA's feature sets enabled is to setup Wine-NSPA's Environment Variables globally. IF you haven't already; read the page below for information on how to set up Environment Variables globally.

The next step is tailor some .desktop files and integrate them into my system. After customizing my applications' .desktop files, I move them into /usr/share/applications. At this point, they will now be seamlessly integrated into system menus or a Dock... Using my VST-as-Standalone method; you can get my VSTs running like normal desktop apps too.

Check out some .desktop examples that I have in this repo, found here:

Specifically, have a look in the VST2/3-As-Standalone Folders. These are in use on my system and provide a nice seamless experience, using VSTs as Standalone apps. You may also notice that for VSTs that I didn't have icons for; I simply created them myself. This method requires Yabridge + Carla-Single binary.

Note: Sometimes VST3's can have issues that the VST2 version of a plugin may not have. For example, I prefer to use Kushview Element as VST2-as-Standalone; the VST3 plugin has some stability + resize issues. Personally, I think VST2s tend to be a little more 'proven' and have less quirks.

In any case, Element VST2 plugin can host VST3, so it's a non-issue for my setup.