DP 7.22 won't open last weeks projects

[kassonica]

Did you try the file extension change?

Yes. Both. 7.22 just sat there. Though thanks for staying on things James.

Even if that did work who would be happy having to manually add file extensions to their DP projects when even the simplest Mac application can ID and open files it created.

Have you repaired the disk (and permissions) off your install disk?

[Tuxtla]

Can you start a "New" file in DP 7.22? And if so, have you tried using
"Load" to then load an older project?

This is all mysterious. I'm having absolutely no issues at all opening
older projects, whether they're last week's, or from a year ago.

Yes - I can create new projects in 7.22 and I have tried using LOAD but the same files that will not open directly in the App are not recognized.

Good to hear things are working for you. I've been a DP user for years and haven't had too many problems moving from one version up to another. Those were normally associated with older plug-ins. I've checked about a dozen projects dating back to last January and there are 5 that won't open in 7.22 however - some that do open immediately crash on playback.

[Tuxtla]

Did you try the file extension change?

Yes. Both. 7.22 just sat there. Though thanks for staying on things James.

Even if that did work who would be happy having to manually add file extensions to their DP projects when even the simplest Mac application can ID and open files it created.

Have you repaired the disk (and permissions) off your install disk?

Yes. Once with Disk Utility and then rebooted in to Applejack as well. Very few repairs.

I'll briefly add here that close to half of my income comes from maintaing and repairing Macs. I've been using them since the Mac Plus. I know them well and my system and disks are always in tip-top shape.

This AM I ran Disk Warrior's "Check Files" function on my external Audio HD and on a second backup drive and on EVERY 7.21 project (16 of them) I've been working on since it came out DW reported the following - I include one report here:

File: "Smash Cut Masters"! Detected that the resources overlap and cannot be repaired! Location: "1.5 Archives/Audio Store/Show Masters/Smash-Cut DP Masters/Smash Cut Masters Project/"!

I'm not sure what to make of those results because all of those project files open in 7.21 and "some" of them open in 7.22.

[Tuxtla]

Did you try the file extension change?

Well there are utilities that allow you to rename files easily. Also keep on mind that this issue isn't affecting mist people and I'd be willing to bet it never came up during MOTU's beta testing or they wouldn't have released it. Any chance you can post a project file?

Hiya James. Thanks for the offer to take a look.

I just prepared a project that would not open in 7.22 to send for examination. I opened the project in 7.21 - played the main sequence through and tested all the v-racks (3) and plug-ins (5). I then deleted all tracks except for one minute of a single stereo track to keep the project small. I removed all v-racks, busses and plug-ins, deleted all unused audio tracks and compacted the project. And then it DID open in 7.22 but of course there's nothing left of the original project save the 1 minute of audio.

I have to step out but will try again later today.

[Tuxtla]

Well there are utilities that allow you to rename files easily. Also keep on mind that this issue isn't affecting mist people and I'd be willing to bet it never came up during MOTU's beta testing or they wouldn't have released it. Any chance you can post a project file?

Thanks for the offer to post a file J. MOTU have responded to my Tech link so I'll pursue it with them. Should they have any good news I'll post it here.

R

[Steve B]

This AM I ran Disk Warrior's "Check Files" function on my external Audio HD and on a second backup drive and on EVERY 7.21 project (16 of them) I've been working on since it came out DW reported the following - I include one report here:

File: "Smash Cut Masters"! Detected that the resources overlap and cannot be repaired! Location: "1.5 Archives/Audio Store/Show Masters/Smash-Cut DP Masters/Smash Cut Masters Project/"!

I've been having some instability in DP and just ran Disk Warrior's "Check Files" and I get the same error for what appears at first glance to be all my recent DP files, including the templates I use to create projects. I was about to rebuild all my templates but there's no point if opening them in DP is going to scramble them again.

Does appear to be a bug in DP 7.21 & 7.22?

Do you have any ideas what I should do about it (if anything)?

Thanks in advance,
Steve = : ^ )

[David Polich]

This AM I ran Disk Warrior's "Check Files" function on my external Audio HD and on a second backup drive and on EVERY 7.21 project (16 of them) I've been working on since it came out DW reported the following - I include one report here:

File: "Smash Cut Masters"! Detected that the resources overlap and cannot be repaired! Location: "1.5 Archives/Audio Store/Show Masters/Smash-Cut DP Masters/Smash Cut Masters Project/"!

