I'm really struggling with an issue . I have FCP X libraries that I backed up on a old computer with Time Machine. I am trying to use them on my new computer . When I attempt to load them I get an error that says
The document "Untitled" could not be opened. Permission denied
"Untitled" is already in use by MY-MBP on 'miles-macbook-pro.local".
I have tried everything I have read online...
1 - rebooted
2 - made sure permissions are set for red/write in all areas on the drive, on the folder, on the library and all related files
3 - I tried to copy the internals of the library into a new library, and that didn't work at all nothing showed up
4 - copy library from external drive to my computers own HD , same issue / error
I cannot find a solution for this anywhere ! It's so frustrating and I need to access these files .
I've seen this once before, copying Libraries from one RAID to another. I could not delete a specific Library off of the old RAID, it was fine on the new one. Turned out to be a corrupted folder that couldn't be trashed or anything. It was stuck on "being used". I did a web search of fixing a file flagged as "in use" when it wasn't. There are several things you can try, none worked for me. Over time, and a few re-boots, and the folder deleted fine.
Not that any of this solves your issue, but there's a flag on every file and folder locking it as "in use" in specific situations. You seem to have a Library that has a folder or file inside of it with this issue.
If you are not afraid of Terminal, or if you are willing to download a free little application that enables you to show Hidden Files on your Mac, there may be a way to fix this.
The reason why you cannot open the Library is probably because the .lock file, the .lock-dir folder and/or the lock-info file that are hidden inside the Library package are corrupted. The trick is to open the Library package (with FCP X closed of course) and to trash these files. This is harmless,because these files are automatically recreated when you open the Library in FCP X.
But of course first we need to be able to see these hidden files. There is a Terminal command that enables Show Hidden Files (and another one to disable this function), or you can download a free utility to easily enable/disable Hidden Files in the task bar. I will point you to the utility, if you prefer the Terminal commands let me know and I will post them here.
Download the app and drag it into your Applications folder.
Then double-click the app icon to open the app.
A little black button will appear at the right side of your top task bar. Click the button and set the switch to ON:
Now go to the problematic Library (which should NOT be on the Time Machine drive anymore) and open the package. You will see a lot of new files that you have never seen before. Never mind, these are the only ones you should care about:
Trash them, close the package and then try to open the Library in FCP X. This has worked for many others before, I hope you are in the camp of the lucky ones!
NOTE: after this procedure, switch the Funter button back to Hide Hidden Files and delete the app. Hidden Files must ALWAYS remain hidden except for troubleshooting. Messing around with hidden files is a recipe for disaster.
I wanted to update this thread I finally had a chance to work on this again and I figured it out !! The issue was, for some reasont he library from the Time Machin back-up was assigned strange permissions "Custom permissions" for files all scattered through the files . It was alot of work to do manually so I found.a program called BatCHMOD that was awesome, I ran it - and reset the permissions . The library loaded - finally!!
Thanks for your assistance. I wanted to leave this here for anyone else who might encounter this issue .
Ive got the same problem, I just tried downloading this app to but it didn't work, can you help?
This is what I'm getting....
“NEw Hardruve” is already in use by “harrybristow” on “harrys-imac-2.local”.
BatchMod is what did it for me. I had the same issue, after upgrading to a 2018 MBP, even though my FCPX library was on the same external drive, I was getting that issue on the new Mac. BatchMod really cleaned it up. Interestingly, I had to unmount and move my external drive (where the library and all my FCP files are) and plug it back in on a different dongle, and that did the trick, after at first running BatchMod but getting no success. I'm finding that these dongles are all very finicky. I just got this MBP about 4 days ago and already purchased 4 dongles in an effort to get sh*t to work right. Some have good USB but slow ethernet, others have good ethernet but HDMI won't work - what a f...... nightmare!
OK rant over, good luck ya'll!