Currently Being ModeratedJan 29, 2012 6:53 PM (in response to Pancenter)
Man, I can't believe how this thread has evolved since I started it back in June of last year.
Just to follow up: I ended up switching to Premiere Pro, and haven't looked back. PP is far more like FCP7 was, but faster and with some really nice features that FCP never had. On the other hand, it's not without its issues, has occassional crashes, and does a few strange things here and there...but FCP did that too...
I'd love to love FCPX, but as someone who makes his living editing every day, I just can't deal with it's issues. Maybe in a year or two, but judging by Apple's current 'consumer' stance, I wouldn't hold my breath..
I'll check back in another 6 months or so to see if things have improved...
Currently Being ModeratedJan 30, 2012 11:23 AM (in response to marion jack)
Jack, if you use Snow Leopard - stop it! Use Lion instead.
Go to the top of the page and look and andynicks comments...
If you think Premier Pro is a 'brilliant' alternative to your problems then listen to this:
It would seem that the new pretender, is sadly, just that!
Currently Being ModeratedJan 30, 2012 5:20 PM (in response to the black sun)
I hate this program I hae been working at a snails pace for hours only to have FCPX decide my work must not have been worth saving ... and no this isnt the first time I have Lion ... there are pages of comments here but are there any answers ??? HELP ME PLEASEEEEEE
Currently Being ModeratedFeb 24, 2012 10:43 AM (in response to Benjamin Freedman)
I am really dissappointed. I am a carreer editor or 20+ years and I find I can't work on a product I don't trust. I just lost 2 days work on a project I was cutting in X. I was trying to get a feel for the layout & language when I crashed and discovered there is no save "feature". My "CurrentVersion.fcpproject" is corrupted and there is no other version.
The time on the preoject is not a loss, but I am afraid FCPx is.
Currently Being ModeratedFeb 24, 2012 10:51 AM (in response to EditMonkeyNYC)
What version of the software is this? What version created the project?
Currently Being ModeratedFeb 24, 2012 1:54 PM (in response to Benjamin Freedman)
Please take my comments as constructive. I'm not a professional so can't relate well to pressures and frustrations that people like you are having with FCP X; however, I have experienced loss of work and time with every video and graphics program I've ever used over the past 20 years and know the sick feeling you get when this happens. I'm currently using Premiere Pro CS5.5 on my iMac and Vegas Pro 9 on my PC. I'm now deeply into FCP X and, despite shortcomings, I think it has many features that are superior to editing programs I'm familiar with. Will I quit using Premiere and Vegs? No -I will contiue to use whichever program best suits the footage I've got and the delivery format I'm after. I'll always go to Vegas for extensive audio content and editing. Premiere for integration with After Effects and Photoshop and DVD authoring.
I know my approach probably isn't practical if one's livelihood depends on delivering quality product in the most efficient manner or if you have employees who have to be trained and highly proficient with whatever systems and software you use. However, I can tell you that my experience with FCP X has turned from disastrous to one of actual enjoyment. 10.0.3 on OSX 10.7.3. iMac 3.7 GHz i7 w 16 GB.
I haven't had a lock-up or crash for two weeks and very seldom get the spinning beach ball. I've never lost a project so far. How did this come about? By spending a lot of time going through these posts and paying special attention to what Mr.Wolsky and other frequent contributors suggest. These guys know how to help you overcome the difficulties. Do what they say and I'm guessing you might not want to give up on FCP X.
In particular, like you, I can't bring myself to trust the built-in file save feature and am still very uncomfortable with how FCP X manages my files. But there's an easy solution - simply duplicate the project at regular intervals and work from the most recent copy. Put one copy on your working drive and backup on a separate drive. Download Active X Manager ($4.99) and it will automatically remove the backup from your active project library and restart FCP X. Same will automatically restore backup to active project library in the event of a disaster.
Hope this helps.
Currently Being ModeratedSep 13, 2012 2:42 PM (in response to Benjamin Freedman)
So, it just happened to me as well, lost 5 hours of work in a very intensive and busy project. I really don't have time to report it, but I'm to angry not to.
What happened was that i had to import a Final Cut 7 XML file via 7toX.
This utility makes timelines into compound clips in the Event library.
I edited one of the compound clips, but at a certain point the sound started to sound distorted, so I quit to release resources (FCPX eats ram like mad).
When i opened FCPX again, the Compound clip was back to it's first state.
This is unacceptable, how can Apple promote persistent state amongst their development community, when they can't even implement it themselves?
I guess it's no sleep for the next few nights.
Currently Being ModeratedSep 13, 2012 2:58 PM (in response to ole.kristensen)
You're not supposed to use compound clips like projects. They're a tool, but they're not projects. You're supposed to open the compound clips that 7toX used to import sequences and copy the contents into an FCP project.
Currently Being ModeratedSep 13, 2012 3:21 PM (in response to Tom Wolsky)
I fail to see the relevance. Where ever i am allowed to make changes, those changes have to be implemented persistently, and Final Cut must save them.
Otherwise, what will letting me changing them serve?
I had no warnings from either Final Cut or 7toX and cannot be expected to know that an editable object is not persistent.
I will tell 7toX that they should add a warning message in their flow, that their compund clips should not be edited -
But it is still a bug in FCPX. There should be no tools that don't work, no matter if you use them sematically correct or not.
Currently Being ModeratedSep 29, 2012 12:21 PM (in response to ole.kristensen)
This just happened to me for the first time (and has happened twice since). Running Mountain Lion 10.8.2 with Final Cut Pro X 10.0.0.5. Exited Final Cut Pro after an hour and a half of editing, re-opened later, and my project was back to a timeline with the original clips in it. All of the effects, audio enhancements, in & out points, etc. were gone. Really frustrating. Working off a local drive on a laptop, no SAN involved.
I really wish there was a manual save button. That would make me feel better. I'm going to try doing a File > Duplicate Project next and using that for a few days to see if I can work around this issue as user "Grandpa Adams" above suggested. If I can't trust something as simple as the system not deleting all of my work, well, need I say more?
FCP-X is growing on me, but these not-so-small bugs are starting to drive me nuts. I still have my other major (and majorly annoying) bug where all of my RAM gets eaten (8GB on our newer i7 FCPX testing laptop at work) during export from within FCP-X. I've tried doing a fresh install on a spare drive, running all of the OS & FCP-X updates, and I still have these problems. Not cool. I haven't even bothered to try it on my work desktop because I don't want to screw up my FCP7 install.
Frustrated. iMovie '11 works better than this does.
Currently Being ModeratedSep 29, 2012 2:02 PM (in response to kaidomac)
You might want to look at Pro Versioner from Digital Rebellion to create an autosave vault.