Final Cut Pro 7 crashing when updating a project file from FCP 6

[Jonathan Eagan]

Okay – I think I’ve discovered the issue – it’s likely got something to do with an incompatible plugin being used. I don’t know how to go about searching this out because there is no way to open the project and check, even off line.

It seems that even if I wipe my system it won’t solve my problem. Please help? How do I suss out this faulty plugin????

[David Roth weiss]

[Jonathan Eagan] “How do I suss out this faulty plugin????”

Start by going to Library>>Application Support>>Final Cut Pro System Support in the Finder. Locate the Plugins folder and rename it to Plugins JE.

Now, start up FCP and see if it opens properly. If so, you know at least one of the plugins in the folder is bad and you will need to suss them out one at a time by adding them one at a time to the new Plugins folder that FCP will automatically create.

BTW, every plugin in the folder is something you added, these are not FCP plugs that come in with the app.

David Roth Weiss
Director/Editor
David Weiss Productions, Inc.
Los Angeles

POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

A forum host of Creative COW’s Apple Final Cut Pro, Business & Marketing, Indie Film & Documentary, and Film History & Appreciations forums.

[Jonathan Eagan]

Thanks.

Tried that, and it did not work.

I can open FCP without any problems, can even import the project media, etc, etc but if I try to launch or open that bloody FCP 6 project file it crashes.

BTW – all it says is FCP quit unexpectedly. There’s not further explanation.

It’s only using the FCS Maintence pack that was suggested above that I have any inkling that it’s plugin related. I’m completely at a loss here.

Is there any way this could be a problem on their end? Should I just wipe my system and reinstall? I really don’t want to do that, if at all avoidable.

Thanks!

[David Roth weiss]

Okay Jonathan, try this test…

Turn off or eject all of your media drives. Now, try to open your project. FCP may take quite a while to get going as it will be looking all over creation for those darned media drives.

Eventually however, FCP may open the offending project and it should tell you that everything is offline. If that happens, don’t save or do anything foolish, just shut off FCP.

If you pass this test it will indicate that you have one or more corrupt media files, not a corrupt project and not a corrupt FCP installation.

Report back with you findings…

David Roth Weiss
Director/Editor
David Weiss Productions, Inc.
Los Angeles

POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

A forum host of Creative COW’s Apple Final Cut Pro, Business & Marketing, Indie Film & Documentary, and Film History & Appreciations forums.

[Jonathan Eagan]

Hi David,

okay – tried this again, to no avail.

The problem is, when I try to open this project, the very first thing it prompts me to do is update the file with a pop up window. If I choose ‘yes’ it begins updating, freezes and crashes. If I choose ‘no’, it simply opens a new project and I get nowhere.

So I can’t even get to a place where it’s showing my media as offline.

So…now what?

[David Roth weiss]

Doesn’t sound good Jonathan. Sounds a ground-up install might be a good thing for you.

David Roth Weiss
Director/Editor
David Weiss Productions, Inc.
Los Angeles

POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

A forum host of Creative COW’s Apple Final Cut Pro, Business & Marketing, Indie Film & Documentary, and Film History & Appreciations forums.

[Jonathan Eagan]

yeah.

that’s what I was afraid of.

Okay – let me ask you this though:

if I do a ground up install – and it still doesn’t solve the problem. I can safely say that the issue is something to do with a file corruption or something on their end?

Thanks so much for your help.

[Alex Snelling]

Hi Jonathan

Before you do a clean install which you should probably do anyway try this.

If you have another computer running FCP6 – doesn’t matter if it is a slow computer – try opening the project on that. If the project opens, then export an XML file of the project and try importing that into FCP7. This may not fix everything but it may allow you to start working on the project now and worry about the cause of the problem later.

If you don’t have FCP6 still installed, find a mate who has and then email them your FCP project (zipped into a protective file) and ask them to create the XML for you.

Hope that might help
Alex

https://www.tantrictourists.com

Alex Snelling
http://www.slackalicefilms.com
https://web.me.com/slackalicefilms/

[David Roth weiss]

[Jonathan Eagan] “if I do a ground up install – and it still doesn’t solve the problem. I can safely say that the issue is something to do with a file corruption or something on their end?”

Not sure I comprehend? On who’s end? I thought this was purely a matter of a FCP 6 file not opening after you updated to FCP 7.

Whoever “they” are, does the file open on their system?

David Roth Weiss
Director/Editor
David Weiss Productions, Inc.
Los Angeles

POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

A forum host of Creative COW’s Apple Final Cut Pro, Business & Marketing, Indie Film & Documentary, and Film History & Appreciations forums.

[Jonathan Eagan]

Hi,

sorry for the confusion. I’ll elaborate.

As I mentioned in another post above, I’m working remotely right now and the director sent me a project file from the production office that was created using FCP 6.

Now they are aware that I’m running FCP 7 and they themselves are going to be updating next week. I wondered if there was any way something they might have done on their end could be contributing to my problem. I don’t want to inform them yet of the situation until I’m sure it’s not my system, yunno?

Either way – when I import the media I was sent on the drive I don’t encounter any problems, so I’m guessing there’s no corrupted file.