All Airwindows Plugins Now Run Natively on Raspberry Pi

TL;DW: you heard me!

download LinuxARMVSTs.zip for the Pi
MediaFire backup of LinuxARMVSTs.zip

I’m Chris from Airwindows, and you can do this… ON A SIXTY DOLLAR COMPUTER.

That would be a Raspberry Pi 4B with 4 gigs of RAM, effectively the same as the Raspberry Pi 400 I’m using in this video. Oh… also, though the system is apparently locked at 48K sampling rate to match the HDMI audio output I’m using, these tracks are all 24/96 and are running just fine. You might get more performance than I got if you’re not using 96k tracks.

Take these plugins and put them in the VST folder that Reaper is looking at. You can either use the hidden folder that’s default (“.vst” which doesn’t relate to what suffix the plugin has: they’re still .so files, but the FOLDER starts with a period to hide it in the Linux file manager) or point Reaper to the folder you’re keeping the plugins in.

That’s it. Now you can use all the Airwindows plugins… repeat ALL the plugins, all 290 or so of them, and all new ones going forward… on Raspberry Pi, with Reaper or any other DAW that’s legally allowed to use VST2 plugins (me and Reaper have licenses for this, so it looks like we’re good to go). All the plugins, free and open source, on a sixty dollar computer (or eighty if you want more RAM, or around a hundred to a hundred and sixty if you want the Pi 400 like I have, and also want to get all its peripherals as part of a kit)

Seems to work pretty good. Tell your Pi-using friends, and there will be more where those came from. This is now an officially supported platform. :)

This happened because my Patreon let me do the much more demanding update of a few weeks ago (including crucial Linux fixes) and then go out and get a Pi to make these on. The procedure is the same as compiling the plugins on x86 Linux. But you won’t have to, just use the ones I made for you :)