What’s with “Operation not allowed” when saving or exporting

[Peter Corbett]

Thanks Dave. I haven’t got Disk Warrior. Will get it for sure. Thanks again. Have a great Christmas! Boy am I looking forward to slowing down for a few days.

Peter Corbett
Powerhouse Productions
http://www.php.com.au

[Dylan Murphy]

Just experienced this “op not allowed” error out of the blue.

Was able to get out of it and recreate it.

Luckily, I didn’t have any work I feared losing, so I quit FCP and re-launched.

In a new session, I was able to make changes and re-save them without issue. So, in my case, it had nothing to do with prefs or permissions.

I retraced my steps and performed the same actions that led to the error message – hitting save successfully after each one – UNTIL (dramatic music…)

I shift-deleted a nested sequence.

This gets me the save error message every time.

go figya

[Richard Chenoweth]

I was getting this message “Operation Not Allowed” when trying to insert footage into the Timeline.

I tried a few basic things like quitting and restarting. Then I noticed I had been trying to insert
footage that had sound into the Timeline with one audio channel on and one audio channel off.
Since I am using a soundtrack, I didn’t need any audio channels on. So turned them both off.

I realize you are “exporting”, not doing a mid-stream operation like “insert”, but maybe this thread can help others…

Richard

[Jason Lyons]

Just to chime in- Today out of nowhere I started experiencing this same error while trying to save all. The make new project and copy and paste all contents did the trick.

2x3Ghz Quad-core
16GB RAM
10.6.2
FCP 7.0.1

Repairing permissions did not help.

[Zach Perkins]

Hey Peter!

You are not crazy! (I know this is a couple months old by now, but….)

I as well am having that problem, and since all these peeps are shouting “noob” at you, I wanted to let you know that its not the noobism thats causing all this, cause I am not new to FCP, been using it professionally for 6 years, and I just ran into this problem

Every time I save, to any drive, regardless of permissions, or file overwrites, even when I try to save to Desktop, change the name all that…. I get “Operation Not Allowed” from FCP 7, same when it tries to Autosave….

For me the problem arose when I chose to pause my After Effects render and do some editing in FCP, after that things went whacky. I figure for my problem a reboot will fix it, but I was afraid of losing all the work I did!

Long story short, you are not crazy and your temporary solution worked wonders, thanks!! Keep working, and don’t listen to this “need more practice” bull crap, cause the best practice you can get is this real world experience, and that comes through the online edit.

words…

zap

[Andrea Stewart]

I second Zach’s opinions. While I great respect for a number of you other guys. This is not something that happens just to newbies.

And Peter, yes, it is something Apple should address. I thought they had since I hadn’t had this happen since version 5. Today it hit me on a brand spankin new MacPro 8 core running Snow Leopard and FCP 7.0.1.

As Shane suggested, we did a permissions rebuild. Thankfully autosave at 5 minute intervals had a usable version for us. (We tried the create a new project, move everything, etc method, but FCP crashed on creating a new project command.)

-Andrea

Andrea Stewart
Producer/Editor/Director – Owner
Germane Creative LLC

[Damien Kincannon]

I’ve been assisting on a two-week edit and my editor has been plagued by this problem. Now granted, we are not working with the best set-up. Our house has been growing faster than we can build it and he is using two partitions on Terrablock, an external G-Drive (via Firewire 800) and an external. 3 TB JBOD array. I know; not the ideal. However, others with cleaner, more consolidated work-flows are having the same issue, so although our set-up may not be helping the problem, it’s not at the root of the issue.
But we are having the same errors. First the Autosave cuts off and then FCP won’t let you save at all. Not even under a different project name/location. We’ve lost hours of work. Copying and pasting everything over to a new project is the only (and unfortunately poor) workaround we can come up with. After scanning the forums, we are clearly not the only ones having this issue with FCP 7 and Snow Leopard. It’s not the permissions (all set to read/write). Deleting the preferences is not an option since you have to quit FCP to do it. Saving XML’s comes up with the same error message (Operation Not Allowed), so they’re no good.

[Dawn Mikkelson]

I agree with Damien. I’ve been using FCP for over 10 years and had the scenario that he just described on my MacPro. Since the project is on an external drive, I’m not using a different computer (interestingly a MacBookPro) and that seems to have helped for the time being. Thinking I might reinstall Final Cut Studio entirely and see if that makes a difference. This is not a “noob” problem, this is a larger software problem methinks.

Dawn

[Paul Sulsky]

Thank you for your work around. I just ran into the “Operation not Allowed” problem and your solution really came through.

[Carl Macneal]

Well Peter I am a cross Avid and FCP guy who is well versed in both and also had your horror. It isn’t FCP at all, it is the Mac OS and 8 core machine. They have a permission problem. I am repairing permissions once a week now. I have never had to do that before and have been on Mac since the quadra. Keep the faith, with state of the art comes state of distress.