Re: Airwindows VST's
Posted: Mon Aug 07, 2017 4:22 pm
I mean Console (or Desk, or Busscolor, etc)funkmuscle wrote:Ardour + Airconsole??scalawag wrote:I hope he will do it. Ardour + Airconsole might be the "new" Mixbus
I mean Console (or Desk, or Busscolor, etc)funkmuscle wrote:Ardour + Airconsole??scalawag wrote:I hope he will do it. Ardour + Airconsole might be the "new" Mixbus
cool... thought I was asleep and missed out!scalawag wrote:I mean Console (or Desk, or Busscolor, etc)funkmuscle wrote:Ardour + Airconsole??scalawag wrote:I hope he will do it. Ardour + Airconsole might be the "new" Mixbus
I know a few guys here are great at porting VST plugins to linux, so if anybody with the relevant skills would like to message Chris, I think it would really move this along.Chris from Airwindows wrote:I’m still working on getting the Linux build to work. It’ll be an .so file, and when those become possible I will update every plugin I’ve made VST so far, to be also LinuxVST. (if anyone’s building LinuxVSTs, I’d love some pointers!)
no gui??occulkot wrote:Linux versions are now available:
https://www.kvraudio.com/forum/viewtopi ... 6&t=499919
ok I read the reasons why. makes sense!funkmuscle wrote:no gui??occulkot wrote:Linux versions are now available:
https://www.kvraudio.com/forum/viewtopi ... 6&t=499919
sysrqer wrote:What was the reason for no gui?
I made a similar claim when I first released infamous plugins, but that didn't last. :\ He is right, but its a hard sell.airwindows.com wrote: why no GUI?
Airwindows’ reputation was built out of generic-interface plugins, which typically focus on doing only one thing, often with very simple controls, labelled to help understanding but not to encourage formulaic work. There are two reasons for the generic, non-GUI interfaces. One, because it improves reliability a huge amount (many audio plugin bugs, including showstopper bugs, have to do with the GUI part). Two, because time that could be spent debugging the GUI or tweaking its look—or writing copyprotect code—can be better spent improving the sound. That’s how Airwindows rolls, since 2007.
in mix, nobody can hear your screen
Airwindows is about listening. It’s about the sound being far more exciting than looking at the screen, because that’s all your audience will have to go by. If you get good feelings, it had better be about what you hear! The plugins naturally lend themselves to MIDI control, assigning sliders to control surfaces. Doing that, you can mix without watching pixels, and listen without being distracted by nonsounds.
In the same spirit of ssj71, who said:scalawag wrote:Well, Ardour+Airwindows is for sure a great combination! It can almost be called the new Mixbus (kind of!)
Would you mind sharing which ones you're using? (And your impressions, maybe?)ssj71 wrote: p.s. there are so many I'm really interested to read everyone's thoughts so I don't have to try to audition them all.
Thanks for the pointers! I will give it a try.scalawag wrote:I would say use Airwindows Console Channel on all tracks + Airwindows Console Buss in all Busses and 2bus + Airwindows FromTape on all tracks + Airwindows ToTape on all Busses and 2bus.
It's basically that. But Mixbus also has EQs, and might sound quite different overall. But i'm sure Ardour + Airwindows should give you quite good results on pair with, if not better than Mixbus.