Can't create new document because of assertion error 1351...

[caleriggs]

Hey everyone, I'm having trouble getting Pro Tools to open a new session. It says verbatim

Could not creat a new document because Assertion in "/Volumes/Development/ws.Encore/AlturaPorts/DFW/MacBuild/../Views/UMenu.MacOS.mm", line 1351.

After Googling the problem and then deleting all kinds of preferences and folders and everything I could possibly find to fix the problem, it still persists. Do any of you have any ideas how to help me figure this problem out?

Here's my machine specs: MacBook Pro Intel Core i5, 8GB Ram, Mac OSX 10.7

Thanks!!!
Cale Riggs
@caleriggs - twitter

[Darryl Ramm]

Originally Posted by caleriggs

Hey everyone, I'm having trouble getting Pro Tools to open a new session. It says verbatim

Could not creat a new document because Assertion in "/Volumes/Development/ws.Encore/AlturaPorts/DFW/MacBuild/../Views/UMenu.MacOS.mm", line 1351.

After Googling the problem and then deleting all kinds of preferences and folders and everything I could possibly find to fix the problem, it still persists. Do any of you have any ideas how to help me figure this problem out?

Here's my machine specs: MacBook Pro Intel Core i5, 8GB Ram, Mac OSX 10.7

Thanks!!!
Cale Riggs
@caleriggs - twitter

What version of Pro Tools?

Trashing prefs may fix this. Make sure you are deleting everything you are supposed to. See http://duc.avid.com/showthread.php?t=54888. Also do a full reboot after doing this.

If all else fails I would try a full uninstall and reinstall of Pro Tools.

Darryl

[caleriggs]

A buddy of mine in town actually figured it out. I still had the Playback Engine set for Dante cards, so unless I had those plugged in it wouldn't recognize the playback engine, thus giving me that warning. I opened Pro Tools and reset everything to default in the I/O and Playback Engine, and it fixed it! Thanks for the reply!

[starsweeper]

Press "n" as PT boots up. Then change your output device to what you are using. If that fails, try using your Internal Output- which will enable you to at least get past that message- and go back into your setup to select the output device that you use

[revans]

I also found that if I turned off Bluetooth, Pro Tools would start up without the "line 1351" error.

I saw I had an old Jawbone Bluetooth headset (that I stopped using long ago) listed among the devices in the Bluetooth System Preferences window. I deleted that obsolete device from the device list, turn on Bluetooth again, and when I restarted Pro Tools again it started with no problems. Go figure.

[shultzee13]

Originally Posted by starsweeper

Press "n" as PT boots up. Then change your output device to what you are using. If that fails, try using your Internal Output- which will enable you to at least get past that message- and go back into your setup to select the output device that you use

That's interesting. Will have to try that. I'll report back. BTW - Thanks for the quick tip!

[architectspiders]

booting pro tools with 'n' and picking a different output fixed this for me.


thanks

[Mike Mckikdrum]

If this error still persists after trying the above fixes,try repair disk permissions in the disk utility,then go back and set up your default device in the Audio Midi utility.Worked like a charm,after trying all of the above.

[King Lou]

Tried fixing permissions, updating to 10.3.3 (was happening in 10.3.2) and a full clean install.

AVID has a FAQ about it

http://avid.force.com/pkb/articles/e...1&x=-934&y=-20

This didn't help at all. All the full clean install did was make me have to go through the stupid iLok registration hoops all over again. Now I have to dig out all the annoying registration cards and nonsense.

Once again there is a months long issue with Pro Tools and no definitive fix.

[Craig F]

Originally Posted by King Lou

This didn't help at all. All the full clean install did was make me have to go through the stupid iLok registration hoops all over again. Now I have to dig out all the annoying registration cards and nonsense.

then you have some deep system problems, once the iLok is authorized the card is spent

I take one system, update and tweak it, image it, then deploy it to 70 odd computes, pull the iLoks/ update/replace if needed, and let the student use them