Lost 3hrs of progress in FCPX upon restart

M

Mickey G

Active member
While working in FCPX (10.0.2) I noticed I could not "undo", needless to say this was a serious problem so my 1st thought was to quit and restart FCPX, well upon doing so I found my timeline not where it was when I quit. I have lost around 3hrs of work because of this.
WTH?!?! I thought there was no need to "save" in FCPX.

I've been working in FCPX quite a bit since day 1 and while I've been ripping my hair out due to many other issues this is the 1st time I've actually lost progress upon a restart. Now that I see this can actually happen, I question using this software going forward on any project. This is not acceptable to me. I've never lost any data/work progress in previous versions of FCP unless it was due to user error.
I really hope to find out what happened.

Has anyone else had this happen or know of a way to recover my lost work??


I'm trying to work in FCPX and really trying to love it but I feel like I'm spending more time fighting the software then actually getting any work done.

I also have lots of playback stutter when playing my timelines, I have to stop/play like 3 or 4 times before it plays back normally. Once the playhead hits a simple cross-dissolve, playback halts to a crawl. (Play-back is better with a rendered timeline but not perfect as is in FCP6/7)
Speaking of playback does anyone else have the curser remain on the screen during full screen playback? Every other piece of software I use the curser will fade away, just wondering if this is a bug in FCPX or just on my system.

BTW I'm on the latest version of Snow Leopard running on a Quad I7 iMac with 8GB RAM, (the iMac just before the T'Bolt iMac)
I am editing 1080 ProRes and h264 (not in the same timeline) over 7200rpm FW800 G-Tech drives.


Thanks for any insight into these issues
 
Its really strange, I presume the "undo" glitch and the lost data upon restart are related to one another. Its as if once I lost the ability to undo that FCPX just quit compiling data into its database tracking my progress or whatever the hell it does under the hood to keep up with one's progress, fact is it didn't work in my case. Unfortunately this went on for over 3hrs (yea I don't "undo" much) :happy:

I hear a lot of people going on and on about how FCPX's database is so much more robust than FCP 7 etc. Well that may be but again I've never lost any data or work in FCP 5-7 (unless it was pilot error). This is the 2nd time I've lost work in X. the 1st time was due to a project becoming so corrupt I could not even launch FCPX unless I removed said project from the HD that FCPX was trying to access it. (Luckily I had already exported it as a QT, hopefully I'll never have to do any re-edits on that project.)
 
Mickey G said:
BTW I'm on the latest version of Snow Leopard running on a Quad I7 iMac with 8GB RAM, (the iMac just before the T'Bolt iMac)
I am editing 1080 ProRes and h264 (not in the same timeline) over 7200rpm FW800 G-Tech drives.
Thanks for any insight into these issues
Click to expand...

This is the first I've ever heard of the autosave "not" working, and I've had some hard crashes or lockups and never had this issue. To me, I would highly recommend being in OSX Lion when editing with FCPX. Lion uses "Versions" which is basically the same idea as FCPX no save. That's the way our machines are setup.

Also, did you install FCPX on a system with FCP7 on it? That can cause random issues.
 
TheReverend said:
To me, I would highly recommend being in OSX Lion when editing with FCPX. Lion uses "Versions" which is basically the same idea as FCPX no save. That's the way our machines are setup.

Also, did you install FCPX on a system with FCP7 on it? That can cause random issues.
Click to expand...

Thanks for the prompt reply!

idk I'm just not so sure about making the jump to Lion since all my other software is so stable. I guess Lion has been out in the wild long enough to be stable with most plug-ins. I didn't realize the versions feature was working with FCPX, that is enticing.

Yes I did install X on the same drive/partition as FCP7. Everyone else that I know of that did this claims there system is fine so I guess I'm just the lucky one.
 
Mickey G said:
Thanks for the prompt reply!

idk I'm just not so sure about making the jump to Lion since all my other software is so stable. I guess Lion has been out in the wild long enough to be stable with most plug-ins. I didn't realize the versions feature was working with FCPX, that is enticing.

Yes I did install X on the same drive/partition as FCP7. Everyone else that I know of that did this claims there system is fine so I guess I'm just the lucky one.
Click to expand...

On the main editing stations, we are dual-booting, Lion and Snow Leopard. FCP7 on Snow Leopard, and FCPX on Lion. This has kept things pretty clean and glitch free.

My laptop has Snow Leopard and FCPX and FCP7, but overall, I haven't had major issues. But if you are experiencing troubles like you have, I would immediately look at the core setup (FCP7 and FCPX on the same boot) as the source of your problem. We have no idea the inner workings of that stuff, and for maximizing stability, I'd recommend double booting over what you have right now.
 
I'd recommend the update to Lion and make sure everything else in Software Update is up to date.

-Noah
 
Laco said:
It hapened to me now.

I'm on Lion 10.7.2 and FCPX 10.0.2 :-(
Click to expand...

Ouch! sorry to hear that but in a way i'm happy to hear I'm not the only one and am not crazy. I love using FCPX but the prospects of losing data really make me hesitant of using the software for anything at this point.
Still though I REALLY like using the software, damn you Apple!

Thanks everyone for the advice and I may go ahead and make the plunge to Lion. However I jump between FCPX, FCP7, Color, etc so much I can't see myself having to dual boot for one piece of software especially since for the most part FCPX and 7 do play nice on the same system. Apple advertises this should work so it should...

-Laco does versioning project/event files really work in Lion, I didn't think that feature was implemented yet??
 
It happens to me also regulary. I'm on OSX Lion and update al the time.
I found out it happens while color correcting. When I colorcorrect I keep checking on the undo option in the menu, and when it can't be clicked it means it won't save. Then I restart FCPX

It is very frustrating you have to keep your eyes on this. I don't have issues on playback though.

Last update allot of glitches are solved, I hope this one will get out very soon.
 
You must log in or register to reply here.
Back
Top