So I know there's the big thread about trying to get the Color plugin from Apple, and a lot of waiting for RED to produce something. Note that I'm not complaining here by any stretch of the imagination. I'm... pontificating, I guess.
I've been thinking a lot about the Color plugin, the various workflows that we've been using to get around the new color science, and the fact that other tools (BaseLight, Scratch, etc) have the new toys and we don't. One of the things that struck me was the fact that these are *other companies*. Places with internal development teams that do nothing but add hot new features to their product, a narrow product line, and management that supports said development.
Let's be honest. Apple's primary market isn't professional video. It's more or less at the bottom of their product tree. And there have been some disturbing rumors about the future of that product line. All that said, is it really all that surprising that support for new video tech isn't really all that forthcoming from Apple?
RED, on the other hand, lives and dies by their product. And I love pretty much everything they do. But they're not as big as Apple. And I imagine their software development team is significantly smaller. So they're busy. Something like RedCine-X pops up, and that's the development focus. I'm ok with that, since the result is pretty amazing.
So I had an idea. I know it's not really feasible, for a number of reasons, but I'll feel better if I get it off my chest and out into the wild.
Why not outsource, or, (god forbid) open-source the Color Plugin? Take the development burden off the team at RED and let them keep working on the hot new toys. Tie the plugin firmly to the SDK, like all the other post solutions. Color science gets updated in the SDK? We don't have to clamor at Apple and RED for a new plugin. The outside development team will take care of it. (We'd have to clamor at them, but it'd be better than trying to get a response from Apple. :P)
I see two major problems with this idea of mine.
1. Apple's response. Whatever architecture/hooks were used to build the Color plugin aren't exactly documented and open. So I'm guessing open-source would be out of the question.
2. RED's response. Again with the undocumented Color hooks. Also, I don't know how much of the Color framework is SDK based, and how much is proprietary.
There's also the issue of finding coders. It's a project I'd be willing to work on, but I doubt it'd be a one-man show, unless both the hooks and the SDK are a lot simpler than I imagine. And finding people to work for free on it might be tough. Then again, I would willingly pay a reasonable amount of money for a reliably updated plugin rather than having to wait on RED.
So that's my thought. Discuss, if you'd like.