DP11 end of file -39 Kills file and all autosaves!

[lightbodymusic]

Hello one and all! I've been on DP for some time and could REALLY use some help with my DP11 files just quitting with an error -39 message. Unfortunately killing all the autosaves and backups I have created. This is insane to me. How does one file take out all related files. I have submitted this to techsupport at MOTU and I'm not getting too much support yet. I'm holding on to hope there. This randomly occurs but without Crashes or crash reports so I'm unable to reproduce the issue leaving me with little direction. Believe me I've been on a Mac since 1987 and have survived many issues Mac and Performer since but this one is leaving me to recreate my work from scratch and a time and money waister!

Yes I have thoroughly tested all my drives and done due diligence. Including Load, deleting analysis files, audio etc. Not sure where the first bad file came from IF it's a bad file that created the issue. But this problem is destroying my current project to no end.

Any and all clues would be greatly appreciated!

richardmartinezcomposer.com
Mac mini 2018 VEP7 Keyboard Maestro Waves 13 Izotope Fabfilter Slate Digital Altiverb and countless other plug-ins and VI's
Using Teamviewer, Dropbox, Audiomovers.com, Zoom and my wits to help any and all digital slaves in need.

[HCMarkus]

Wow... kills separate backups, too? Are they on a separate drive?

Have you tried rebuilding your template? Perhaps there is something nasty residing in there...

[lightbodymusic]

Hey HCMarkus!

To answer your first question. YES it killed all the backups too! It seems it must have flipped DP into a state that when opening such file. BOOM!

BUT!

Thanks for seeing this plea and your reply. It's funny you should say rebuild the template. I did rebuild it BUT I rebuilt the core Main buss section from clipping files.

And just today at about 5pm I noticed in the Effects Performance window that there was a rogue plug-in using resources. By rogue I meant it wasn't in the buss inserts visibly. All the inserts in that Master Buss were empty. But alas the Effects Performance said it was there and using resources.

I'm madly going through all of my files now and deleting that buss and it's rogue plug-in where it is in hopes that I have found the ticking bomb!

And when I say ticking bomb I mean the files open and could at any moment explode. I guess this will take a while to surmise since I have many files to open and hope they open so that I can investigate that buss and repair it. If I'm right as you so wisely have reminded me it will take weeks of no exploding files to be sure it was the cause.

AND SO ANOTHER CORRUPTED BUSS. I DO RECALL IN THE PAST BUSSES CRASHING MY INTERFACE. I did have a suspicion it might be a plug-in issue and over the past weeks I've been disabling plug-ins in swathes hoping the DAW would stabilize. WE SHAL SEE!

Let's HOPE! BUSY BUSY BUSY
THANKS AGAIN and I'll report back as I become more sure...

[HCMarkus]

Hope you have found it... fingers crossed!

[philbrown]

That's terrible. I would report to MOTU ASAP as maybe they have some ideas to help, and at least need to know. Best of luck!

[mikehalloran]

Any error with a minus sign is MacOS. In this case, DP is trying to write but can’t. This was common when people had loaded files from a CD or drive where you didn’t have full permissions—of course DP couldn’t write back to it.

Are your work files on your system drive or another volume?

[lightbodymusic]

Hi Phil,

Thanks for your well wishes. I have a tech support ticket with MOTU and I'm holding for their reply.

Thanks Mike,

Your friendly face is well received. As has always been, my work files are on external drives. I have never had a permissions issue with any of my external drives that I can remember but I will look into this. I have run disk utility on all my drives including the master disk from recovery mode. All is clear so far. Do you know of another utility which might give me a better understanding of the permission state my drives are in than Mac Disk Utility?

As I mentioned to HCMarkus I found a bad buss with a plug-in from PSP consuming CPU performance. It turns out that plug-in is not visible in the busses insert E where it seems to be, according to the Effects Performance window. Deleting and reinstating the buss is something I'm trying to troubleshoot now. No proof as to yet. Although I've preserved this bad buss for MOTU to research when they get back to me.

But what you said about the MacOs trying to write is something I will keep in my method of troubleshooting. In the many times this issue has occurred, I think that using "Save As" or "Save a Copy As" has been a symptom to creating fragile sequence files that eventually fail. Yet to prove this theory either. I have been starting new templates from scratch rebuilding my work in hopes that they are in a more safe state. But some of these templates have also failed after time. This could also be related to your permissions comment. If Disk Utility passes the drive is that the truth? If only I could get a crash instead and have a Crash Report to investigate.

