Pro Tools hardware is either not installed or used by another program. If you thought that having Pro Tools 9 installed meant no more “Hey, Mr. Engineer Genius, where’s your fancy hardware?” errors, then this nagging error probably came as a surprise. It did for me. Since installing Pro Tools 9, my workflow has allowed [...]
Pro Tools hardware is either not installed or used by another program.
If you thought that having Pro Tools 9 installed meant no more “Hey, Mr. Engineer Genius, where’s your fancy hardware?” errors, then this nagging error probably came as a surprise. It did for me. Since installing Pro Tools 9, my workflow has allowed me to jump around from my Mbox 2 Pro, Mbox 2 Micro, and MacBook Pro’s built-in sound card. This has been really handy while trying to finish up my album on the road. But, apparently, all that hardware hopping can cause the playback engine to get stuck in some funky states that don’t so work –if at all. See my previous post “FIX: Pro Tools could not set sample rate to specified value” for a similar issue.
Obviously, the problem has something to do with the playback engine. Since the error dialog only offers an ‘OK’ button, which closes Pro Tools, there doesn’t seem to be a way to work around the problem. There is not even a way to know what hardware Pro Tools is expecting.
I found a simple solution via this Sweetwater forum. The answer given there details how to get Pro Tools running on a PC, but I found that it worked for Macs too and without having to install any drivers. The fix is kind of like booting Pro Tools in safe mode. Simply hold the ‘N’ key while starting up Pro Tools. This will bypass the normal start up sequence and open up the Playback Engine window. Now you can select the correct playback engine and continue using Pro Tools.
In my situation, Pro Tools was looking for the last connected device (my Mbox 2 Pro), but since it wasn’t available it opted for the next available option: my MacBook Pro’s line input, which doesn’t make a very good playback engine.
Let me know if this fix worked for you.
2 Comments >
This problem may have been fixed in the Pro Tools 9.0.2 update that came out yesterday, though I’ve not been able look through the 9.0.2 Readme file in detail or to test this out on the updated software. I’ll update this page when I find out more.