FCP 7 quits while using MB Looks

[Andy Mees]

Have you tried Color? It ships as part of the Final Cut Studio suite and is much more capable than MB Looks, and if you need more presets to work from you can check out Color Looks as an add on:
https://support.apple.com/downloads/Color_Looks

Maybe have a look at Core Melt’s Pigment:
https://www.coremelt.com/products/v2/pigment—color-tools.html

Also check out Patrick Sheffield’s Movie Color:
https://straylight.tv/pluginz/

[Rafael Amador]

With that computer you shouldn’t have these issues.
If you just have installed everything, I would recommend you to run Diskwarrior or TechTools.
After a PERFECT installing normally the system is a huge mess.
rafael

http://www.nagavideo.com

[Jeremy Garchow]

Sounds like the MB looks plug in is causing problems. This isn’t FCPs fault necessarily. I would contact the makers of the plug in and ask them if they have seen this. Perhaps you need an update to bring you up to speed.

[Zeyat Aden]

Rafael,

Yeah the system is a mess after the upgrade of Snow Leopard for the mid-2010 new MacBook Pro (15″ & 17″). I use DiskWarrior 4.2 and it still leaves about six items three of which are the SUIDs as below:

Permissions differ on “System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/Deploy.bundle/Contents/Resources/JavaPluginCocoa.bundle/Contents/Resources/Java/deploy.jar”, should be lrwxr-xr-x , they are lrw-r–r– .

Permissions differ on “System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPluginCocoa.bundle/Contents/Resources/Java/deploy.jar”, should be -rw-r–r– , they are lrwxr-xr-x .

Permissions differ on “System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPluginCocoa.bundle/Contents/Resources/Java/libdeploy.jnilib”, should be -rwxr-xr-x , they are lrwxr-xr-x .

Warning: SUID file “Applications/Utilities/Keychain Access.app/Contents/Resources/kcproxy” has been modified and will not be repaired.

Warning: SUID file “usr/libexec/authopen” has been modified and will not be repaired.

Warning: SUID file “usr/libexec/security_authtrampoline” has been modified and will not be repaired.

I spoke with APPLE and they said I shouldn’t worry about that. But FCP still takes time to open and then quits after a while on the long project while it opens pretty fast and doesn’t quit on the short project. Any idea why it does this. The Apple guys suggested that I should delete the Preferences, which I’ve already done thanks to the suggestions posted here. Thanks.

Andy,

I tried to work with FCP’s COLOR but when I try to test/check the COLOR by opening it, I get this prompt:
Color recommends a screen resolution of 1680×1050; this system currently has a screen resolution of 1440×900.

There must be a way to fix the color resolution of the new MacBook Pro 15″ iCore 5. I went into the DISPLAY in the System Preferences and the display shows only 1440×900. Do I need to calibrate the color? But the screen color looks fine… even though when purchased in April it looked much much brighter. Thanks.

Jeremy,
I think I’ll have to contact MB Looks if I don’t solve the problem by tomorrow.

The problem still persists. MB Looks definitely causes FCP 7 on intel MacBook Pro to quit sometimes at Launch or sometimes after working on the Timeline Sequence for a while. The Timeline project is about 1hr and 45min but there are so many other projects within that projects in BIN folders but only 2 other projects are open. Do you think breaking the projects into shorter sequences and saving them separately might help? But the final movie will still have to come together. It’s a 90-minute feature. Why does FCP take so long (more than 10-min to open the long project while it opens the short projects in a jiff? Did anyone ever encounter this problem?

Thank you all again. Any advice or suggestion is really appreciated. Thanks for sharing the knowledge.

[Jon Chappell]

Here’s how to run Color under a lower resolution:
https://www.digitalrebellion.com/blog/posts/how_to_run_color_below_its_minimum_requirements.html

My software:
FCS Maintenance Pack – Tools to keep Final Cut Studio running smoothly and fix problems when they arise
FCP Versioner – Backs up Final Cut Pro projects to XML and creates changelists for each revision
More tools…

[Rafael Amador]

Hi Zeyat,
I work often with MB and I have had a lot of problems due to the limitation in my GPU (256MB), but I’ve never experienced crashes.
I’m in Leopard so I can not have a look to those “SUID files”. I’ve saw them before. Are locked files and can not be modified.
When you did ran DW, did you got the “0 items out of order”?
rafael

http://www.nagavideo.com

[Shaun Boyte]

Hey Zeyat –

I am having the same exact problem. It’s just recently started to happen after I installed the new MB Looks AE CS5 update.

I am running Snow Lepoard, on a new iMac, with FCP 7, and AE CS5. The error happens when I edit one clip in MB Looks and then click on another clip to start color correcting. FCP quits with the following message,

“Final Cut Pro quit unexpectedly while using the Looks3 plug-in.”

I am trying to contact Red Giant right now to solve the problem…must be in the new update? Anyone have any updates? I am on a tight deadline –

Thanks!

[Zeyat Aden]

Hi Rafael,

Yeah, DW does say the same thing Apple’s Disk Utility does and even though they both report “repaired” and when I run them again, the same things come out. Apple Guys said that I shouldn’t worry because that “Java” thing is just for internet purposes.

I deleted them all now… including the SUID’s, which can’t be modified. And the DU & DW don’t report any differences anymore.

Funny that Apple comes up with all these updates just to get things messed up every regular fellas…

And MB Looks still acts pretty weird. If you’ve never had any problem with MB, then it must have some disagreement with the new MacBook Pro. Ironically sometimes FC opens but only one of the three projects in the Timeline Sequence and doesn’t even show that and when clicked to see it displayed it says “System low on Memory”. That can’t be true but then how can a machine lie? Can someone help me figure this s**t out. Makes me doubt the beauty of Apple now. Thanks.

[Zeyat Aden]

Shaun,

Yeah it does the same exact thing that you describe. Is it really MB or the MacBook Pro? Please let me know any new updates or findings.

Did anyone else have any problem like this?

Thanks for all the help

[Shaun Boyte]

Hey Zeyat –

I am actually running into the error on both an iMac and an Mac Pro, haven’t hit the issue yet on the MacBook Pro, however, am sure when we do some color correction next on the MBP we’ll get issues there as well.

I have been working with a Red Giant Software guru all day on chat, his initial tests he had me tried failed ( reinstalling, resetting permissions, etc.). He had me send over a crash report for him to look over. Am waiting to hear back from him soon – I’ll keep you posted if I run into any solutions. My initial guess is that it’s a software error that’s going to need to be updated with a new version of 1.4. Coming to the conculsion only after it failed on two separate machines after installing AE CS5 and the new 1.4 software that MB Looks required to run.

Keep you posted on any word – let me know if you find out anything in the mean time.

Thanks so much!
Shaun Boyte