OSStatus error -50 when trying to load Patches - Access Issues

[velanche]

Greets:
I have a User Patches folder in Logic's Library, where I have copy and pasted select patches from a third-party sampleware library. It has worked well for me, in the past. They were created before I moved to Apple silicon.

When I did move over, because  had a few choice ones as part of my beatmaking template, I was left unaware. Because when I went into the User Patches folder and I clicked on one of the patches, I get an error

"The operation could not be completed. OsStatus error: -50."

This is for every patch that I have copied. Again, this was not the case when I set it up on Logic on Intel.

Google....is of little use. I am hoping that some of you Logic users might be familiar with the error and can direct me to a course of action.

I do have plenty of SSD space, 2TB out of 4TB available. 

Thanks, folks.

 

[oscwilde]

This site covers OS Status errors:
https://www.osstatus.com/

Error 50 indicates a file corruption or permissions etc. issue on an external drive.

Edit: see David's post below....

[David Nahmani]

Here's a list of topics related to OSStatus Error -50:

https://www.logicprohelp.com/tags/osstatus error -50/

[velanche]

Sometimes, these errors make me feel like I'm alone on an island.

then you guys come in and, somehow,I feel a little less lost.

Thanks, gents; I'll look them up and hope that my solution will not take a long time to solve. 

[David Nahmani]

Just to try the obvious, is your disk formatted for MacOS Extended or APFS? 

[velanche]

No question is too obvious, @David Nahmani

APFS, it is. 

[oscwilde]

And also check permissions....for the files in question/or the folder they're in.

[velanche]

@oscwildeYes, permissions is kinda what I think it may be, as I have not come across a single patch so far in that library that did not provoke the error. Also, they are all on the internal SSD. I’ll have a look, later this evening. 

[velanche]

@oscwildeI had a few minutes while waiting to check those permissions. Things look fine as I traversed through the Patches folder. When I got to the patch level, it's changed from "Read and Write' to "You have custom access," with permission for my user account is set to "Read and Write." Not sure if that's a clue, but it's something to deal with later. Might have to check with Terminal to see said "custom access" settings.

And also look up the info that David shared, too. 

[velanche]

I looked up one of the threads that was part of the search results that @David Nahmani shared. Turns out, the problem is worse than I thought. And to think that I've been able to use Logic for months without discovering that not only are my select third-party libraries are affected by the error, but so are the factory-installed ones.

That....is a buzzkill. Really.

At least now I'll know what to do. As for the third party libraries, oy that tool time to put together, and now it needs to be redone. I believe I have the downloads.

Thanks again, folks; onwards. 

[David Nahmani]

5 hours ago, velanche said:

now I'll know what to do.

So what is the solution you're undertaking? 

[velanche]

An update.

The reinstall of Logic's factory Sound Library cleared up the issue. 

And, as cherry on top, I did not need to do anything to my Uber Patches that were there previously, as somehow, without any intervention, they are now working properly again too. As I make substantial use of those, it's a huge relief that I did not had to reinstall those.

So, there you have it: done, and done. 

Thanks to everyone who chimed in. 

 

[David Nahmani]

11 hours ago, velanche said:

The reinstall of Logic's factory Sound Library cleared up the issue. 

Great! Thanks a lot for letting us know what resolved this for you, I'm sure this'll help others with the same error in the future.