FIX: Pro Tools “Could not create a new document because Assertion in…”
There’s an easy way to fix this Pro Tools error.
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.21 Comments >
Thanks for this fix! Worked instantly.
yay! thanks! that fixed it!
Doesn’t work for me on a Monday in November. The Moon Phase is also Waning Crescent, I had pasta for lunch and am facing East. I have some vegetable soup in the fridge, I’ll try eating some and will try again. If all else fails, I will consider re-arranging my studio so I am facing South (but I can’t wait until November)… Actually it works if I select the Built-in Output, but when I try to select my interface it complains that it “doesn’t support sampling rate of 48kHz” (which it does).
Hmm…maybe reboot and try it all again. Dunno. If that doesn’t work you may need to burn the whole studio down and start all over.
Yeah, a simple reboot (while facing East) did the trick (should’ve tried it first duh).
Yes! It worked. I guess it also works in February as well. It’s also Friday. I checked and it’s not good Friday. However, it’s very cold outside.
I’m not using the interface at the moment…just the MacBook Pro. Still the message is the same and I don’t know what to do!!!!! Help!
Tried this several times, rebooted and updated macbook and still no luck, any other suggestions?
Thank you so much!!!!
thanks brother you are a life saver lol i was getting frustrated already it worked perfectly for me…..
I’ve been with AVID for two weeks, spinning in all directions, was just about to light the studio on fire and found this.
Thanks for the fix and the entertainment.
Now then, anyone know how to fix the firmware issue “NOT_SET” in Box Pro3?
THANKYOU for this fix! Worked instantly 🙂
Thanks for this fix. Worked instantly!
Thanks for the fix. Worked strait.
OH. MY. WORD. This was driving me nuts! Thank you for the solution!
Haha! PT errors can make one crazy. Glad it worked for you.
Hell ya bro, no more trying to get that old ass M-Audio interface to work, tossing that POS. Every time I try I end up the assertion line 1351 headache.
Thanks for the super simple fix and sharing it.
Worked perfect on a MacPro trash can running High Sierra with Burl B2, Lynx Aurora and Digi 192.