Package Details: airwindows-git r395.171fc8a1-1

Git Clone URL: https://aur.archlinux.org/airwindows-git.git (read-only, click to copy)
Package Base: airwindows-git
Description: Airwindows plugins are modular, graphic-less, stripped-down, VST plugins for Mac and PC
Upstream URL: https://www.airwindows.com/
Licenses: MIT
Groups: vst-plugins, pro-audio
Provides: airwindows
Submitter: Teteros
Maintainer: galuise
Last Packager: galuise
Votes: 6
Popularity: 0.000000
First Submitted: 2020-08-18 08:38 (UTC)
Last Updated: 2024-07-01 19:35 (UTC)

Latest Comments

1 2 Next › Last »

galuise commented on 2024-12-27 20:08 (UTC)

The libfakeroot error I believe is a "known" issue with libfakeroot that can be safely ignored (I get the same message several times as well when building):

See here: https://bbs.archlinux.org/viewtopic.php?id=299733

Output of the end of my build:

==> Entering fakeroot environment...
==> Starting package()...
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Stripping unneeded symbols from binaries and libraries...
libfakeroot internal error: payload not recognized!
libfakeroot internal error: payload not recognized!
libfakeroot internal error: payload not recognized!
libfakeroot internal error: payload not recognized!
libfakeroot internal error: payload not recognized!
libfakeroot internal error: payload not recognized!
  -> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "airwindows-git"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Creating package "airwindows-git-debug"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: airwindows-git r419.30a0d794-1 (Fri 27 Dec 2024 02:46:30 PM EST)

Just ran another build on a completely different machine running Arch and I'm unable to reproduce the issue you are running into.

Running the latest 

Linux ga-arch-ws 6.12.6-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 19 Dec 2024 21:29:01 +0000 x86_64 GNU/Linux

And the plugins are working for me in Reaper v7.28/linux-x86_64 rev 31cb21.

I'm not sure what is different with your system. I have one other Arch machine I can run the same build process on as well to try again to reproduce the issue.

Have you tried "Clear cache and re-scan VST paths for all plug-ins" under Options -> Preferences -> Plug-ins section -> VST sub section? (It's under the "Re-scan" button).

Also, what does your VST Plug-in paths look like in that same window? This package should install the airwindows plugins in /usr/lib/vst/airwindows so a minimum would be to make sure /usr/lib/vst is included in said path.

One last thought: Have you tried launching reaper from a terminal window? It does write out some log like messages. For example, for me when I launch by typing "reaper" in the terminal I see:

jack: created client
jack: non-realtime threads
jack: activated client
/dev/cpu_dma_latency: set to 0

I have some LV2 plugins that are "unhappy" and I see messages about those:

lv2: /usr/lib/lv2/lsp-plugins.lv2/ http://lsp-plug.in/plugins/lv2/autogain_mono - patch specified with unsupported type http://lv2plug.in/ns/ext/atom#String
lv2: /usr/lib/lv2/lsp-plugins.lv2/ http://lsp-plug.in/plugins/lv2/autogain_stereo - patch specified with unsupported type http://lv2plug.in/ns/ext/atom#String
lv2: /usr/lib/lv2/lsp-plugins.lv2/ http://lsp-plug.in/plugins/lv2/compressor_lr - patch specified with unsupported type http://lv2plug.in/ns/ext/atom#String
...
...
...

This might give some clues as to why the plugins are not loading on your system.

Is Reaper installed via the official Arch Linux package? https://archlinux.org/packages/extra/x86_64/reaper/

Mezzy12 commented on 2024-12-26 22:40 (UTC) (edited on 2024-12-26 22:42 (UTC) by Mezzy12)

Thanks for the response.

The only untoward thing that happened during the build is as follows (appeared towards the end of the build process, just before the package was compressed and created):

libfakeroot internal error: payload not recognized!

This error appeared the first time I built this package and again after I clean built it following your comment. My system is up to date (I also did a pacman -Syu beforehand).

The package was installed with no further complaints.

Still nothing in reaper.

galuise commented on 2024-12-25 20:14 (UTC)

Hi @Mezzy12,

I just re-built a working airwindows-git on 2024-12-22

Just to confirm I just did a full pacman -Syu as well as ensured my vst2sdk (AUR) package was up to the latest (i.e. git fetch) and even rebuilt vst2sdk. I then rebuilt airwindows-git and it's fully working in my environment (as of about 5 minutes ago 2024-12-25). I confirmed the plugins work in both Reaper and Bitwig studio.

Do you have any error messages or further information?

Mezzy12 commented on 2024-12-25 14:04 (UTC)

Hey, building this seems to make unusable plugins again. Do we need to go back to using the workaround @galuise suggested?

Thanks.

galuise commented on 2024-08-22 17:30 (UTC)

@HurricanPootis,

Thank you! Sorry my gratitude is quite delayed!

HurricanePootis commented on 2024-06-29 07:08 (UTC) (edited on 2024-06-29 07:09 (UTC) by HurricanePootis)

vst2sdk was updated, my apologies for not paying closer attention to my comments.

galuise commented on 2024-06-11 23:18 (UTC) (edited on 2024-06-11 23:50 (UTC) by galuise)

Yes, it appears that the vst2sdk aur package was updated 5/20/2024 and that modified the PKGBUILD to no longer pull the archive.org copy of "vstsdk3610_11_06_2018_build_37.zip" file...

Also, it appears the steinberg-vst36 AUR package that used to exist has been removed (I'm guessing maybe a DMCA via Steinberg as it was distributing said file directly and unauthorized - judging by my own previous AUR checkout circa April 8th 2022...)

I've been trying to get this working using the existing vst2sdk AUR package to no avail...

I tried removing the following line from CMakeLists.txt:

  ${VSTSDK_ROOT}/vstplugmain.cpp

While that does get the project to successfully compile it produces a package that does not work. Firing up a DAW like Reaper results in no airwindows plugins...

I'm afraid at this point things are really kind of stuck as far as "officialy fixing" this package (at least to my knowledge). However, here's a thought:

A very Manual Work-around...

If you grab the "previous release" of the vst2sdk AUR package (prior to said 5/20/2024 update - i.e. Commit ending in 3fda6) it will build using said cached archive.org copy of the previous vst36 SDK download... Then one could modify this package's PKGBUILD file to depend on vst2sdk (instead of AUR steinberg-vst36 which no longer exists) and one would get a working build...

I can confirm that this work-around does work.

Why I haven't made any changes yet...

I'm reluctant to do any of this "Manual Workaround" officially for the following reasons: 1) I don't control the vst2sdk package 2) I'm pretty sure referencing the vst36 SDK download from archive.org might get said AUR package DMCA'ed as well as I do not want to knowingly violate any software licensing agreements (no matter how much I disagree with them on principle).

I'm not giving up, but I wanted to share those thoughts since adopting this package. I'm also open to suggestions.

nyxkn commented on 2024-06-09 09:13 (UTC)

build fails with this error: CMake Error at Helpers.cmake:5 (add_library): Cannot find source file: /usr/include/vst36/vstplugmain.cpp

replacing steinberg-vst36 with vst2sdk and vst3sdk doesn't seem to solve this

nhoma commented on 2024-05-29 08:49 (UTC)

hey there, is it possible to include airwindows consolidated in this build? Cheers -nika

krassecommits commented on 2022-10-17 05:23 (UTC) (edited on 2022-10-17 05:43 (UTC) by krassecommits)

Dependency "steinberg-vst36" is missing (would switching to vst2sdk work?)

Edit: manually installed vst2sdk and the build worked..

1 2 Next › Last »