Apple big picture….how big of a deal is this really?

[Chris Kenny]

[David Cherniack] “Now while I agree with the first part of the sentence, the “few hours” strikes me as unbridled optimism :)”

Heh. Well, the Ruby script I wrote to take an FCP 7 XML file and re-link everything it to clips rendered out of Resolve based on reel/timecode only took about 15 hours, and this should be a fair bit easier. (Again, assuming a sensibly designed, well documented API.)

[David Cherniack] “But I was refering to IO drivers and keyframeable plugins….if keyframable is going to be at all possible – hard to see how it couldn’t factor into their plans if they see it as a pro app. But is there a place for that in the present interface or will it need something that’s not yet apparent?”

The I/O hardware vendors tend to be pretty good about drivers. I mean, people with hardware more than a couple of years old are probably screwed, but that’s nothing new.

The plug-in architecture is just a version of FXPlug. Everything needs to be recompiled because FCP X is a 64-bit host, and I would guess there are some other changes that need to be made, but I think plug-ins probably won’t be a problem. And I’m not quite sure what you mean about keyframing. FCP X has perfectly serviceable keyframe editing that I would assume plugins would be able to use.

—
Digital Workflow/Colorist, Nice Dissolve.

You should follow me on Twitter here. Or read our blog.