Can't open a project. Internal error: parameter error (-50)

[lamusiclab]

When I try to open a project and any of its backups, after the initial loading progress bar is about 2/3 of the way done, I get the following message:

An Error occurred while reading from the desk. The files/volumes/ name of project/.dpdoc was not loaded.
OS error: internal parameter error (-50).

This is a big expensive orchestral recording and it is vital that I can work on it and deliver it to my client.

A solution would be greatly appreciated.

I already tried creating a new project and importing the chunks with the same result. I also tried copying the project to a different hard drive. That didn't help either.

Maybe it is an error with one of the associated files (soundbites, analysis, overview...) what can I do?

[FMiguelez]

I'm so sorry to hear about that!

Additional things to try>

- Trash Analysis and Clippings folder
- Trash audio files temporarily and see if it opens. There may be a corrupted audio file in there

- Try opening DP in Safe mode, without any 3rd-party plugins

- Try opening it with an earlier DP version, such as 9.02 or 8.xx.
This works quite often, and I've rescued most corrupted DP projects like this

- Try the above but opening it with a different computer

- Open OSX Console, and make a search for DP or MOTU. See what it reports at the time it tries to open the faulty project. In lots of cases DP is trying to find or load something that it confuses it, such as Mackie console or a duplicates Waves path, etc.
This is another way I've had success opening faulty projects too.

- Zip/Unzip (though I'm not sure what that's supposed to do, but I've read that tip in the forum)

- Chant to Moctezuma...

[beatzart]

- Try opening DP in Safe mode, without any 3rd-party plugins

Thanks so much for reminding me about safe mode, I also had an important project that kept crashing DP10.11. After opening in safe mode, I removed 3 instances of izotope Vocal Synth2 on some vocal aux tracks, and lo and behold, all is restored! Seems this plug-in was also causing CPU max out and memory warnings.

Hope the OP has similar luck.

[mikehalloran]

Is this a Mac?

[lamusiclab]

Yes, a 2010 Mac Pro, 3.33GHz 6-Core Intel Xeon with 32 GB 1333MHz DDR3 memory, SSD system amd application hard drive, ATI Radeon HD 5770 1024 MB Graphics card...