Airwindows console 8 and aux sends

[Scrubbing Monkeys]

Airwindows Console 8 question.

I understand the workflow. Tracks to subs to bus. What about aux sends? Since an aux track uses the channel I/o you end up with a track to track to sub to bus. Any difference?

[mcbpete]

Not sure if it's right but I've been sticking the 'bus' plugin at the start of the aux send i/o chain and then the 'channel' at the end

I kinda see the 'channel' instance of the plugin as an encoder and 'bus' as the decoder, and you 'encode' between the channels but then have to 'decode' if you want to process the channels further

[Scrubbing Monkeys]

Yeah i agree with the logic but console 8 specifically requires channel ..to sub ...to bus. Bus being the 2 bus.

In your example the aux track would start with a channel out then channel in then fx then channel out. Which makes sense if the encode decode logic aplies.

[mcbpete]

Apologies, forgot console 8 had 3 parts to it - in which case I think the aux would effectively be considered a 'sub mix' (as multiple channels could feed into it) so 'sub in' at the start of the aux chain and 'sub out' at the end of the aux chain

[dikrek]

There’s the light version of console 8 too. I use that one

[Winstontaneous]

paging @jinxtigr

[Scrubbing Monkeys]

There’s the light version of console 8 too. I use that one

Whats the difference?

[Scrubbing Monkeys]

Apologies, forgot console 8 had 3 parts to it - in which case I think the aux would effectively be considered a 'sub mix' (as multiple channels could feed into it) so 'sub in' at the start of the aux chain and 'sub out' at the end of the aux chain

Seems logical.