There’s a first time for everything. This is not one of those times.
Blame it on entropy or whatever. Things get messed up. Apple’s OS X is no exception.
In the last few months, I started getting this error a lot:
You are opening the application ”Pro Tools” for the first time. Are you sure you want to open this application?
Except, it’s not true. I open Pro Tools nearly every day. The alert isn’t very important, but it was beginning to get annoying seeing this pop up every time I wanted to record.
So, a little googling and I found an answer on StackExchange. It involves using the command line on your Mac, which can be a bit scary if you’ve never done that before. But it’s a single command, so you should do just fine. Here’s the quick and dirty summary…
This is where the Matrix is on your Mac. There’s no green falling code or woman in the red dress. There may Agent Smiths lurking though.
- Open the Terminal application (found in /Applications/Utilities/).
- Copy the following command (all of it… the whole long line) and paste it after the prompt.
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -all local,system,user
- Hit the Enter/Return key.
- The process will begin. It may take a minute or two to finish. Do not quit the Terminal application while the command is running.
- Eventually the process will complete and another prompt will appear. Now you can quit the Terminal app.
This command resets all of the first run warnings. So any application that requires that will be reset. So you should see the alert one more time for each of those applications and then it will go away for good.
1 Comment >
A friend gave me a Pro Tools session on a thumb drive. I copied the entire session folder to my external hard drive and opened it. After changing the routing to work on my system, everything played back fine. Then I tried to clean up the session.
Every time I attempted to cross fade or consolidate an audio or MIDI region, I would get an error like this:
“Could not complete your request because You do not have appropriate access privileges (-5000)…” Why do you build me up, Buttercup? Capitalize ‘You,’ then award me negative five thousand points…pssh.
Seeing the “access privileges” bit, I figured the problem was probably an operating system issue, not a Pro Tools thing. The session files were indeed set to ‘Read Only,’ which is why I could play back the session, but couldn’t do anything to the regions or fades.
Here’s how to fix the issue.
- Close the session. You shouldn’t have your Pro Tools session open while changing its permissions.
- Select the session folder in Finder. Make sure the session folder is highlighted, not the files inside the session.
- Get Info. Hit Command-I (capital i) or from the Finder menu select File > Get Info. An Info window will pop open.
- Change all privileges to ‘Read & Write.’ At the very bottom of the Info window is a box with a list of users and their privileges. They should all be set to ‘Read & Write.’ You may be asked for user password to unlock and verify the change.
Not listed are NSA permissions, which by default are set to ‘Collect All,’ but, like, totally isn’t a violation of your privacy.
- Close the Info window. After making the privilege changes, try reopening your Pro Tools session and editing some regions. If you can, this fix worked for you.
Why does this error occur?
Many common problems that Macs develop are related to file permissions errors. Files are given various permissions to maintain privacy between computer users and prevent users from easily messing up the operating system.
Permissions can get wrecked when disks are removed without being ejected and during unexpected shut downs. That’s why it is important always to try to eject disks and shut down your Mac properly.
Permissions can also get messed up during copying and moving of files or while installing software. That appears to be why I experienced this error. During the copying of the files, the permissions were never changed to grant me access. Simple problem, simple fix.
After encountering this problem on several other sessions, I tried another method and found a better (and probably more proper) solution. Try this in addition to or instead of the above fix:
In the problematic Pro Tools session, pop open the Disk Allocation dialog (Setup > Disk Allocation…).
When the dialog window opens, you’ll be presented with a list of all the tracks in your session and the location where that track should be located. If you’re having problems creating fade files and getting the sort of error that brought you to this page, then you’ll probably see something like the picture below.
As you can see, not all of the tracks had their disk allocation pointing to the right place. To fix them, select all of the incorrectly allocated tracks, then click and hold the little up/down arrows on the right hand side. A little window will appear and ask you to select a folder. In my case, the session file was looking on my internal system drive instead of my external audio drive. Choose the correct location of your session files and click OK. That should solve the issue. Let me know if this worked for you.
37 Comments >
Those fonts probably aren’t missing.
Error dialog windows can be really frustrating. They pop up and demand your attention, when you just want to get to work on something. Sibelius 7 has thrown this missing font error for me a few times:
There are fonts missing. Sibelius 7 will still work without these fonts, but some scores may not display properly. The missing fonts are: Reprise Std, Reprise Special Std, Reprise Title Std, Reprise Stamp Std, Reprise Rehearsal Std, Reprise Script Std, Reprise Text Std
Most likely the fonts aren’t missing, but simply disabled, which makes the fix really easy. Here’s how to re-enable the “missing” fonts.
First, open the application Font Book. This native OS X font manager should be located in your Mac’s Applications folder.
Second, search for the missing fonts. Font Book has a search field in the upright corner. Type in the names of the missing fonts.
Enabled fonts are shown in black text. Disabled fonts are grayed out and are labeled “Off” on the right hand side.
In my case, all of my “missing” fonts were part of the Reprise family, I typed in “reprise” and all of the fonts in question appeared in the filtered list.
Third, enable the fonts. Select the fonts you want to re-enable. Then hit Shift-Command-D. You can also enable fonts by using the menu bar by selecting Edit > Enable Fonts. The fonts should turn black and the “Off” label will disappear.
I see you checking out my wallpaper.
Lastly, close Font Book and reopen Sibelius. If you enabled all the “missing” fonts, you should be good to go. The error shouldn’t pop up this time, however, it may happen again in the future.
Why does this error occur?
I’ve had to run the fix a couple times now. I don’t know why this error seems to reoccur. If you know why those Reprise fonts sometimes disable themselves, please send me an email or comment below.
Being a graphic artist as well, I know that fonts are notorious for becoming corrupt, conflicting with other fonts, and generally being a hassle to manage. You might think being a musician is a good way to get away from graphic design problems, but unfortunately software like Sibelius relies on fonts to display notation. At least the fix for this error is easy to do and only takes a minute.
The fix I posted above seemed to only work for a while. Occasionally, I would have to run the fix again, which is to say, it wasn’t much of a fix. So, I dug in further and found a real, permanent fix.
The issue was with duplicate fonts. The strange bit was that it wasn’t duplicates of the Reprise family, which was the family of fonts that Sibelius said were missing. Instead it was duplicates of various other fonts that Sibelius uses.
By referencing this forum post and this forum post, I figured out which fonts Sibelius requires and, thus, which ones might be causing problems. Then, for clarity’s sake, in the Font Book application I created a new Collection (File > New Collection or ⌘N). After that I did a search for duplicate fonts (Edit > Look for Enabled Duplicates… or ⌘L) and looked in the Sibelius font collection for any that were flagged. Sure enough, about a third of the fonts that Sibelius uses had duplicate copies. One by one, I “resolved” (deleted) the duplicate fonts, then rebooted. Problem solved.
1 Comment >
This might be the solution.
An unexpected authorization error 14051 occurred.
ID: ePAY : 14051 / Dngl : 1595
I got this error a few days ago. It’s a new one for me. What caused this? Good question. I have no idea. Pro Tools wouldn’t really start after this.
As usual the Avid forums weren’t very helpful. Which led to this tweet…
For the record, at the time the error occurred I was running OS 10.8.4 and Pro Tools 9.0.6 on a Mac Book Pro with an iLok 2.
I had to force quit Pro Tools. Then I unplugged my iLok 2 and plugged it into a different USB jack. Presto. Working again. Not sure what caused it, nor if switching USB jacks was actually the fix, but I did get it working again after doing so. Hope this helps somebody.
I confirmed again that switching which USB jack the iLok 2 was plugged into made the difference. I would think that this is a problem with that particular USB jack, but all other USB devices work just fine plugged in there. Hmm…
5 Comments >
How to get a Pro Tools rig up and running when the error message “The audio device buffer underflowed…” won’t go away.
The Error Message
The audio device buffer underflowed. If this occurs frequently, try decreasing the “H/W Buffer Size” in the Playback Engine panel or remove other devices from the audio firewire bus. (-6085)
Occasionally this error pops up in Pro Tools, usually after I return from a meal in the middle of a long recording or mixing session. The session file will only playback audio for 1 second or less and then the error message pops up. Apparently, Pro Tools 9 is a workaholic and doesn’t like taking lunch breaks, at least when running on the particular combination of MacBook Pro, Mbox 2 Pro, and Western Digital hard drive that I’m using.
Following the directions to decrease the “H/W Buffer Size” in the Playback Engine panel doesn’t seem to help. In fact, not only does decreasing the buffer size seems contrary to the suggested way to solve a buffer underrun, but it then sometimes throws this error message:
A CPU overload occured. If this happens often, try increasing the “H/W Buffer Size” in the Playback Engine Dialog, or removing some plug-ins. (-6101)
I’ve tried a lot of things and the problem seems to be related to the hard drive and firewire ports. Here’s how I fix it.
- Save and Close the session.
- Quit Pro Tools.
- Eject the hard drive used for recording audio.
- Unplug the audio hard drive and Mbox 2 Pro (or the audio interface you’re using).
- Wait 10 seconds.
- Reconnect the audio hard drive and audio interface.
- Restart Pro Tools.
- Reopen the session and press Play.
If the session plays back without stopping, then it worked. If not, then I don’t know what to tell you, which reminds me of a “Deep Thought” by Jack Handey.
If you ever crawl inside an old hollow log and go to sleep, and while you’re in there some guys come and seal up both ends and then put it on a truck and take it to another city, boy, I don’t know what to tell you.
Hopefully this solution worked for you. Let me know if you’ve had the same problem, what hardware you are running and if this solved the problem.
5 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!
31 Comments >