Here is how I fix this Pro Tools error.
Really? A typo in the error? Grrrrr…
Ever get this error? Can’t open your session, right? Not only is it a major workflow stopper, but the double punctuation typo at the end is annoying as well.
Luckily, the solution is quite simple.
This is the quick fix that works for me and my particular setup of hardware/software. Your mileage may vary.
- Quit Pro Tools
- Restart Pro Tools
- Open the session that wouldn’t open before
- Get back to work
The IT mantra “Have you tried turning if off and on again?” waves the problem away like a magic wand, but why is this problem happening in the first place?
The last time this error occurred for me, I noticed that it was after I had ejected my audio hard drive, removed my iLok, and left Pro Tools open, but put my machine to sleep before Pro Tools could issue the panic message: “Hey! Where’s your iLok, buddy?! That’s it! We’re shutting this whole thing down.” Then when I went to reopen the last session I was working on, boom, the error in question occured.
I’m guessing that between the time I ejected everything and the time I plugged it all back in and tried to fire it up again, Pro Tools had switched its default sample rate from whatever my Mbox 2 Pro says it was to whatever my MacBook Pro thinks it should be. Then when I try to open a session with a particular sample rate that doesn’t jive with what the current rate is, Pro Tools freaks out because it thought it knew what was right, but doesn’t even know anymore, man.
Disclaimer: I don’t actually know how or why the error is occurring. These are just my slightly educated stabs in the dark. If you know anything more about this error, why it happens, and, most importantly, why there’s a typo in it, please leave your thoughts in the comments section below.
No Comments >
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.
10 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.
After upgrading to the newly released Pro Tools 9, I couldn’t open sessions or create new ones. I got this error: “Could not complete the Open Session… command because Pro Tools could not set sample rate to specified value..” I hunted around on the web and various forums, but couldn’t find a solution that fit. […]
After upgrading to the newly released Pro Tools 9, I couldn’t open sessions or create new ones. I got this error: “Could not complete the Open Session… command because Pro Tools could not set sample rate to specified value..” I hunted around on the web and various forums, but couldn’t find a solution that fit. I found several items relating to Windows and Pro Tools 8, but nothing for a Mac running Pro Tools 9. After messing around a bit I figured out the problem was with my playback engine. Here’s how I solved it. Let me know if it works for you too.
Open the Playback Engine dialog under the Setup menu item.
From the menu bar select Setup > Playback Engine… to open the Playback Engine dialog window.
The problem is with the Pro Tools Aggregate I/O.
By default, my current engine was set to “Pro Tools Aggregate I/O.” It’s odd that this Pro Tools would leave it that way after an installation since AVID states that it is not supported in OS X.
Select your current playback engine.
The fix is easy. Simply select the right playback engine. Your options may differ based on your setup.
In my case, I usually would edit with my Mbox 2 Micro, but since Pro Tools 9 gives us so many more options for hardware compatibility, I selected Built-in Output. I was able to edit some vocal takes using my Macbook Pro’s speakers instead of pulling out my headphones. Nice!
29 Comments >