This discussion is locked
ridindave

Q: Apple Shake crashes with optical flow & new multicore MacPro

Hey there,

I've been working with Shake for years, on powerPC G5, then on intel macpros. I've been thru the 10bit PRHQ turned into noise with 4.1.1 update. I finally had a stable usable 4.1.1 version that ran perfectly on a 8core 2008 macpro, running latest 10.5 OS.

I've just bought the double 6core 2010 macpro, that runs 10.6. Shake is even faster, and I can multiply parallel renders, that's really cool.
What's less cool is every time I ask for optical flow module, Shake crashes immediatly.
I have to use older machines to deinterlace or convert footage, and that is really not cool at all...

My question : Is it a problem with OS version, or with hardware ?
I runs smoothly Shake on intel 8core macpro without a single problem, but it is 10.5, and I guess I can't downgrade my 2010 macpro to 10.5...

Is there any workaround ? Will Apple endlessly mute about Shake ? Do I have to simply trash one of the best software ever ?

Thanx for any help,

David

intel multicore MacPro, Mac OS X (10.6.7), 12GB Ram

Posted on Apr 13, 2011 3:29 AM

Close

Q: Apple Shake crashes with optical flow & new multicore MacPro

  • All replies
  • Helpful answers

  • by stuckfootage,

    stuckfootage stuckfootage Apr 14, 2011 1:27 PM in response to ridindave
    Level 4 (3,040 points)
    Apr 14, 2011 1:27 PM in response to ridindave
    Not really an answer, but is there a crash
    when you do other optical flow operations?

    1. Compressor > Frame Controls On > Quality Best
    2. Motion > Inspector > Clip Properties > Timing > Frame Blending > Optical Flow
  • by Patrick Sheffield,

    Patrick Sheffield Patrick Sheffield Apr 14, 2011 4:27 PM in response to ridindave
    Level 7 (29,175 points)
    Apr 14, 2011 4:27 PM in response to ridindave
    Other's here have reported problems with optical flow on greater than 8 core systems. I think even Motion (that was the beneficiary of Shake's optical flow code), had problems (and a fix). I don't know if anyone had a workaround for Shake's issues...

    Patrick