Joel Bocko
Forum Replies Created
-
Further update: apparently what I have to do is keep a separate backup project available where I copy and paste the sequence from time to time. My autosave vault past a certain point is inaccessible so I have to actually “physically” back the file up myself repeatedly or I risk losing everything. This is nuts – there’s gotta be some workaround. Besides getting a new computer with an operating system that isn’t a decade old…but that’s not an option right now unfortunately.
-
Ok, now it’s happening again to ANOTHER project. It seems like if I close a big project, and re-open it many hours later it won’t re-open. (Again, when I go into the autosave vaults everything of a smaller size is available but once it gets up to a certain level – in this case jumping from 44 KB to 276 – it just keeps crashing.)
-
Since I was able to successfully export the video and am thus done with the project, I decided to delete all the media files completely (they were on my desktop). But the project STILL doesn’t open.
Incidentally, when I received the xml yesterday I created a whole new project name. And now that I’m done exporting and have closed and attempted to re-open THAT project, it won’t open either. Very strange.
So now two different project names (albeit spawned from the same initial project file), with media disconnected, crash FCP every time they are open. But all my other projects are fine, including some the same size or bigger. I guess there was just some weird corruption somewhere along the way deeply embedded in the file, to the point where even when opened on another computer and sent back to me as an xml which I successfully imported back into my own FCP…it still won’t re-open when closed.
Very weird.
-
I still don’t know why the file went screwy in the first place, but happily I was able to find someone who could import the project into Final Cut Pro 7 on their own computer, and then send me my project back as an xml. I had to bump it down to version 2 in TextEdit to import it, but when I did, the project was back online and able to open.
That said, I’d still love to know if anyone has further explanations of WHY this might have happened or other troubleshooting options if something similar happens again without a generous soul on hand to send me an xml.
-
Ok, looks like even though I was using Final Cut Pro 6, I could only import xml versions 1 and 2. So I went into TextEdit, changed “4” to “2” and it worked.
-
I just had this same problem (trying to import an xml from FCP7 to FCP6). Unfortunately when I opened up textedit the “xmemlversion” was ALREADY set to 4. So that wasn’t the issue. I even went through the textedit and changed all the “version 7.0” text (which probably had no impact on how it was being imported) to “6.0” out of desperation, and that didn’t work either.
-
Yes, unfortunately, I’ve tried all 4. Since opening the project crashes FCP, that means I’m restarting it every single time (dozens at this point) that I try to open the project. I rebooted and/or shut down the computer several times (once for 90 minutes) and trashed the 4 key preferences suggested in another thread. None of it worked – every time I open it I still get the good old spinning rainbow wheel, followed by the message: “The application Final Cut Pro quit unexpectedly” (etc). Occasionally, usually when I am transferring files to a thumb drive ody enough I will get the “reading project” window which makes it as far as 50% in a few seconds before freezing.
I’m close to redoing the project from scratch/memory unless anyone has other ideas how to open the project that’s just sitting there, intact but unusable. Although even if I go ahead with that it would be good to know any workaround in case (shudder) it happens again.
-
Not to wander too far off-topic but out of curiosity, what are the recommended OS for FCP 6? I’m using 10.5.8 and haven’t had too many problems in the past but now a project keeps crashing.