Incoming
What do you know about FxPlug?
Motion users are probably well aware that it’s an “open” set of protocols used to create filters and generators. With the FxPlug SDK third-party developers are able to access “the same GPU hardware acceleration or CPU-based technologies that Motion uses” (FxPlug SDK for Motion), and it would seem that a number are already. If you need further convincing, no lesser luminary than Graeme Nattress has already offered his endorsement for the longevity of the standard.
Have you heard that FxPlug will also be supported “in an upcoming release” of FCP? This was one of the announcements Apple made alongside the other technology previews they featured at NAB. I’ve been hoping to read more about it, but haven’t seen anything other than further confirmations.
32-bit float RGB and YUV image processing. Access to OpenGL, Quartz, QuickTime, and Core Image. All within FCP. This used to be big, big news!*
Has the moment passed? Or are people awaiting firm details this time around?
Well, I for one am excited. The more time I spend with Motion, the more intrigued I become. And while I’m aware that there’s a lot of love out there for AFX, I do think Motion is vastly underrated. So I say, bring it on Apple! I very much look forward to embracing this particular advance in FCP workflow.
*Such integration was the subject of much speculation before FCP 5 and Tiger made their debut last year.