Quote:
Originally Posted by Seablade  Ok so let me ask, what is the benefit of going back and forth repeatedly from Logic like this, assuming it works like you want(And from your description I think it will), vs just letting Mixbus do the summing instead?
Seablade |
Fair question.
With our way of working there are three main advantages:
Firstly, it allows me to use Logic's automation AFTER the MixBus channel strip compressor - up to now I'd automate fader levels in Logic and then I'd get the MixBus channel compressor fighting that.
Secondly it allows me to use Logic's Aux sends (to reverb etc.) Post Fader with respect to MixBus EQ & Compressor. Otherwise Logic's sends are Pre-EQ, Pre Fader which is not ideal. While you CAN route audio back into Logic from MixBus to access Logic's reverbs and delays, the latency through Jack makes this impracticable.
Thirdly, if you're streaming audio in from Logic to MixBus, PDC for my UAD plugins in MixBus doesn't work - it works beautifully on audio running WITHIN MixBus but not on audio being streamed into it. This is no surprise as it's technically impossible to do and no fault of anyone's. But this also relates back to point no 2 regarding where in the signal chain you tap in to in order to send to your parallel effects.
We like to stay in Logic as long as possible as we make tweaks to our VSTi's during the mix process. We also like our Logic reverbs and delays.
We could lock MixBus to Logic using MTC and automate in MixBus - that would address point 1 - but my Alphatrack Faderport doesn't seem to want to work properly with with MixBus at the moment.
The other solution would be to bounce everything to audio and mix within MixBus entirely but that precludes the use of our favourite Logic FX and usually pins us down too early - for us, the line between tracking and mixing is virtually non-existent.
I'm sure that there will be unforeseen downsides to my suggested routing scheme too.