Here’s the perspective from someone who works on the inside, and can give you a little information on how Apple behaves with its OEMs. We had to port our drivers and software for the Matrox RTMac realtime video editing card to OS X. (I’ve been the tech writer for the RTMac project since its inception, even though I’m a PC person. Unfortunately, the card is no longer much more than an analog I/O and VGA out, what with FCP 4.)
Now, OS X came out long before our OS X drivers did. In fact, our drivers are still being open beta tested. For two years, the RTMac user forums were filled with bitching, tantrums, taunts, general stupidity, and - I shit you not - threats of class-action lawsuits because our drivers weren’t ready. The usual argument was this: “Adobe has ported Photoshop and Illustrator to OS X! They did it in {whatever} months! WHY CAN’T MATROX GIVE US DRIVERS? GIVE US DRIVERS!”
To which one of our gentle moderators would respond to the effect of, “OS X is based on an entirely different kernel than previous versions of Mac OS. Porting software is far easier than our task, because we have to completely re-write our hardware drivers from the ground up before we can even begin to port our software.”
To which one of the MacCult would reply: “See? Even Quark is out before RTMac! What’s wrong with you, Matrox? You suck! WHERE ARE THE DRIVERS? CLASS ACTION LAWSUIT! WHO’S WITH ME?!?!??”
Photoshop. Illustrator. Quark. SOFTWARE.
RTMac. HARDWARE AND SOFTWARE.
Now, these are supposedly video editing professionals. They’d venture into our RT.X (PC) forums and see all of the fantastic things our software can do with Adobe Premiere on an equipped 2+ GHz machine running WinXP.
“GIVE US MORE EFFECTS! PC USERS GET ALL THE FLEX 3D EFFECTS! GIVE US EFFECTS IN FINAL CUT PRO!”
Listen, fuckwit, you wanna know an insider secret? The reason we can give you a shitload of effects in Premiere - including our own proprietary ones, in our plug-in - is because ADOBE FUCKING CO-OPERATES WITH US. It’s in their interest to, because we bundle their software with our PC hardware/software suites.
Apple stopped co-operating with us after RTMac 1.0. One measly 15-minute conference call a week is all Apple gives us now. So of course we’re not going to be able to develop more effects for your glorious G4 or G5 running FCP 4 because APPLE WON’T GIVE US THE SOURCE CODE WE NEED.
An RTMac - using its onboard Flex 3D architecture and G450 chip - fully integrated with FCP 4, including plug-ins with proprietary realtime chroma keys, waveform and vectoscopes, color correction (hardware-driven, so as to take the load off your precious G4 or G5 processor and let you do OTHER THINGS while you edit) - would be pretty fantastic, for well under $1000.
We could have done all that, but Apple wouldn’t let us. We did manage to write a cool realtime 3D motion effect that blew FCP’s out of the water, but there was a bug on Apple’s side, and we wrote a work-around, but it wasn’t that great, and Apple wouldn’t fix their FCP bug.
I can’t tell you how many times I’ve had to document an Apple bug in our Release Notes as if it were our bug. I’ve finally taken to coming out and writing “This is a limitation in Final Cut Pro” or “This is a limitation of Mac OS X.”
The RTMac card is over, kaput, dead, after release 4.0 and a couple of updates. Plans for future Mac products have been scrapped. Why? Because we can’t invest the time and money to develop and support products for a company who won’t co-operate with us in optimizing our third-party hardware and software.
But the users don’t understand that. If it doesn’t work under OS X, it’s crap.
And I don’t think Win2K users of our next RT.X release will whine when told we’re only supporting XP from now on. They’ll just smile, and upgrade, and enjoy blazingly fast realtime editing with more effects and features than you could ever imagine on a software-only video editing system.
If you’re going to think different, don’t forget the think part.