Could not create a new document because Assertion in “/Volumes/Development/223020/ProTools/DFW/Views/UMenu.MacOS.mm”, line 1813. (Use the Copy button to copy this message to the clipboard.).
Pro Tools 2018Â error
If you get this error, it’s likely due to Pro Tools trying to use the wrong audio interface.
Quit Pro Tools. (Not forever, just for a moment.)
Restart Pro Tools while holding the ‘N’ key. This forces Pro Tools to ask you which interface to use.
Select your interface.
Boom. No more error, hopefully.
This worked for me on a Mac Pro trashcan running macOS High Sierra 10.13.6 and Pro Tools 2018.7.0 on a Tuesday in November. The Moon phase wasÂ Waning Crescent. I had vegetable soup for lunch and was facing South at the time of the error. Your mileage may vary.
On a recent session, I was given 24-bit 96kHz stems to which I need to add acoustic guitar. Since I nearly always record 24-bit 48kHz, the higher sample rate is not familiar territory for me, but it didn’t seem like it would be an issue.
To set up for the session, I switched both my RM32AI and Pro Tools to the higher sample rate and restarted Pro Tools. I thought that was enough.
On the CS18AI I could see the meters bouncing, but no audio was passing to the speakers. I tried switching back to 48kHz and everything worked fine. Audio simply would not pass through at 96kHz.
After troubleshooting using every bit of Google foo I knew, I finally found a forum post that enlightened me. One of the shortcomings of AVB networking is that it can only pass audio at 48kHz or lower sample rates. Boom.
I had been using the monitor outputs of the CS18AI to send mains audio to my studio speakers. The CS18AI receives it’s audio feed via AVB, which is why audio was passing fine at 48kHz, but not 96kHz.
The fix was simple: unplug the cables from the monitor outputs of the CS18AI and plug them into main outputs of the RM32AI. Problem solved.
Here’s hoping this prevents some hair-pulling frustration for you.
You want to record audio in the modern age? You donâ€™t have a Zildjillion dollars to be able to record to tape? Even so, it all ends up digital. You need some hard drives.
Five Audio Recording Hard Disk Drive Tips
Hard disk drives arenâ€™t all the same. Picking out the right one can be tough. Here are some things Iâ€™ve learned â€” sometimes the hard way.
1. Heed the DAW makersâ€™ suggestions.
If AVID says that Pro Tools doesnâ€™t support it, donâ€™t expect it to work. Legit DAW makers will post the system requirements for their software/hardware. Look them up. Follow their recommendations and instructions. Spoiler: Youâ€™re probably going to have to spend more than you had planned for.
2. Faster is better.
A faster drive means it read/writes faster. And faster read/writes means more tracks and/or higher quality.
Traditional hard disk drives have platters that spin. A hard disk drive that spins at 5200 rpm really isn’t fast enough â€” itâ€™s like red-lining a Geo Metro. 7200 rpm is better. 10,000 rpm better still.
And then thereâ€™s flash drives, which are way faster than hard disk drives.
There are also seek times to consider, for which lower numbers are better. Seek time is the baseline amount of time in milliseconds that it takes for a drive to fetch data.
I have found that drive manufacturers donâ€™t always make these stats readily available. When in doubt, assume the drive doesnâ€™t meet spec (because it likely doesnâ€™t).
3. Data interfaces matter.
Hard drives have come with lots of data interface flavors: PATA, SATA, USB (1, 2, 3), FireWire (400, 800), Thunderbolt, Ethernet, and some are even wireless. The data interface dictates bandwidth, which roughly translates to how many tracks you can record at once and how much latency your playback will suffer. More bandwidth is better, which translates into better recording and mixing experiences. Again, check your DAW makerâ€™s system requirements and choose the drive with the fastest and most forward-compatible data interface.
Also make sure your computer can handle the data interface type youâ€™re choosing. And find out if the data port you intend to use on your computer is sharing a bus with any other peripherals in your computer. That can adversely affect your bandwidth, causing a data bottleneck.
4. Bigger isnâ€™t better.
For tracking and mixing, you donâ€™t necessarily need a 3 TB drive. (Unless, of course, youâ€™re recording a 10-piece prog-rock group with 40 minute “works” at 32-bit 192kHz.) Save the big, slow drives for backups and archiving. Use smaller, faster drives for works in progress. If you have more than one project going at a time, consider using a small drive for each project, so the different project files are not interleaved with each other on the drive. This will speed up read/write times, as the drive will not be jumping around on the platters trying to find the files for the current session. This also saves money, since really fast and really big drives are expensive.
5. Always have a backup.
Have a backup plan, because hard drives fail. All the time. More so than any other part of a computer. Make sure to always backup your work after every session, whether recording, editing, or mixing. And make sure you have an extra drive ready in case one goes down during a session. I canâ€™t stress this enough. Millions of ones and zeros (i.e. your priceless recordings) can go poof at any time â€” and thereâ€™s never a right time for that. Buy more hard drives. Make backups like a chronic. Sleep well.
So there you have it: my top five hard drive tips. Comment below to let me know what you would add to the list.
And enjoy some “Tainted Love” made with old hard disk and floppy disk drives…
After doing a fresh install of Pro Tools and my Waves plugins, this Waves 9.2.100 Preferences dialog window (pictured below) kept popping up every time I fired up Pro Tools.
Checking the “Don’t ask me again” checkbox didnâ€™t seem to be working.
I searched for some solutions on the Google machine and found some forums were recommending a complete uninstall and reinstall of all Waves plugins. This didnâ€™t seem necessary. Hereâ€™s the fix I used:
Quit Pro Tools.
Trash the entire Waves Preferences folder. The folder is located in the Preferences folder in your user Library folder, not your system Library folder. A quick way to locate the folder is to switch to the Finder and hit Shift+Command+G. A Go to Folder dialog window will pop up. Copy and paste the following line in that field and hit enter.
Put that folder in the trash and empty the trash.
Start Pro Tools.
A window should pop up asking you to select the Waves 9.2 Plug-Ins folder. By default, it should be located in the Waves folder in your Applications folder.
Once youâ€™ve located the folder, click Open.
The Waves 9.2.100 Preferences dialog window should pop up again. The “Don’t ask me again” box should be checked. If not, check it and hit OK.
To test if everything worked, quit Pro Tools and start it again. The Waves dialog window shouldnâ€™t reappear.
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.
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.
Appleâ€™s GarageBand makes it relatively easy to sketch out an audio demo, but it does have some severe, intentionally-crippled limitations.
One of the biggest drawbacks is the lack of built-in support for exporting MIDI data.
Performances are stored inside the session file in some sort of MIDI fashion, but Apple doesnâ€™t give users an easy way to get that information out. Major bummer. *looks west towards Cupertino, squints eyes, shakes fist in air, mutters under breath*
However, a nice guy named Lars Kobbe has put together a workaround/hack that extracts MIDI data from the reluctant clutches of GarageBand. You can download his GB2MIDI Apple droplet script from his site: MIDI-Export in Apples Garageband. Here’s the direct download: GB2MIDI.ZIP If that link doesn’t work, I’m providing the file hosted on my site here: GB2MIDI.ZIP
The article is in German, but instructions in English are found near the bottom of the article (just before the comments section). Getting the MIDI data out involves several steps. Hereâ€™s my summary of the process.
How to Extract MIDI Data from GarageBand
Join (Command-J) regions of a track you want to export
Convert that region to a loop via Edit > Add to Loop Library (NOTE: In GarageBand 10.1.0 this menu item is now located under File > Add Region to Loop Library )
Find the newly created loop file (an .AIF with MIDI data hidden inside it) in the folder: Macintosh HD (or whatever your system drive is named)/Users/(your home folder)/Library/Audio/Apple Loops/User Loops/SingleFiles/
or the abbreviated: ~/Library/Audio/Apple Loops/User Loops/SingleFiles/
Drop that .AIF file on Larsâ€™ GB2MIDI droplet
Grab the freshly extracted .MID file, which should appear in the same folder where the .AIF loop was. If not, see the comment section below.
Import the .MID file into a respectable DAW (basically almost anything other than GarageBand).
Make next hit record.
That last step is optional, but I say go for it. 😉 Let me know if this helped you.
If youâ€™re having trouble locating the loop file, it may be because your Library and/or Users folders are hidden, as later OS X versions have been wont to do.
To unhide the Library folder, open the Terminal application, which is found in the /Applications/Utilities/ folder. At the prompt type the following: chflags nohidden ~/Library/
To unhide the Users folder, type this into Terminal: sudo chflags nohidden /Users
Then enter your administrator password.
Look for the newly unhidden Users folder in your hard driveâ€™s root folder. It should look something like this:
After running “sudo chflags no hidden /Users” you should see the Users folder (highlighted in red in the image above) appear under the root folder of your hard drive (often named “Macintosh HD” by default).
This GarageBand MIDI article has regularly been one of the most popular posts on my site. That means there are a lot of people using GarageBand and discovering its unfortunate MIDI limitations. The best bit of advice I can give to any musician or audio engineer still using GarageBand is STOP. I know that may sound harsh, but GarageBand is intentionally made to be consumer-grade software. If youâ€™re serious about recording, take the time to investigate other DAWs. Find an alternative solution. There are many to choose from and nearly every one of them is less limited than GarageBand. They range from super affordable to â€œprofessionally priced.â€ Hereâ€™s a list to get you started. (Some links are affiliated.)
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.
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…
A smart guy named Helmut Haas discovered a bunch of cool things about the way our human brains decode the sounds we hear to determine the direction of where those sounds originate.
Back in 1949, Mr. Haas found that early reflections of sounds help our brains decipher where the sounds came from. We can tell a noise came from the left not simply because we hear it in our left ear, but also because the sound bounces off a wall to our right and hits our right ear a very short time after it hit our left ear. Almost instantaneously, the brain detects the short time between the two signals and tells us, â€œHey, that sound you just heard came from your left. Better turn your head to see what it was!â€ This happens so quickly that we donâ€™t really even think about it. We just â€œknowâ€ it came from the left.
Haas also recognized that early reflections are basically copies of the initial sound that are delayed slightly. He started messing with peopleâ€™s heads. He pointed speakers at them and firing sounds with very short delay differences. Then he asked the test subjects which direction the sound seemed to come from.
His conclusion: Not only is it fun to play with sounds, but also 40 ms (milliseconds) is some kind of magic point for our brains. If an echo is more than 40 ms after the initial sound, then we hear the sounds as separate instances. But if the delays happen within 40 ms or less of each other, then we perceive them together as merely directionality cues of a single sound.
For example, if a sound hits our right ear and the same sound hits our left ear 0.3 ms later, we donâ€™t hear two sounds, we only hear one sound coming from approximately our 1 oâ€™clock position.
Engineers have implemented the Haas effect as an alternative to panning. Most of the time panning works just fine, but it does have limits.
Sometimes panning leaves the location of the audio feeling indeterminate, smeared, mono, or one dimensional. This is why a lot of engineers skip the pan knob altogether and mix LCR.
To effectively localize a track in a stereo field using the Haas effect, engineers have to do a couple things. They duplicate the track, pan the two tracks hard left and right, and then apply a delay to only one of the sides. The delay is applied to the side opposite of the side from which the sound is intended to perceived as originating.
Typical delay times for this technique are increments of 0.1 ms from 0.1 to 0.7 ms. This yields linear movement across the stereo field. You can think of it like this chart shows.
Example: Want the sound to come from 9 o’clock on the left? Delay the right side by about 0.4 or 0.5 ms.
After researching the Haas Effect, I decided I wanted to try it out in a mix. Since the settings must be very exact, setting it up correctly can be a bit confusing. Presets to the rescue!
I made these presets for the stock Digidesign Mod Delay II plug-in. These presets only work for this specific plug-in and Pro Tools. If thereâ€™s interest, maybe Iâ€™ll make more presets for other DAWs in the future.
Download this ZIP file, unzip it, and drop the folder and included presets in the Mod Delay II folder in the Plug-in Settings folder. On a Mac itâ€™s probably located at Library / Application Support / Digidesign / Plug-In Settings / Mod Delay II, but may be in a different location on your system.
Setting up the tracks
Insert an instance of the Mod Delay II (mono/stereo) plug-in on the mono track you want to Haas-ify. Select the preset you want. No need to duplicate tracks. Bingo.
Understanding how to use the Haas effect properly means you need to understand and pay attention to things like stereo-to-mono compatibility and comb filtering, as well as other stereo field mixing techniques. As with all effects, have fun but be careful not to over do it. Experiment and do your homework. Then let me know if you find learn or discover anything cool. Hereâ€™s a cool video that got me thinking about the Haas effect.This video no longer available.
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.
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 Digitalhard 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.
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.
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.
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 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!