Also, this is a far fetched theory but could my master drive which is encrypted have some thing to do with disk access or possibly something to do with DP11 and it's functionality. Unfortunately I have read some things about Apple's T2 security chip being a sinister gate keeper with my data. Have you heard of anyone with a similar symptom that could offer support to this farfetched theory?

I apologize for my long winded reply. As you can see this problem is eating my brain alive.

Thanks all, your support is keeping my hopes up!

[daniel.sneed]

Sure this is of little value, but, shooting in the dark:
have you tried to copy the project folder on your startup drive, then try to launch from that new copy?

[mikehalloran]

As has always been, my work files are on external drives…

Your problem will be related to this. It doesn't have to be permissions but not knowing anything about your externals, I don't want to write a few paragraphs speculating further. If your drives are connected via USB, shut down, burnish all connections by unplugging and re-plugging three times, then reboot—see if you still have a problem. As in the example I gave earlier, it could be hardware.

If you suspect a port issue, reset the SMC. Shut down. Unplug the power cable and wait 15 seconds. Plug it back in. Wait 5 seconds and reboot.

Unfortunately I have read some things about Apple's T2 security chip being a sinister gate keeper with my data. Have you heard of anyone with a similar symptom that could offer support to this farfetched theory?

You can safely ignore all of the armchair expert nonsense you have read on MacRumors about the supposed problems with the T2. Crash reports that mention it are always the symptom, never the problem. I've been in the trenches with Apple on this issue including last Friday when I was told to rebuild the firmware on my T2 after another team so thoroughly hosed my system that it was my only choice. Doing so wiped everything requiring a complete restore from Time Machine that took 40 hours. I finally got my iMac Pro back online a couple hours ago — with the problem intact. When I have my projects for next Sunday done, I will see if I can get Apple to properly diagnose what happened when I installed Monterey 12.2. I'm mostly functional including DP but … I'll give details once I know wtf happened.

[efernan]

Hello one and all! I've been on DP for some time and could REALLY use some help with my DP11 files just quitting with an error -39 message. Unfortunately killing all the autosaves and backups I have created. This is insane to me. How does one file take out all related files. I have submitted this to techsupport at MOTU and I'm not getting too much support yet. I'm holding on to hope there.

Hi, it's happening here too (again!). Did you find a solution or have any definitive answer from MOTU? I already contacted them but only got a vague generic response.

Any help really welcome! Thanks!

[waterstrum]

I haven't experienced this for 12 years, but here is my past entry about it.

Re: DP7.24 MacOS error: Unexpected end of file (-39)
Edit Report Quote
Post by waterstrum » 15 Apr 2013 12:26 am

I've been through this a couple of times.
Contacted MOTU and sent them the files.
They were unable to open the project or get it to work.
Pointed to data corruption somewhere, but said the cause was unknown.

Only twice over a period of many years, but of course it happened at critically bad moments.
Now I'm saving every session on three drives and the cloud.
I've got my fingers crossed.


Why would this odd thing be coming up again?

[mikehalloran]

-39 is no more a DP problem than it is a Finale problem or Microsoft problem — or any of a hundred other apps where it can occur.

It is a MacOS error stating that the app cannot write to a directory or file. Either the directory does not exist, a path is corrupted, permissions errors, a drive cannot be written to — plenty of causes.

If your files are on a remote drive, do you see the drive on your desktop? Did you load your files from a CD without saving them to a writable drive (we used to see that a lot)? Are you storing your files in Dropbox? Do you have a failing hard drive? Is your SSD too full?

[mikehalloran]

I haven't experienced this for 12 years, but here is my past entry about it.

Re: DP7.24 MacOS error: Unexpected end of file (-39)
Edit Report Quote
Post by waterstrum » 15 Apr 2013 12:26 am

I've been through this a couple of times.
Contacted MOTU and sent them the files.
They were unable to open the project or get it to work.
Pointed to data corruption somewhere, but said the cause was unknown.

Only twice over a period of many years, but of course it happened at critically bad moments.
Now I'm saving every session on three drives and the cloud.
I've got my fingers crossed.


Why would this odd thing be coming up again?

Yea, MOTU support had a lot of problems with 7.24 files back then. I was told my files were corrupt when it was a permissions issue. I figured it out.

Anyway, there is no way for MOTU or anyone to diagnose -39 without having direct access to your Mac unless your description of the problem is so thorough that someone can see the problem — like you loaded audio files directly from a CD.