FC crashes whenever I try to apply a filter

Question

Level 1

13 points

FC crashes whenever I try to apply a filter

Alongside my 'day-job' Mac Pro I also run FC studio on my imac as a back-up and for doing odd jobs I want to keep on separate system. It's all been working fine for a couple of years but today, whenever I try to apply a filter I briefly get the spinning beachball then FC crashes and I get a crash report.

I haven't tried all the filters but the ones I have will result the same. I've also opened a couple of previous jobs with various formats (HD / SD / animation / PAL) and they will all crash if I try to apply a filter.

I'm hoping that some simple expedient such as ditching some preferences files or somesuch could be a solution before I have to do things like uninstall / reinstall.

While experienced in using FCP I'm no Mac techy so any simple idiot-proof advice would be very much appreciated.

Thanks

Process:	Final Cut Pro [159]
Path:	/Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier:	com.apple.FinalCutPro
Version:	7.0 (7.0)
Build Info:	FCPApp-906181654~22
Code Type:	X86 (Native)

Parent Process: launchd [98]

Date/Time:	2013-07-09 10:00:24.727 +0100
OS Version:	Mac

Model Name:	iMac
Model Identifier:	iMac11,2
Processor Name:	Intel Core i3
Processor Speed:	3.06 GHz
Number Of Processors:	1
Total Number Of Cores:	2
L2 Cache (per core):	256 KB
L3 Cache:	4 MB
Memory:	4 GB

Posted on Jul 9, 2013 2:19 AM

Reply

Answer 1

Chinook! Author

Level 1

13 points

Jul 9, 2013 3:09 AM in response to Chinook!

Just to update this question; I have just trashed the preferences files (following instructions on this site) and have still got the same problem.

I've tried 'Threshold', 'Light rays' filters which both crashed and then the Gamma correction which worked ?!

If it's of any help the extensive crash report includes this near the top:

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000050da6bee

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Reply

Answer 2

Jul 9, 2013 6:20 AM in response to Chinook!

Did you trash your prefs using this ?

http://www.digitalrebellion.com/prefman/

DM

Reply

Answer 3

Chinook! Author

Level 1

13 points

Jul 9, 2013 7:11 AM in response to David Mclaine

No, I used the instructions from Kenstone.net for trashing FCP7 prefs. It (apparently) removed prefs successfully and the restart created new ones.

Would the 'preferences manager' do anything different?

Reply

Answer 4

Jul 9, 2013 8:15 AM in response to Chinook!

well Preference Manager eliminates the possibility of operator error. It's free and it also allows you to back up your preferences.

Digital Rebellion also has as a crash analyzer which is part of one of their suites of media utiltiies (Can't remember which one, but go to their site and do a bit of digging. You'll find it pretty easily). Although it's not free, it's a worthwhile purchase and there is a free trial available.

www.digitalrebellion.com

Reply

Answer 5

Chinook! Author

Level 1

13 points

Jul 9, 2013 8:34 AM in response to Michael Grenadier

Interesting. Thanks for the info; I'll follow that up.

It still seems to me though that I successfully followed the 'preferences' route correctly but to no avail. What is the thing with changing 'permissions' or is there any other route to cure this problem?

Reply

Answer 6

Jul 9, 2013 8:43 AM in response to Chinook!

The mac os has permissions for each and every file and the os uses these to determine whether the user is allowed to read, or change a file. They can get corrupted but I've rarely been able to solve any problem by repairing permisions. but as far as I know it can't hurt. Just go to applications: utilities: disk utiltiy and repair permissions on your startup drive.

Have you installed any new software or done any software updates recently?

Reply

Answer 7

Jul 9, 2013 8:44 AM in response to Michael Grenadier

And here are some basic fcp troubleshooting tips.

https://discussions.apple.com/docs/DOC-2591

Reply

Answer 8

Chinook! Author

Level 1

13 points

Jul 10, 2013 7:39 AM in response to Michael Grenadier

I've repaired the permissions via disc utility but no joy.

I also went through the basic FCP troubleshooting tips (excellent list btw) and followed many of the suggestions.

The only one I haven't yet tried is the prime one of running disc utility via another start-up disc. I tried booting up from Disc Warrior and it just sat there with the mac start-up logo for ages and ages. Sadly I can't find the original imac install disc to try to boot up from (yet).

I'm beginning to wonder if I should un-install FCP studio (is this fiendishly complicated?) and then re-install.

Obviously my fear is that after a lot of hassle the exact same problem will still be there.

I haven't installed any new software and I haven't done any system updates for ages. I'm one of those people who gets a system nicely balanced, working and reliable and then doesn't fiddle with it. It could be that I DO need to give the system an update of course, but that could simply add another whole load of complications.

Basically, it was all working fine, then it wasn't.

Thanks for your help and suggestions

Reply

Answer 9

Jul 10, 2013 8:40 AM in response to Chinook!

Did you download digital rebellion's pro maintenance tools?

http://www.digitalrebellion.com/promaintenance/

There's a free trial and you can use crash analyzer to get some insight into what's going on.

If you clone your startup drive, you'll be able to boot off the clone and run disk repair and diskwarrior off the clone.

https://discussions.apple.com/docs/DOC-2494

I think carbon copy cloner is no longer free. If so, check out superduper

http://www.shirt-pocket.com/SuperDuper/SuperDuperDescription.html

And once we solve the problem, and get things back to a working state, you should definitely clone your startup drive. That way, if things go south (like they have now), you can clone back to your internal drive and get back to work.

Reply