Mohave Update necessitates DP file repair, save copy as

[toodamnhip]

I updated to Mohave from Sierra today. I got the following strange error message when editing soundbites and other things inside my prior DP session:
"OS error reported by File I/O: File can't be deleted because it is in use (-47). Additional information: Users/.........."
Also, my mixing board would not show the proper files. Seemed to be stuck on an earlier chunk's available files. Then, I lost 1/2 hr work because it turned out DP was NOT saving. The File menu would light up like normal when hitting save so I thought I was saving, but DP was not saving. Once I quit and started again, all new work was lost.

The solution was to do a "save a copy as"..which seems to have fixed things, but I haven't done hard work yet so I will post again of something else comes up.
This file is a file that was originally a Dp 8.07 file. But it had been "saved as" in DP 10.11 before, so I actually consider it a DP 10.11 file. A DP 10.11 fieldworker from BEFORE Mohave.
So my question is, has anyone had issues with files made BEFORE Mohave? I am now wondering if I will need to do a save a copy as or create new DP files and import all older work into them? We shall see. Anyone have any similar experiences let me know.

[MIDI Life Crisis]

Jumped from Sierra to Mojave (incrementally with High Sierra first) and not a problem except for a scrolling issue.

I still worry about the number of that plugs that load in your system at startup.

[toodamnhip]

Jumped from Sierra to Mojave (incrementally with High Sierra first) and not a problem except for a scrolling issue.

I still worry about the number of that plugs that load in your system at startup.

So then you’re an advocate of having “plug in sets“, and only using the ones you need? The problem is, like I said before, the file that got slow was working for quite a while large. So I think there are various factors going on. Hard to say. It’s a lot of trial and error to try plug in sets
And really get to understand how they really effect things. I don’t have a technical assistant at this time do I often have them. Next time I have one, that will for sure be something to focus on

[bayswater]

My newest Mac Mini that I use now with DP came with Mojave installed. Previously everything was on a High Sierra iMac. I have not seen this happen with projects that were originally created on the iMac. There was not copying involved -- I just connected the external project drive to the Mini. If I understand your situation, you didn't copy the files either, just upgraded OS X?

One difference might be that I never ran earlier versions of DP on my Mini. I installed DP 10 on when it was new out of the box. DP 10 worked fine, so I never installed DP 9 on the Mini, or started any new projects back on the iMac.

[MIDI Life Crisis]

So then you’re an advocate of having “plug in sets“, and only using the ones you need?

Absolutely!

[HCMarkus]

I was already on Mojave when I updated to DP10.11, but have found that LOADING old projects into a blank DP10.11 session allows me to run very smoothly, much better than when I try to open a DP9.52 project directly into DP10.11.

Maybe this isn't on point here; offering on the off-chance it might be pertinent.

[toodamnhip]

I was already on Mojave when I updated to DP10.11, but have found that LOADING old projects into a blank DP10.11 session allows me to run very smoothly, much better than when I try to open a DP9.52 project directly into DP10.11.

Maybe this isn't on point here; offering on the off-chance it might be pertinent.

It is on point. I think that’s something we all need to be ready to do, open in a clean file when necessary and import. I mean, look at the sneaky problem I had, DP pretending to save but not really
Saving lol. Crazy man.