MOTUnation.com

Not good enough. This only grants access to the drive; it doesn't grant new Permissions to write to the files if you didn't already have them:
You need to grant Permissions to the enclosed files and folders. Unlock with your Admin password, highlight the User, then click on Apply... You'll get a confirmation pop-up. Click OK.

I first discovered this when my 2010 iMac couldn't read my files in DP 7.24 — but DP 7.1 read them just fine. Running the Activity Monitor in DP 7.21 gave me the clue. MOTU told me that my files were corrupted though 7.1 could read them just fine as did DP 5 on my G4.


Since Sonoma, you may have to do this at the Folder level — as I found out after accidentally updating to Sequoia and nothing worked including Mail, Time Machine and backing up my iPhone. Every problem I had turned out to be Permissions and reverting to Sonoma (yea, you're not supposed to be able to but I figured it out) did not fix this.

I spent a few weeks going round and round with Apple Support & Engineering before I figured it out. The error messages were just whack. While trying to back up my new iPhone, the error was that my phone couldn't be read to—Apple Engineering took a few attempts before giving up. I then wondered, what if the message is backward and it's really the Mac? Bingo! I was then able to go into Library and Users/Username/Library and start granting permissions — slowly, everything came back to life. I then showed Support and Engineering what I did and how while complaining why wasn't I being paid... Someone agreed with me and I received payment for my troubles.

Gents, don't you think that if this was a Permissions issue, I wouldn't be able to Save a new document, or Save As a new version of an existing document?

I can do both.

As I've mentioned, I can save over existing files using BMD DaVinci Resolve and Adobe Ae, Ps, Ai, etc.

I'll double-check my Permissions next time I fire up the NAS. I've relegated it to a backup device for DP. I use it primarily for editing with Resolve now with no issues. Resolve writes many files: Projects, Project Backups, audio and video caches, renders, and a database for tens of thousands of AV media files. And natch, exporting / rendering movie files.

Jim wrote: ↑Wed Feb 05, 2025 2:25 pm Gents, don't you think that if this was a Permissions issue, I wouldn't be able to Save a new document, or Save As a new version of an existing document?

I can do both.

As I've mentioned, I can save over existing files using BMD DaVinci Resolve and Adobe Ae, Ps, Ai, etc.

I'll double-check my Permissions next time I fire up the NAS. I've relegated it to a backup device for DP. I use it primarily for editing with Resolve now with no issues. Resolve writes many files: Projects, Project Backups, audio and video caches, renders, and a database for tens of thousands of AV media files. And natch, exporting / rendering movie files.

I just had a crashing on startup issue with DP related to an alias I put in the Clippings folder. The manual flatly says you can stick an alias in the clippings folder to get access in DP etc. but apparently that's broken and it crashes DP. Because it was in the manual it took some other person googling that clippings could crash DP on startup via the crash report I showed him. Relying on my own not unjustifiable logic would have had me locked out of DP for another day likely before I remembered I made an alias and that might be an issue.

I see clearly two different levels of permissions on the same drive depending on whether it's mounted via ethernet or TB, you can't write to the file on ethernet in DP, it's a trivial thing to check and see, to follow Mikes advice, and it's good housekeeping, but it's trivializing the free support you're getting to write off the suggestion as not possible or erroneous.

I don't think it's as relevant as you think it is that other applications can do this, it's dependent on how MOTU saves files VS others, what permissions setting each app has etc. and right now you're having issues saving files.

Gents, don't you think that if this was a Permissions issue, I wouldn't be able to Save a new document, or Save As a new version of an existing document?

Nope. You have access to the drive but that does not automatically grant Write privileges to all the files on the drive.

I don't think it's as relevant as you think it is that other applications can do this, it's dependent on how MOTU saves files VS others, what permissions setting each app has etc. and right now you're having issues saving files.

That.

Michael Canavan wrote: ↑Wed Feb 05, 2025 3:11 pm
I see clearly two different levels of permissions on the same drive depending on whether it's mounted via ethernet or TB, you can't write to the file on ethernet in DP, it's a trivial thing to check and see, to follow Mikes advice, and it's good housekeeping, but it's trivializing the free support you're getting to write off the suggestion as not possible or erroneous.

I don't think it's as relevant as you think it is that other applications can do this, it's dependent on how MOTU saves files VS others, what permissions setting each app has etc. and right now you're having issues saving files.

I don't intend to trivialize anybody's suggestions. I'm just trying to apply logic.

To wit: If I can Save a new Project to a folder, and Save As to the same folder, it seems to me I have permissions to save to that folder, and should be able to Save over the same file I just saved.

I'm no tyro when it comes to troubleshooting computer issues. I've usually tried all elementary steps before I post here.

Again, no offense intended.

Likewise, others should consider the possibility they're barking up the wrong tree.

I'd written that I'll check the permissions the next time I use the NAS, which I fully intend to do. I will report back if that turns out to be the issue, and prostrate myself before the Grand Poobahs of DP. I don't think I've failed to thank anybody for actually helping, or even just offering to help.

Funny - just two days ago, I read on Reddit a guy who offered this site as a source, and the poster added, "But, they're sensitive over there."

I'm pretty sure I've set all my shared disks to "Ignore Ownership" (SOP), but I've seen stuff like that get changed mysteriously running certain routines.

THANK YOU

Jim wrote: ↑Wed Feb 05, 2025 8:00 pm Funny - just two days ago, I read on Reddit a guy who offered this site as a source, and the poster added, "But, they're sensitive over there."

Seriously, stop with the backhanded BS. Personally I just get tired of people who want to argue with you while you try to help them, it's a weird habit it seems some people on the internet get where they think random strangers owe them something, and at the same time don't admit in this one instance, they aren't experts, they need help, i.e. other opinions. If you think you're the expert here, fine, the pay sucks and the customers are arrogant, so yeah go at it bud.

Way to confirm the accusation the guy on Reddit made, Michael.

You seem to be ignoring that I can Save NEW, Save AS, but cannot Save OVER. I think this is valuable information. And again, it's LOGICAL to assume I have write privileges to a folder or volume to which I can Save and Save AS, and would rule out a permissions issue.

Despite that, with respect to Mike, I fired up my NAS, did the "Apply to enclosed items" AGAIN as he suggested to the whole volume, and the errors persist.

I attached the Get Info of my NAS, mounted by TB on the left, and Ethernet on the right. I cannot change the "everyone" Privilege from "No access." (It flips back to "No Access" when I try it.) "Ignore ownership" is not available on these two Get Info panels. That's handled by the NAS Administrator function.

See the other screen shot of the NAS Administration interface in which all users of the volume "Public" are granted RW access.

Again, I get the same errors sharing a DAS RAID over ethernet in which "Ignore ownership" is enabled by the Mac to which the RAID is attached by TB. That should rule out a permissions issue, as well.

Matt at MOTU TS acknowledged this issue may be due to "a lack of optimization" in the DP code, and added they plan to "address this in the future."

If my comments annoy anybody, please consider the option to ignore me. I've suffered some condescension in silence, and haven't disrespected anybody, which I don't think has been reciprocal. Disagreement isn't disrespect.

James Steele, feel free to delete this whole thread, if you think it's gotten out of hand. Since I've heard back from MOTU, I'm happy to await further input from them. I have found a satisfactory workaround anyway.

I'm just trying to apply logic

So what? Michael and I have experience.

You seem to be ignoring that I can Save NEW, Save AS, but cannot Save OVER. I think this is valuable information

It is but you don’t understand what it means. You have access to the disk but do not have Permission to write to those files. I’ve shown you how to fix this.

I have years of experience with this including MOTU Support telling me that my files were corrupt when they changed the Permission structure in DP 7.24—they were wrong and fixed the issue in DP 8, BTW.

I’m not the one with the problem and neither is Michael. You should really follow my instructions.

mikehalloran wrote: ↑Thu Feb 06, 2025 9:58 amYou should really follow my instructions.

I did, and they did not solve my issue. Read my posts again.

You two are not infallible, despite your years of experience. Nor am I. Try admitting that you're human, and please stop being condescending to people you view as your inferiors.

I probably have as much computer experience you do. Logic is relevant.