COLOR bug? Constantly crashes...

Discussion in 'Digital Video' started by ZballZ, Mar 12, 2012.

Most Liked Posts
  1. ZballZ, Mar 12, 2012

    ZballZ macrumors regular

    Joined:
    Nov 11, 2006
    #1
    I use Apple Color to do very basic primary grade on corporate videos. I normally work on a MBP with Final Cut studio, but recently got a macbook air to take on the road. It works great, and runs Final Cut Pro much better than expected...

    But recently I wanted to do a little basic grading on a project, and since I was working on the Macbook Air, I just opened the project from that machine.

    BUT; Color crashed immediately - "quit unexpectedly"-error.

    So, I did different test, and even tried to cold-start Color, which worked fine until I imported a clip. Immediately it crashed again ! I tried re-installing. Deleting all preferences. No difference. It crashes still.

    So - I cant really figure out what the problem is. Could it be that Color simply will not run on Intel 3000 HD gfx card? Or is it something to do with Tiger OSX? (my MBP still runs Snow Leopard). ? Or has the fact that I have FCPX running on the same machine something to do with this??

    I know it will never run great on an Air, but would still be nice to do some simple correction...

    Comments and ideas greatly appreated...
     
    share
    + Quote Reply
  2. LethalWolfe, Mar 12, 2012

    LethalWolfe macrumors G3

    LethalWolfe

    Joined:
    Jan 11, 2002
    Location:
    Los Angeles
    #2
    I don't know if Color is compatible w/integrated GFX cards. What kind of media are you trying to load into it? If you open the same media and same project on another machine does it work?


    Lethal
     
    share
    + Quote Reply
  3. CaptainChunk, Mar 13, 2012

    CaptainChunk macrumors 68020

    CaptainChunk

    Joined:
    Apr 16, 2008
    Location:
    Phoenix, AZ
    #3
    Are you on Color 1.0 (FCS2) or 1.5 (FCS3)? On Color 1.0, Intel graphics chipsets aren't supported at all, but Color 1.5 does support the 3000 HD chipset.

    FCP X shouldn't have anything to do with the crashing. It runs independently of the legacy FCS apps.
     
    share
    + Quote Reply
  4. ZballZ, Mar 13, 2012

    ZballZ thread starter macrumors regular

    Joined:
    Nov 11, 2006
    #4
    I am on color 1.5.3 - and the crash happens on all types of clips. Even if I import a single Prores clip.

    I tried re-install, trashing prefs etc. No difference...
     
    share
    + Quote Reply
  5. serchbb, Mar 16, 2012

    serchbb macrumors newbie

    Joined:
    Mar 16, 2012
    #5
    I have the same problem. Tried repair permissions with disk utility.... but nothing... keeps crashing and crashing and crashing!!!

    I need to work with my MBA!!!!

    Any ideas? Someone????
     
    share
    + Quote Reply
  6. pica93, Mar 19, 2012

    pica93 macrumors member

    Joined:
    Apr 21, 2008
    #6
    Any Fix for this? - I too, am on a i7 Macbook Air 13". With Color 1.5.3 and OS Lion 10.7.3. With exactly the same problems with importing stuff into the timeline of color. It crashes......
     
    share
    + Quote Reply
  7. lesyork, May 2, 2012

    lesyork macrumors member

    Joined:
    Jan 31, 2011
    #7
    I've just had to fix this problem on my MBP8,2. Unfortunately for you, it was resolved by switching to the dedicated graphics card (I use gfxCardStatus). It doesn't seem to play ball with my HD3000 at all.
     
    share
    + Quote Reply
  8. cgbier, May 2, 2012

    cgbier macrumors 6502a

    Joined:
    Jun 6, 2011
    #8
    Yep. Color crashes also when I forget to switch over to the discrete GPU. Seems the Pro Apps don't really like them HD3000 cards. I have some issues with Aperture and FCP X also with that Intel thing.
     
    share
    + Quote Reply
  9. vet, May 11, 2012

    vet macrumors newbie

    Joined:
    Aug 26, 2011
    Location:
    Vancouver
    #9
    I've got the same issue here running Color 1.5.3. Doesn't make sense for it to be crashing out of the blue since it used to work fine. I'm also running it on an i5 MBA. Again, not sure what's wrong, but it used to work on the same machine flawlessly.
     
    share
    + Quote Reply
(You must log in or sign up to post here.)

Share This Page