I've been having some instability in DP and just ran Disk Warrior's "Check Files" and I get the same error for what appears at first glance to be all my recent DP files, including the templates I use to create projects. I was about to rebuild all my templates but there's no point if opening them in DP is going to scramble them again.

Does appear to be a bug in DP 7.21 & 7.22?

Do you have any ideas what I should do about it (if anything)?

Thanks in advance,
Steve = : ^ )

It really helps to post your setup..without that info it's difficult to
answer.

Look, here's the thing - it could be any number of factors that are
causing projects to fail to load correctly. It could be certain VI's that
don't work in 7.22, whereas they did in 7.21. I notice one common thing
in a lot of posts like this - VI's are running in V-racks.

If you have no problems with a project started in 7.22, that
would indicate that it is probably something to do with your plugs or VI's.

You can always go back to 7.21, export the project as a Standard MIDI file
type 1, and start over. Believe me, there have been numerous times in my
life when I've done just that. Interestingly, every time I've started again
from scratch, I've ended up with better tracks, a better arrangement, and a better mix.

[Steve B]

Thanks for the reply. I should have mentioned that much of my work involves opening a template then importing an old DP file and editing it, and I have had zero problems with opening and/or loading files. I just happened to run Disk Warrior's 'Check Files' and found that it discovered an unfixable problem with all my recent DP files. I assumed my templates had become corrupted and this had led to the files I'd created from them being corrupted, but I Googled the error and found this thread, and realised it's not just me.

I'd be interested to know if anyone else out there has run Disk Warrior's 'Check Files' function on a disk containing recent DP files. It may be that all recent DP files have this problem - remember, I had no symptoms, no problems with opening or loading files; it was a routine check that uncovered the problem that Disk Warrior is reporting.

Thanks again,
Steve = : ^ )

[James Steele]

DP 7.21 had a small bug that would sometimes cause project files saved from DP 7.21 to be reported by apps like this. Simply opening the project and re-saving fixed it. It was rather benign though. You would not encounter problems opening or playing the project.

[Steve B]

Thanks James. I read most of what is posted to Motu-Mac but hadn't heard that. I'm now going to ignore it.

Steve = : ^ )

[James Steele]

I should have said opening and resaving the project file WITH DP 7.22 fixes the problem.

[GCBASS]

Hi, I had the same problem, motu could not help but i have found a solution fellow this:
ERROR -39 with 7.22 (7.22 won’t open or load file not save as 7.22)

I find a solution:


A NEW TRICK!
By this you will know that error 39 is not related to plug ins, or special
way of using DP 7.22
I just discorver that any file (dp file of course) that 7.22
won't open by indicating error -39

YOU JUST NEED TO AD TO THE END OF NAME OF THE FILE .AUTOSAVE
and it will open
the same file that won't open >>>>now do!

ex.: P-Lessons in love.mid (7.22 give a error -39)
same file with ad: P-Lessons in love.mid.autosave (now 7.22 will open it)

and with that now the logo DP stamp will appear
with the new name of the file instead of MIDI

Weird! YES -but work.

[1nput0utput]

Hi, I had the same problem, motu could not help but i have found a solution fellow this:
ERROR -39 with 7.22 (7.22 won’t open or load file not save as 7.22)

I find a solution:


A NEW TRICK!
By this you will know that error 39 is not related to plug ins, or special
way of using DP 7.22
I just discorver that any file (dp file of course) that 7.22
won't open by indicating error -39

YOU JUST NEED TO AD TO THE END OF NAME OF THE FILE .AUTOSAVE
and it will open
the same file that won't open >>>>now do!

ex.: P-Lessons in love.mid (7.22 give a error -39)
same file with ad: P-Lessons in love.mid.autosave (now 7.22 will open it)

and with that now the logo DP stamp will appear
with the new name of the file instead of MIDI

Weird! YES -but work.

Your solution works, but you're making the situation much more complicated than it needs to be. Simply don't append .mid to the end of the name of a Performer or Digital Performer document. That will cause recent versions of Digital Performer to treat it like a standard MIDI file, which it most certainly is not. Appending .autosave to the end of the file name makes recent versions of Digital Performer treat the file like an authentic Digital Performer document again: Recent versions can save a copy of the currently open document as a safety feature, and they append .autosave to the end of the copy's name. Adding .autosave to the end of your files' names produces a favorable result, but you're ignoring the origin of the problem.

[James Steele]

Yeah, really seems like user error here. File extensions are becoming increasingly important and .MID means it's a standard MIDI file, hence you're confusing DP. You could remove the extension or change it to ".perf" also.