Bitwig

psycha0s · Post by **psycha0s** » Mon Aug 22, 2016 7:10 am

You're welcome and I'm glad that it helped!

Lava · Post by **Lava** » Wed Aug 24, 2016 5:43 am

I'm confused about how to use Airwave. Here are my questions:

- So I add plugins using the Create Link button? Shouldn't that be called "add plugin"? Unless I'm mistaken...
- When I click Create Link, the VST plugin field... I don't know what to do there. At first I thought that's where I navigate to my DLL files, but then there's this weird ${WINEPREFIX}/ thing in there that makes me think that's not right. And when I navigate around using that file browser I can't get out of my WINE directory.
- Link location... what is that? Maybe that's where I point to the DLL?
- Link name; what should I put in there, if anything?
- In a future version maybe Airwave can be like Carla and scan for everything without adding one at a time?

Thanks, really looking forward to getting this working.

psycha0s · Post by **psycha0s** » Wed Aug 24, 2016 6:48 am

For the most of the plugins you need to install them using wine like you would do it in Windows (run wine setup.exe for example). Not just copy a bunch of DLLs somewhere.
After you have installed a plugin, its DLL is located somewhere inside of chosen WINEPREFIX. In Airwave manager you should write a path to this DLL into "VST plugin" (the path is relative to the wine prefix, but you have just installed a plugin there, remember?). The link name is a name which will be used for this plugin inside of your DAW. And the link location is a directory where your DAW is looking for VST plugins.

Lava · Post by **Lava** » Wed Aug 24, 2016 3:11 pm

phantom-one wrote:For the most of the plugins you need to install them using wine like you would do it in Windows (run wine setup.exe for example). Not just copy a bunch of DLLs somewhere.
After you have installed a plugin, its DLL is located somewhere inside of chosen WINEPREFIX. In Airwave manager you should write a path to this DLL into "VST plugin" (the path is relative to the wine prefix, but you have just installed a plugin there, remember?). The link name is a name which will be used for this plugin inside of your DAW. And the link location is a directory where your DAW is looking for VST plugins.

Thank you! 90% of the Win VST plugins I have do not come as EXE files, only standalone DLLs. How do I install them?

psycha0s · Post by **psycha0s** » Wed Aug 24, 2016 3:22 pm

You can just copy them to the directory, where you have other plugins installed in your wine prefix. If you're using a default wine prefix, then it is something like this:

Code: Select all

${HOME}/.wine/drive_c/Program Files/VstPlugins/

Lava · Post by **Lava** » Fri Aug 26, 2016 3:26 am

phantom-one wrote:You can just copy them to the directory, where you have other plugins installed in your wine prefix. If you're using a default wine prefix, then it is something like this:
Code: Select all
${HOME}/.wine/drive_c/Program Files/VstPlugins/

Thanks! And once I've done that, I assume I point Tracktion to the Airwave directory so it can see the airwave plugin and therefore load the VSTs?

psycha0s · Post by **psycha0s** » Fri Aug 26, 2016 5:44 am

What do you mean by "airwave directory"?
You have the "plugin directory" $HOME/.wine/drive_c/Program Files/VstPlugins with a bunch of Windows dlls
and the "link directory" with all of your native (Linux) plugins (*.so files) - $HOME/vst for example.
You need to install Windows plugins to the first one and create "airwave links" in the second one. And yes, your VST host (Traction) should be configured to search vst plugins in the second directory. But I'm unsure that Traction works well with airwave.

Lava · Post by **Lava** » Fri Aug 26, 2016 6:14 pm

phantom-one wrote:What do you mean by "airwave directory"?
You have the "plugin directory" $HOME/.wine/drive_c/Program Files/VstPlugins with a bunch of Windows dlls
and the "link directory" with all of your native (Linux) plugins (*.so files) - $HOME/vst for example.
You need to install Windows plugins to the first one and create "airwave links" in the second one. And yes, your VST host (Traction) should be configured to search vst plugins in the second directory. But I'm unsure that Traction works well with airwave.

What I mean is that Airwave becomes the container for the VSTs. So presumably you then need to tell your DAW where that container is and register it as a plugin that contains the meta-plugins (VSTs). Sounds like the airwave links are the containers.

re23071998 · Post by **re23071998** » Sat Sep 03, 2016 11:37 am

Hey panthom, today I reinstall my Ubuntu and I don't remember how to apply wine patch and compiling it, please help me to patch and compile it.

or maybe I can contact you on Facebook?
Sorry :v

Lava · Post by **Lava** » Mon Sep 05, 2016 4:47 am

Hi Phantom,

Question - why does the airwave wineprefix browser limit the location of dll files to the WINE C:\ drive? I mentioned earlier that I have a number of standalone VSTi dlls that don't utilize executables to install. For me to use them I have to copy them into a folder in the C:\ drive then make .so links (which can be placed anywhere on my machine). Is there a reason that the dlls have to be in the C:\ drive? Carla doesn't have a problem with dlls outside the C:\ drive, and it would be nice to utilize my VST plugins in the folder I store them in rather than have to make an unnecessary copy of all of them in the C:\ drive.

All that being said, I'm not the most knowledgeable person about these things so there may be a perfectly valid technical reason it can't be done that I'm not aware of.

Thanks!

psycha0s · Post by **psycha0s** » Mon Sep 05, 2016 8:52 am

Lava, currently it is limited to the wine prefix, not the C: drive. Some plugins may work only in the specific wine environment (configuration + installed libraries), which can be incompatible with other plugins. Thus you might want to have a few wine prefixes. And it would be wrong to use dll from different wine prefix. But honestly, technically there is no reason for limiting a user to do what he want. Airwave is able to work with dlls outside of the wine prefix (right now you can achieve it only manually by fixing a configuration file). Several people have already asked me to remove this limit and I'm planing to do it in the future.

Lava · Post by **Lava** » Mon Sep 05, 2016 2:17 pm

Glad to hear it. I would also love to see directory scanning of plugins as well, so many plugins could be added at once.

Also FYI, last night I got all my Win VST plugins working great in Tracktion 7 using Airwave. Out of numerous plugs, the only one that didn't work was Crisalys, which had a question mark icon next to it in the Airwave browser.

re23071998 · Post by **re23071998** » Sun Sep 11, 2016 7:01 pm

Which wine version you're using to run sylenth1 v2.2 in this post? viewtopic.php?t=161093

Thanks,

re23071998 · Post by **re23071998** » Mon Sep 12, 2016 7:49 am

installed spire 1.1.9 on wine 1.8 + airwave 1.3.2 , override d2d1.dll then open spire in bitwig studio, the GUI appears transparent. What wrong?

Sorry too much questions

psycha0s · Post by **psycha0s** » Mon Sep 12, 2016 8:21 am

re23071998, as far as I can tell, you need a specific version of d2d1.dll:
version: 6.1.7601.17514
size: 827904 bytes
md5 hash: 3e0a1bf9e17349a8392455845721f92f

You can find it freely in google, but personally I don't know whether it's legal or not (at least it should be legal if you own a Windows license).

You have to replace the file itself (.wine/drive_c/Windows/system32/d2d1.dll) and then override it using winecfg.
And don't worry - ask any question if you need, I'll do my best to help you.

Bitwig

KVR Audio

Airwave - yet another WINE VST bridge for Linux (April 12 update)