What the heck is this? "Assertion in... Line 1045"

[sololi]

In my case, I've found a solution. This error is related to hard drive. My computer is a Mac, but I have a WIN NT drive mounted, after I unmount the drive, it finally worked.

Also, sometime it may caused by a wrong name of your hard drive, remember never have same name of two drives, alway use English character as drive name.

[SevenRising]

I just had one of these crashes as well when messing with Elastic Audio. It was weird because all the menus in PT were all grayed out after that message.

Originally Posted by Pedro perez

Could not complete your request because Assertion in "/Volumes/Development/158347/ProTools/NewFileLibs/FF/Audio/FF_AudioFile.cpp", line 1045.

(Use the Copy button to copy this message to the clipboard.).

[cathedral recording]

check your clock. this happened to me and i discovered that the session was a 98k and the interface clock (apollo twin)was stuck in 44.

[Ted Blaisdell]

Originally Posted by Rich Breen

Also, move the project to a different drive, disconnect the current drive, and see if that helps.

Yeah Rich! Thanks!

[Rich Breen]

ha! hi Ted!

[LesPaul2550]

Originally Posted by sololi

In my case, I've found a solution. This error is related to hard drive. My computer is a Mac, but I have a WIN NT drive mounted, after I unmount the drive, it finally worked.

Also, sometime it may caused by a wrong name of your hard drive, remember never have same name of two drives, alway use English character as drive name.

Solution to above with Paragon NTFS:::

Pro Tools 12.7.x and 12.8 have issues with Paragon NTFS when not running the very latest version of Paragon. I struggled with this for months (as well as other 12.7.x bugs). Update Paragon NTFS to version 15 (as of this writing) since Pro Fools has issues with 14. Worked okay using PT12.6.1 but nothing newer without corrupt WAV files. Once I upgraded to 12.8 I found the WAV files as well as session files were locked!!! Never saw that before nor did I see anything about it in a google search. Figured it out on my own though. For years I've used an NTFS partition as my data drive without incident with older versions of OS X and Pro Tools. By using an NTFS formatted drive, I can easily switch via bootcamp to Windows in case I'm having an issue with Pro Tools or a plugin under OS X. It also enables me to take my external 3 terabyte drive with me and track with my PC laptop without having to copy crap to another drive, remember to copy it back when done, blah blah blah. I just know someone is going to nag that doing this isn't supported but tough... it SHOULD be supported especially since Apple is creating yet another format for hard drive partitions with the upcoming High Sierra OS. Fudge them and their constantly moving target called OS X!!! I'll stick to my NTFS external data drive, thank you very much. It also is necessary since I sometimes need to quickly open files in Sonar which recently announced they've dropped plans for an OS X version .

Here's an easy way to find out which WAV file is corrupt... open your Audio Files folder, then open each WAV file with QuickTime until you find the ones it say's it can't import. Those are the corrupt ones and anything in them is lost and must be retracked or recreated.

I lost vocals on the same session TWICE due to this error. After updating to Paragon NTFS 15 and attempting to track vox a third time, it finally worked and has since then (1 week now and counting).