Regarding the buffer I was not quite clear: When I used the Scuffham amp simulation the 64 buffer is enough, but the other day I checked out the new (and pretty, pretty good) UAD Bluesbreaker simulation and things started to feel slow. Unfortunately switching the interfaces is not an option, since I have two HD 16 I/O which are wired to patchbays and a monitor system - so a change on the fly is not possible. If you want to record/monitor through the Twin, you would need to switch to that as your interface, then switch back to HD Native for everything else when you're done.īut I'm also baffled that you feel a 64 buffer on HD Native is not quick enough. HD systems will not aggregate with any other interface. My plan is to use the Twin as a stand-alone FX box with my laptop and run analogue outputs into my main ProTools HD rig, and also as a mobile recording rig with up to 10 inputs using a Focusrite ISA 828 with the digital card.

However, since the Twin features an optical input, nothing is stopping you from using the OMNI's optical output to feed up to 8 channels of audio into the Console, but you won't be able to pipe any outputs into ProTools since the Twin doesn't feature any digital outputs. using the Apollo Twin as your ProTools interface. I'm taking delivery of my new Twin Duo next month and should be able to investigate more in depth, but I believe that if you use it in conjuction with a ProTools HD/HDX system, you cannot bring audio from ProTools into the Console unless you run ProTools HD software without the hardware, i.e.

The UAD Apollo Twin should behave like all the other Apollo interfaces - the Apollo Console is always operational even if ProTools isn't up and the DSP is shared between what is used on the Console and what is called up by plugins within ProTools.

Uad dsp