Final Cut Pro X saves projects unreliable

DJ Duke wrote:

I agree. I have not lost a single thing and I only crashed one time because I tried to open an incompatible plug in. Maybe because they use older laptops.

If you -read- the posts on this several other forums you would realize it's happening across the board to both old and brand new machines... and, is a serious problem. Whether it's happening to you or not is irrelevant, these folks are asking for help.

one thing to try is to see if any error messages are being reported in the system log files.

In the Applications/Utilities folder, open the "Console" application. This lets you see all the log files that are "behind the scenes" for your computer.

At the top of the left-hand panel, select "All Messages" and then type "final" into the search box in the upper-right hand corner. That should filter the messages to include anything related to final cut pro. Maybe there's some info in there that might help.

Since this isn't happening for me, I can't really see if there will be or will not be helpful information, but maybe someone else can give it a try, especially right after they have the undo button become inactive.

I think I've worked this out. The history goes grey and it fails to autosave if I go into the transform tool and don't click the 'done' button after making my onscreen changes - the system probably disables the autosave briefly so that the transformation is seen as a single step. Problem is its too easy to forget. To stop myself from doing this, I've been dragging the numerical values rather than go into the transform tool as its too easy to click on something else rather than the 'done' button. Since this, haven't had a problem.

Just a thought -- could this be happening under Snow Leopard (which does not have autosave built in) and not under Lion (which doers have autosave built in)? I'm training myself on FCP X on a separate workstation which now runs Lion and it hasn't so far exhibited save problems.

Rod

All I make is 4 minute tuitional music videos. Imagine trying to use fcpx to produce a feature film such as harry-potter.

Just finished recording a track in Logic.

All I want to do is import the audio into fcpx.

I import, all ok, but when I re-open fcpx, the file is not in the event even though it was copied to the event folder in the finder.

Un-usable and a complete joke.

I'll be finishing off this project in fce7.

I've just bought FCPX but (fortunately in this case!) not yet used it. I found this thread when searching for information regarding a similar problem I (and others) are having with Pages under Lion (https://discussions.apple.com/thread/3226457). It seems to me it's a bigger problem within Lion.

It's not related to Lion! Users experience this on Snow Leopard as well.

Hello

This odd behavior was also reported with iWork and TextEdit.

Look at : https://discussions.apple.com/thread/3226457?answerId=15816836022#15816836022

May you try to run Final Cut from an other user account ?

Doing this test will tell us if the wrongdoer is in your current account or if it is in the set of files shared by every account.

Doing a "safe boot" would be useful too.

It would tell us if the problem strikes when the system doesn't use third party extensions.

Yvan KOENIG (VALLAURIS, France) mardi 2 août 2011 11:02:51

iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.0

My iDisk is : <http://public.me.com/koenigyvan>

Please : Search for questions similar to your own before submitting them to the community

To be the AW6 successor, iWork MUST integrate a TRUE DB, not a list organizer !

I think i figured this out. I was having the same problem on a brand new iMac with Lion and 16GB of RAM. I noticed an odd hesitation in FCP after large project changes and the "Undo" function would stop working. After that, FCP would stop Auto Saving too. As a recent convert to Mac OS X, i suspected something was interfering with the file system or memory. Sure enough, I add exclusions to my real time AV solution for all of the FCP directories (program, project files, and source) and AutoSave began to work correctly again as advertised. I can only guess that like in the PC world, the AV solution was locking all the "touched" files and preventing FCP from a proper AutoSave. Once it failed, it was dead from there on out. If any users are running real time AV, or even time machine on a FCP project directory, you may want to check this out and confirm with proper exclusions. Since i did this, no more problems with AutoSave. Can anyone else confirm if it works for them ?

Same thing happened to me. I lost 2-3 hours of work with this problem and are you guys sure there is absolutely sure there is no fix? 😕

So far I have had no luck finding my lost file.

Good luck to the rest of you.

McShamus wrote:

It's not related to Lion! Users experience this on Snow Leopard as well.

Looking at all the posts relating to Auto-Save not working and the non-functional UNDO entry in the menu points to FCPX running into an "action" or combination of actions it doesn't understand, whether that causes an internal error loop (can't undo a loop) or some other internal error is still a bit of a mystery as it's happening under several different scenarios.

Does anyone notice the program slowing down after the Undo function becomes unavailable?

I suffered badly from Autosave not working but for me, Undo was still working, so I had no idea when Autosave wasn't working.

I was running FCP X on my Lion OS and eventually did a CLEAN REINSTALL.

(By this, I mean erase and reinstall the system, then manually reinstall any applications I wanted. To erase then reinstall and then import settings and applications etc from a backup is likely to bring back whatever was causing the conflict in the first place).

FCP X has worked perfectly ever since.

I have not installed FCP Studio 3 - and I don't intend to, unless I really need it.

Andy

andynick wrote:

I suffered badly from Autosave not working but for me, Undo was still working, so I had no idea when Autosave wasn't working.

I was running FCP X on my Lion OS and eventually did a CLEAN REINSTALL.

(By this, I mean erase and reinstall the system, then manually reinstall any applications I wanted. To erase then reinstall and then import settings and applications etc from a backup is likely to bring back whatever was causing the conflict in the first place).

FCP X has worked perfectly ever since.

I have not installed FCP Studio 3 - and I don't intend to, unless I really need it.

Andy

Hey... it's just like PC's used to be! 😉

Pancenter wrote: Hey... it's just like PC's used to be! 😉

Not so.

Search the FCP forum archives - there are dozens of posts by experts (such as Jerry Hoffman) recommending a clean reinstall.

Andy