Home »

FIX: Pro Tools “Could not create a new document because Assertion in…”

There’s an easy way to fix this Pro Tools error.

The Problem

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.

The Fix

  1. Quit Pro Tools. (Not forever, just for a moment.)
  2. Restart Pro Tools while holding the ‘N’ key. This forces Pro Tools to ask you which interface to use.
  3. Select your interface.
  4. Boom. No more error, hopefully.

Caveat Emptor

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.



  1. 1 Dave Elvin 9:24 pm Nov 20, 2018

    Thanks for this fix! Worked instantly.


  2. 2 Joel B 2:52 am Jan 19, 2019

    yay! thanks! that fixed it!

  3. 3 Scott Troyer 2:53 pm Jan 28, 2019


  4. 4 Hugo 2:26 pm Jan 28, 2019

    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).

  5. 5 Scott Troyer 2:56 pm Jan 28, 2019

    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.

  6. 6 Hugo 9:32 am Jan 31, 2019

    Yeah, a simple reboot (while facing East) did the trick (should’ve tried it first duh).

  7. 7 Cliff 11:52 pm Feb 22, 2019

    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.

  8. 8 Marcelo 2:15 pm Mar 6, 2019


  9. 9 Kendal 5:38 pm Mar 27, 2019

    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!

  10. 10 Adrian 3:52 pm Apr 1, 2019

    Funciono!! Gracias!!!

  11. 11 Jake 7:59 pm Apr 14, 2019

    Tried this several times, rebooted and updated macbook and still no luck, any other suggestions?

  12. 12 C 4:23 pm Oct 18, 2019

    Thank you so much!!!!

  13. 13 yaiverson 6:37 pm Mar 20, 2020

    thanks brother you are a life saver lol i was getting frustrated already it worked perfectly for me…..

  14. 14 Ronnie Kimball 3:03 pm Apr 10, 2020

    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?

  15. 15 Cassie 9:46 pm Apr 26, 2020

    THANKYOU for this fix! Worked instantly 🙂

  16. 16 Cassie 9:47 pm Apr 26, 2020

    Thanks for this fix. Worked instantly!

  17. 17 JRD 12:01 pm Feb 13, 2021

    Thanks for the fix. Worked strait.

  18. 18 Tony R 8:54 pm Mar 25, 2021

    OH. MY. WORD. This was driving me nuts! Thank you for the solution!

  19. 19 Scott Troyer 3:02 pm Mar 26, 2021

    Haha! PT errors can make one crazy. Glad it worked for you.

  20. 20 David Scott 2:53 pm Dec 20, 2022

    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.

    David Scott

  21. 21 Barry Dubis 5:04 pm Feb 25, 2023

    Worked perfect on a MacPro trash can running High Sierra with Burl B2, Lynx Aurora and Digi 192.


Leave a Reply