Page 1 of 1

NSCocoaErrorDomain error reported by cocoa driving us batty

Posted: Tue Jul 23, 2024 9:01 am
by labman
Need help for one of our team. Everytime they try to do a save on a regular old unlocked work in progress DP 11.32 file, they get the error below. I have seen them do this with my own eyeballs. The only workaround is to contiunuosly do 'save as'.

What does that error mean? Thanks!
Digital Performer error.png
Digital Performer error.png (214.06 KiB) Viewed 1964 times

Re: NSCocoaErrorDomain error reported by cocoa driving us batty

Posted: Tue Jul 23, 2024 11:08 am
by mikehalloran
Use Find Any File to find the location of the file with that name. Hold the Option key to search the root.

You can download it for evaluation from Thomas Templemann

https://findanyfile.app/

Although only $6 shareware from his site, I recommend purchasing from the App Store instead so that you receive automatic update notices when available.

This is what Finder/Find should have been since the beginning.

Re: NSCocoaErrorDomain error reported by cocoa driving us batty

Posted: Tue Jul 23, 2024 12:48 pm
by labman
mikehalloran wrote: Tue Jul 23, 2024 11:08 am Use Find Any File to find the location of the file with that name. Hold the Option key to search the root.

You can download it for evaluation from Thomas Templemann

https://findanyfile.app/

Although only $6 shareware from his site, I recommend purchasing from the App Store instead so that you receive automatic update notices when available.

This is what Finder/Find should have been since the beginning.

Thank you Mike. great idea. We use find any file all the time. Love it.

The odd thing is that the name the error is flagging is not name of each file that fails for him. Whihc is all of them. Its adding weird characteers in the error which dont exist in the shown file name.

Re: NSCocoaErrorDomain error reported by cocoa driving us batty

Posted: Tue Jul 23, 2024 3:21 pm
by mikehalloran
Yea, that's weird and above my pay grade. I'd still run FaF to see if anything like that exists.

Are those work files sitting on System drives? I suspect not.

Re: NSCocoaErrorDomain error reported by cocoa driving us batty

Posted: Wed Jul 24, 2024 5:04 am
by labman
They are on an external drive Mike. Should i have him move them to internal and test?

Re: NSCocoaErrorDomain error reported by cocoa driving us batty

Posted: Wed Jul 24, 2024 1:53 pm
by mikehalloran
labman wrote: Wed Jul 24, 2024 5:04 am They are on an external drive Mike. Should i have him move them to internal and test?
Oh yes.

Re: NSCocoaErrorDomain error reported by cocoa driving us batty

Posted: Thu Jul 25, 2024 4:53 am
by labman
wonderful. Really appreciate your help Mike!

Re: NSCocoaErrorDomain error reported by cocoa driving us batty

Posted: Sat Aug 10, 2024 11:22 am
by mikehalloran
labman wrote: Tue Jul 23, 2024 9:01 am Need help for one of our team. Everytime they try to do a save on a regular old unlocked work in progress DP 11.32 file, they get the error below. I have seen them do this with my own eyeballs. The only workaround is to contiunuosly do 'save as'.

What does that error mean? Thanks!
It happened to me yesterday. I think we found a bug.

A client sent me a number of tracks last night via WeTransfer for a session today. I created a Project and loaded them into DP, changing all the track names to match as I went along. When I went to Save. I saw the same thing. Yikes!

My first thought was that I had corrupt wav files (not my first rodeo on that issue) but, before I opened TwistedWave to convert them all, I tried the following: I closed the project and reopened—it was blank, of course. I added one track then Saved. I then changed the track name and Saved again. Next I added a few more Saving as I went along. No more issues nor when I added my bass track this morning.

A Cocoa message indicates a graphics engine error. Since I still have the original zip file, I will see if I can replicate this before I send it into MOTU via a Tech Link.