Sorry about your lost work. I understand the pain and frustration. I work a lot with alpha and beta software, where the app crashes and documents get corrupted (sound familiar?) and I have learned that it's safest to get in the habit of duplicating documents often.
So here's a tip. My technique for doing the duplication quickly and easily. In Finder, leave the folder open which holds the document you're working on. Then go back to the application and work. From time to time, command-tab over to Finder, duplicate the document (command-D), and the command-tab back to the application. Don't even worry about naming the duplicate. It'll be something like "MyDocument copy 7". And you'll end up with a bunch of them. But when the crash or malfunction happens, go back to Finder and show the folder by date, so you can see which copy was the most recent, and you can restart from there.
Like any good backup strategy, this is quick and easy. That's the main thing. Make it part of your workflow. Command-tab, command-D, command-tab.
Another thing I've learned from working with beta software: if you've lost a bunch of work because of a crash or whatever, redo the work immediately. You'll catch up a lot faster. You can remember what you did, etc.
So keep sending carefully written bug reports to Apple, make a lot of backups, and keep working. It is possible to get work done with buggy software.
Thanks guys for the tips. Unfortunately though stuck, I don't know if the finder trick will work. Remember, I never really had the file LOST, the changes were simply not writing to the actual .fcp file. So if I copied it in Finder, I think it would just copy the .fcp file which is currently not getting saved to anyway. Maybe duplicating the project in FCPX would work, but again I think that just takes the .fcp file and duplicates it. If it's not writing to it, then its a moot point. Oh well.
As with anything that frustrates anyone, I've cooled off haha, and doing the re-edits actually seemed to turn out easier and better then second time (you know, as theu naturally are I suppose haha). Obviously all sorts of problems happen with technology, its just a shame that its a bug that revolves around the ONLY save feature haha.
HOWEVER. I think I have replicated the problem, and MIGHT know the source of it. Or at least one. If someone wants to try this and confirm this? I'm running OSX 10.7 and FCPX 10.0 (obviously), however I encourage someone with 10.6 to try it too.
I noticed the "undo bug" (and thus the auto-save bug) happens when I took one of the "fader handles" (I don't know the actual name, but its the little marker-like icon found at the start and end of audio tracks, which when dragged, let you easily make a fade in or out. If you take a fader-handle, an drag it ALL the way BEYOND the length of the clip, it should get stuck. Youll notice you cant easily make a change to it again, and you can't undo it. I think this is what causes the problem, as I think this happened twice to me.
If this is it, I hope I can find a way to flag this for Apple so it can get fixed! At the very least we can be concious of it.
I could not agree more Jon. Perhaps it's just something they cannot get a handle on to fix. It is so eratic. I've had it happen to me a couple of times, but I have no idea or no way of seeing what causing it, and whether it's something in the app, or something in some other app, or something in the OS. It's a little early to say, but I haven't had it happen to me in Lion, but then maybe I've just been lucky, or maybe something in the OS has changed that prevents this.
Just wanted to check on this thread again.
Tom, I read your comment. Like I said I might have discovered the cause of the bug, read my 2nd post towards the bottom, it happened to me regarding the fader handles and dragging them too far. Hope this helps prevent you from a future disaster
If it's that kind of error, more than likely it exists in several different places within the program. Basically you've performed an operation the program doesn't know how to deal with, it may be something that's caused a loop or it may just be an operation there's no undo for because it was unexpected.
Apple has a lot on their plate with the next update, I imagine they're taking their time and trying to release something a bit more robust. No professional program should crash if you perform an operation that's unexpected. It's still difficult to believe they would release a program that was unfinished. A slap in the face to a user base that has supported them royally. What was the rush?
I've been having this problem and quitting and restarting FCP X & the Machine did not help. I fixed this problem by deleting the preferences in the Library folder:
Select Go Menu -> Go To Folder
Press Go button
Open the preferences folder
In the search field type "final"
Make sure that you are searching in the preferences folder and not in the This Mac folder
Delete all FinalCut preferences
It's very important that you are only deleting the preference files found in the preferences folder.
preference files end with a .plist extension.
Preference files are re-created when you start FCP back up.
Spoke to soon. Still getting the greyed out Undo, and loosing changes when quitting FCPX.
This began happening to me after the 10.7.1 update.
Seems to happen if I resize a still and don't click on the done button.
However, deleting the preferences seems to help other odd problems happening in the interface. Deleting the preferences does reset your preferences to default settings.