Progress Report
In which I read a list of which Airwindows plugins will be ported to Apple Silicon, and though I don’t have a ‘new’ plugin this week, I’ve got some updates that I needed to do to make everything ready for the big M1 push.
If you had trouble with: BuildATPDF, IronOxideClassic2, PodcastDeluxe, especially ResEQ, Slew, or StarChild, try this.
The individual files are now updated, and so’s NewUpdates.zip. For the most part these bugfixes are about fixing missing initialization stuff that could cause the plugins to make unpleasant noises when starting up.
Meanwhile, since I’ve been asked for an explanation of what all those plugins are, I’ll take this opportunity to… just quickly… run through the list of the ones that get an Apple Silicon port. :)
…TWO HOURS LATER…
Good news!
Hey man. Can you someday make a panning plugin based on how loud a signal gets (eg louder more to the right/left)
@Gabriel Zagury, depending on your DAW you might already have that build in. In Bitwig you use a Tool Device, add a Audio Sidechain modulator (leave it on Device Input, so it uses this tracks audio) and map that to the Pan button. If you pre set Pan like 20% to the left before adding the modulators mapping, the signal starts on the left and the louder it gets it goes more and more to the right.
Gabriel Zagury
04/17/2021 – 6:36 PM
Hey man. Can you someday make a panning plugin based on how loud a signal gets (eg louder more to the right/left)
that would be magical indeed
@Ragnar
trippy idea, but id wish for mono at low levels and wider at louder parts..
I probably won’t go apple silicon until next year, but obviously want to keep using your plugins when I do, preferably Mac VST. I also just stumbled across this free course about programming audio plugins for various formats using C++ and JUCE, which I thought I’d share in case it is of any use:
https://www.programmingformusicians.com/simpleeq/
would be cool if u can have some autotune plugin ya know? heehehe
Hi Chris, first of all: thank you for all the work you do. It is awesome. I just recently discovered your work so I need some time to fully appreciate your work but I will.
With respect to packaging: previous comments hinted at an installer that allows selection of plugins. Since there is so many individual plugins you could also offer a grouping in the installer “console emulations”, “reverbs”, “delays” etc. to make the selection easier. That may work for a lot of people, however…
I always rename your component directory names with a prefix “aw_” to prevent name clashes in my Components directory (AU on Mac, putting it in directories under the Components directory doesn’t seem to work for me). It would be great if an installer would also allow that.
I think it may also be awesome if the installer actually detects what you already have installed and do updates (if needed). I like your approach to create new versions instead of “changing” versions (people use plugins as they are. Even if the developer decided that there is a glitch or bug in it, someone can actually be using the glitch for their audio. So fixing the bug actually breaks the audio, so better no fix but a new version without the bug).
Now for me it would be perfectly fine to not have a “full fledged” installer but just a couple of scripts that help people with the “installation maintenance”. This may work in the Unix based Mac ecosystem but I don’t know how that translates to the Windows ecosystem (Powershell, command thing). So maybe this is a bad idea?
Thanks. I’m going to dive into your world of audio effects, work and did support on Patreon. Cheers!