Back to Blog
Avid pro tools first login problems6/30/2023 ![]() That needs to be done thru Windows before starting PT. AVID did add a Windows audio driver to PT 12 ("Windows Audio Device"), but PT can't set its sample rate either. That's why you need ASIO4ALL (which makes the computer sound card look a standard PT ASIO interface). Good luck and please let me know how this works for you! Note that ASIO4ALL (with your computer’s own non-HDMI audio device) will likely satisfy all of your non-recording needs and, unlike PT12’s new “Windows Audio Device” (and likely any other) “Playback Engine”, PT seems to be able to change its sample rate directly and correctly.ġ4. If PT screwed it up, you should probably restart your computer first.ġ3. Regardless of the cause you’ll need to repeat steps 4 – 11. I’ve also seen it think my third party devices were “Avid Hardware” and “HD Hardware”. You should be good to go with your audio interface until you need to change sample rates or interfaces (or PT decides to screw things up for you.) I’ve seen PT change interface sample rates while just closing and re-opening a session. Pro Tools will remember that you last used ASIO4ALL at that sample rate, so you’ll need to change it via “Playback Engine” in the “Setup” dropdown menuġ2. Restart Pro Tools and open the session that you created with ASIO4ALLġ1. Use your audio interface’s control panel to set it’s sample rate to whatever you selected in that Pro Tools sessionġ0. Turn on or re-connect you audio interfaceĩ. Create a new session at whatever sample rate you want to use with your audio interfaceĨ. Turn off or unplug your audio interface (“Playback Engine”)Ħ. Download and install the latest version of ASIO4ALL (its Instruction Manual will appear in your “OS(C:) Program Files (X86), ASIOALL v2” folder) in case you ever need them (likely not now)Ĥ. This post doesn’t address the problems associated with changing buffer sizes - that’s for a future post (if there’s sufficient interest shown in this one).ģ. (Many of the reported startup issues currently being reported by PT 12 users are likely caused by this bug). Here’s the workaround that I developed to help mitigate some of these problems (when changing sample rates and interfaces) and help ensure that Pro Tools 12 starts/re-starts reliably. ![]() My experience that other DAWs don’t exhibit these types of problems (except with AVID devices) strongly suggest that it’s a problem with Pro Tools, not the devices themselves. Although that thread was about “third party” interfaces, AVID’s own interfaces (at least it’s Fast Track Duo and Eleven Rack) have similar problems. ![]() Pro Tools’ inability to work properly with Windows (ASIO) audio interfaces has been well documented on the DUC (i.e. explains how to set the PT's (and ASIO4ALL's) buffer size(s) to avoid sound dropouts during playback. has a link to an excellent video showing how to setup ASIO4ALL for use as a Pro Tools "Playback Engine". Details are provided at ĪugUpdate - The simplified process doesn't work on my son's PT12.1 - Dell Windows 8.1 laptop. Important JUpdate: I just learned about a feature available in PT that can greatly simplify this process. ![]()
0 Comments
Read More
Leave a Reply. |