Final Cut Pro X saves projects unreliable

This issue was reported to Apple using the Feedback feature quite some time back. I worked with Apple engineering on this and various other issues. In the latest version, the problems appear to be corrected. I have not experienced the mentioned bug since the upgrade.

Apple DOES watch the Feedback/Bug Reports. They do contact customers who file in order to track down various issues. But if you do not file a bug report, they cannot track nor work on issues.

Although I appreciate your input, it doesn't stand.

I was one of the early adopters of FCPX. Soon it was clear that I'd bought a beta version of a piece of software, clearly not ready for any market. So far, so good...

I've filed my bug reports, issued my complaints, filed a bug. Did what was suggested. Held my temper. "It is still a piece of **** software". I've tried the 'create a new account' thing. I've tried the ridiculous 'do a fresh install' monster. It is still a piece of **** software.

So, if it's true that Apple developers are reading these Fora, it's about time they admit that there is something seriously wrong with this particular product.

I've stopped caring about the fantastic algorytms, the state of the art timeline editing. When 6 hours of work disapear in the Black Hole that is FCPX, I consider my +200$ as gone.

FIX.... IT....

They're not reading the fora, they're accepting feedback from within the app. I sent a comment about FCPX losing autosave when color correcting and they got back to me within hours asking me to explain my workings.

I disagree that FCPX is "a piece of ****software". If it was, I wouldn't have been using it professionally since version 10.0.3 without hiccups. Admittedly before that version it was too unreliable (as was FCP in it's previous incarnation).

There are still issues and lots of room for improvement but Apple have committed to a ten year plan for the software and I loathe going back to 7 now. It's relatively new software - it was built from scratch - so of course there are going to be work arounds. A lot of what I thought was missing from the program at the start, though, was just down to me trying to apply an old mindset to a new paradigm. I'd say I've had 1000+ hours of use of it now and I'm still learning.

As for saving, duplicating your project at regular intervals does exactly the same thing (and you don't have to duplicate media). I do it when I reach different stages of my edit and store them in a backup folder within the app.

That's not the point. You do not seem to be experimenting the bug in question. Of course it's still a new program and will get better with time but before doing all kinds of cool things it should be able to reliably perform the most basic and crutial task : SAVING YOUR WORK.

As to Apple not monitoring the Apple Support boards and only paying attention to feedback sent from within the app, that just shows poor judgment on their part. They are releasing a new program. They should be paying attention to what people are saying and to the serious issues people are encountering using it. This is supposed to be a professional program. People's jobs are depending on it.... Hours of editing lost is more money than the softwear itself.... These boards are hosted directly on the apple site, it would make sense for them to have a few moderators monitoring issues and offering advice. We are at 10.0.5 now.... not being able to save my work reliably should have been fixed a long time ago.

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.

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 !

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 ****!

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.

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

I have not experienced this issue either, but many here have. We are all anxious to see what Apple support determines to be the problem here. Please keep us informed. Good luck.

No I have lost things many a time

I don't think it has anything to do with older hardware as I'm experiencing it on a brand spanking new iMac quad-core i7.