4 ms·
And hundreds if not thousands of other movies and tv shows. Shake was it. It was all there was around the late 2000's to be able to comp 2k footage in reasonabl
by 0xRusty 4y ago
And hundreds if not thousands of other movies and tv shows. Shake was it. It was all there was around the late 2000's to be able to comp 2k footage in reasonable time. The void filled by its demise was so real some vfx companies panicked and bought the source code from Apple for a fee (I think it was about $100k) to maintain their own version. Luckily nuke came along by around 2010 and is now the absolute standard. I don't know of a single major vfx studio that doesn't use it for all their compositing.
- Teever 4y agoAny idea what made Apple shit the bed on Shake?
- TimTheTinker 4y agoApple's MO with product acquisitions has always been to port them to MacOS if necessary, then kill off support for other platforms. In this way they hope to strengthen their own desktop platform, much like Office strengthened Windows for many years. If this MO is a non-negotiable, then Apple really made the mistake when they acquired Shake. Production studio workflows built on Shake were all Linux-based, and there was no way that was going to change, regardless of the price. Apple tried to lure then with increasingly lower prices for the MacOS version of Shake, but it had few takers, even with new features and Final Cut Pro integration. So Shake (which was still primarily a Linux product) became a liability for Apple, because continued support of it didn't align with Apple corporate's priorities -- because it wasn't really a Mac OS X product that would increase Mac OS X's platform value as long as they had to also support Linux/IRIX. Just my guesses ... there was likely significantly more nuance involved than what I detailed above.