Hi guys! Could anyone please help me to understand and maybe fix my problem. So I have Apollo Twin X and 14 inch MacBook Pro M2 chip, 16 GB ram and 512 GB Storage. I really can’t put three plug-ins in a row without getting message that I need to increase latency somewhere in settings or something like that. If that’s the case.(and it is just for one track.) how am I gonna mix 5–7 tracks? Isn’t Apollo 2core interface supposed to be a some sort of a dual core beast compared to other interfaces in a similar price range? And I am also not even talking about using very “hungry“ plug-ins, like oceanway studio or capital chambers, etc. could you maybe guys give me some tricks how to make the whole chain faster? Thank you so much.
Apollo twin X thunderbolt 3+ MacBook Pro M2 = super slow? Advice needed.
- Thread starter maxim_g
- Start date
JamesNorth
Hall of Fame Member
Where are you seeing this error - in your DAW, or in Console?
I wonder if this is an IDC thing (which you can turn off for all situations except things like miking up a drum kit).
No the 2 core Apollo is not a beast - it only has a couple of DSP cores and will get eaten up quickly if you don't use native ones in a mix.
I wonder if this is an IDC thing (which you can turn off for all situations except things like miking up a drum kit).
No the 2 core Apollo is not a beast - it only has a couple of DSP cores and will get eaten up quickly if you don't use native ones in a mix.
JamesNorth
Hall of Fame Member
Turn off IDC in Console settings - then try again.
This error relates to trying to keep constant phase alignment across multiple inputs and is not needed for anything other than live recordings with a lot of mics and different inserts in those chains.
The Twin Duo has two DSP CPUs - this forum has a list of DSP usage per plugin at different sample rates in the links at the top … you’ll be able to work out how many plugins can run before you overload it.
This is why UA is developing native versions of their plugin collection (so it runs on your computer, not on the interface) and it’s also why you can buy Satellites to run more DSP plugins.
This error relates to trying to keep constant phase alignment across multiple inputs and is not needed for anything other than live recordings with a lot of mics and different inserts in those chains.
The Twin Duo has two DSP CPUs - this forum has a list of DSP usage per plugin at different sample rates in the links at the top … you’ll be able to work out how many plugins can run before you overload it.
This is why UA is developing native versions of their plugin collection (so it runs on your computer, not on the interface) and it’s also why you can buy Satellites to run more DSP plugins.
first of all, thank you so much for your answers guys. I spent around 3K on those plug-ins insert and stuff. The funniest thing will be that none of that matters ha ha and I could just pay 20 bucks a month for Spark.. seriously, I thought that Apollo automatically using my computers memory. so you think satellite would be worth to invest? Again, I really appreciate your answers.
JamesNorth
Hall of Fame Member
Well here's the thing - offloading processing to a Satellite frees up your system CPU (which will overload if one single core overloads) ... and you can also use all those great plugins to TRACK with using the Apollo.
If you bought them all you also get native versions of those that have been made into native versions with the UA Connect app.
I've got around 18 cores of UA DSP spread across X4, X8P, X16 and it's great to have ... but it depends what your needs and goals with the gear are. You may very well get away with using the Twin only but maybe try to keep the DSP plugin use to the tracking chain in Console/LUNA.
If you bought them all you also get native versions of those that have been made into native versions with the UA Connect app.
I've got around 18 cores of UA DSP spread across X4, X8P, X16 and it's great to have ... but it depends what your needs and goals with the gear are. You may very well get away with using the Twin only but maybe try to keep the DSP plugin use to the tracking chain in Console/LUNA.
Sounds like you might be using one or more resource intensive plugins. Some plugs, like UAD Capitol chambers and others are very demanding and could be causing such issues if applied separately on each track. If that is the case, try putting the plugs onto an fx buss and routing/adjusting as needed, rather than applying multiple instances across your tracks.