Final Cut Pro X saves projects unreliable

Loathe as I am to debate things, I do know the bug in question. If you look at the thread you'll see I had the same problem - posted about 2 comments down on the first page. Like I said, since I upgraded to 10.0.3, those problems went away and I found it stable enough to use professionally (on Mountain Lion) - as have a large number of professionals I have dealt with.

I'll state again, if you are having problems with autosave, the duplicate project fuction forces a save.

If you're still not happy, there are other apps out there.

As for how Apple decides to gather feedback, I would suggest their time is more constructively used receiving it from individual users experiencing a problem directly in the app rather than wading through many hours worth of vague complaints and one upmanship contests.

bobbydee wrote:

... since I upgraded to 10.0.3, those problems went away and I found it stable enough to use professionally

I can confirm this.

I hope so.

Was using 10.0 yesterdat and just like some guys told here I lose part of my work.

Not much, but I feel the kick 🙂 , start searching and came here.

Mostly work I lose was titles, thanks god most of cuts are ok.

I'm now updating to 10.0.6 hoping better luck.

My Final Cut Pro X 10.0.7 just crashed on a new MacBook (OS 10.8.2), and I realised that 2-3 hours of intense work disappeared, restarting with backups. FCPX is not doing 15 min backups, and I also experienced UNDO command not working.

So is this still an issue with 10.0.7?

Do some of us need an external backup program lik Chronosync to be sure?

Or do some go out and in of the program regulary to be sure?

This is disturbing when deadlines is approaching..

Any suggestions?

FCPx saves every time you do anything. And it will do so UNLESS you run into the infamous "Undo" BUG.

What the undo but does, is to quit "recording" any of your steps. If you make quite a few and dont know that undo has stopped working (becuase you did not need to undo) and then quit FCPx... FCPx when relaunched will open the project at exactly the state where undo stopped working.

Quite a dangerous bug indeed.

Here is a workaround and steps to consider... At least I CONSIDER thoese steps every time b4 quitting

1) Click the edit Menu, If undo and redo are both grayed out proceed to step two

2) Duplicate your current project (if you have been working on several duplicate those too) (Use Project Only Option)

This will ensure that hours of work have not gone lost.

I have reported this bug back in 10.0.4 but it has yet to be fixed. So perhaps if all those 16,000 reading this thread would use the feedback option in FCPx.... Such NASTY bugs would be fixed much faster.

Some folks have the tought luck of running into this bug - some dont. But is IS there !

This issue reappears after 10.0.8 update. What the **** f$%&$ing apple????

not after 10.0.8 certainly. I want to cry

I noticed that is not a bug on fcpx, Mountain Lion is. If you reassign disk permissions (folder by folder) the problem solves in some cases, or some projects. I work in two ecosystems, snow leopard and mountain lion. The problem backs when I move or editing projects between 2 systems. BIG FAIL APPLE YOU ****!

I was just going to reply to your preceding post that it works as expected for me. But seeing your third post, I am also not running ML.

Why not post this in FCP Feedback?

Russ

For the record, I experienced this same problem today... 05/22/13

FCP 10.0.8

OSX 10.8.3

After hours of work, I rendered the project to my desktop to watch later and critique more closely, planning on going back for additional refinement. After the project rendered, I watched it once, then I shut down the computer to rest, only to start it back up a couple hours later to find that nothing was saved! I'm furious to say the least.

I have no idea if it was the "Undo" bug. I didn't drop down the "edit" bar to see if the undo was greyed out or not before I closed FCP.