Pro Tools Expert Podcast Episode 64
Russ, Mike, Neil & James are here with a packed Pro Tools Expert podcast that includes;
- Competitions
- Exponential claims for PT11
- HD Native could be a killer system
- The future of Apple’s Mac Pro
- Community Tip 1 - Carsten Groa
- Community Tip 2 - Tony Molica
- Community Tip 3 - John aka Tunes
- Community Tip 4 - Kimball Owen-Brown
- No sound from Pro Tools SE
- Control surfaces and monitor sections
- No Digidesign Plug-in Folder after update
- Problems with DAE error 9073 on Windows machine Video to help
- Problems with Ableton Live 9 Intro & Pro Tools 10 Rewire downloads
- Will Bidule work with effects plug-ins?
- AAX version of Vocalign LE
- How to prove eligibility for free academic upgrade
- Pelsuo v Octava mics
- Keyboard focus question on Windows PC keyboard Logic keyboard
- Have you heard of Keycue?
- What is the Pro Tools mode on the Apollo?
- Where are the links your refer to in the podcasts
You can listen here;
Our friend Lev Perrey has helped clear up the Pro Tools mode in UAD version 7, he writes…
“To be clear, Pro Tools mode has nothing to do with the record arming or muting of outputs. That is handled by the “Low Latency Monitor” feature in Pro Tools 10. Low Latency Monitor mode works for inputs routed to 1-2 (or the Monitor outputs in our case) so that is how it is handled. When this option is checked in the menu, record arming a track in Pro Tools does not play back the software path, instead you only hear the Apollo Console path - so its great to not have to manage Mutes or anything…
While you guys were spot on about the gnarlyness that can come about when opening a session made on a different interface, PT Mode in the new UAD Version 7 software is all about Hardware Inserts and Multi-unit I/O.
Here is a description of what PT Mode does in V.7:
1. Aligns the I/O for use with Hardware Inserts with one Apollo or one Apollo 16. This is done by adding 2 Null (Silent) inputs into the driver, so that all of the analog and digital I/O are aligned.
When I say aligned, this has to do with the Pro Tools restriction on Hardware Inserts. PT has a rule that Hardware Inserts have to be in the same input and output slot to be used. With Apollo for example, the first inputs are Mic/Line/HI-Z 1-2 and the first two outputs are Monitor 1-2 - hence, users with UAD v.6.5 or lower couldn’t use the first two Hardware Inserts in Pro Tools. So they were limited to 6 hardware inserts via analog, the problem exacerbates when you want to use HW inserts with the ADAT or S/PDIF - they were not aligned either so it was not practical to use the digital at all. All fixed in UAD v.7
2. Prioritizes Analog and Digital I/O routing to the driver when using 2 Apollos or 2 Apollo 16s. Pro Tools has a limit of 32 inputs and outputs when used with a Core Audio or ASIO device. One Apollo broadcasts 28 inputs and 24 outputs (a lot of those inputs are virtual paths from the console that can be folded back into Pro Tools). WIth PT Mode + Multi-unit support we made sure that the majority of Analog and Digital I/O gets routed to the 32 available driver I/O slots so customers can get at the physical I/O they bought.”