Edgar Pitts
Well-known member
- Joined
- Aug 19, 2007
- Messages
- 170
- Reaction score
- 0
- Points
- 0
- Location
- Dallas, TX
- Website
- www.jetrefilm.com
Jannard said:For a long time now, we have talked about ongoing development with regard to R3D support. As all of you know, we have been working very closely with Apple and ASSIMILATE from very early on to develop consistent workflows.
As part of expanding our workflows and our partner base, we are creating a tiered partner program that will roll out in full this year. This program will be how other companies can access R3D as is appropriate for them and for us. The first step is establishing RED Lead Development Partners. Apple and ASSIMLATE are the first and currently the only companies here. We have always said we will open up R3D to other partners, and we will. But we are going to do it right.
Initially, we planned to open R3D around NAB this year. But there are so many upcoming R3D improvements and changes that we need more time. The delay of Build 15, and the subsequent split of the image enhancements into Build 16 have set us back. We can't afford to miss anything, and we need to make sure everything is thoroughly tested throughout the image chain. We also have to insure backwards compatibility with all our apps. I know this delay will be disappointing to some, but it’ll be worth the wait. We are working hard to catch up and open up our community to partners that can deliver bulletproof workflows. To release too early would be catastrophic to all our customers.
I am a little dismayed that the Tiered Partner thread was closed so quickly. You were getting an honest response from your userbase.
Why would it be so difficult to add Cineform as a current tiered partner??????
jbeale said:We have one case study so far: the Cineform R3D2DPX solution. It was posted Jan. 16 2008: http://www.reduser.net/forum/showthread.php?p=138517#post138517
Later that day, Graeme pointed out the image quality shortcomings with the third-party debayer, complete with still frame examples. http://www.reduser.net/forum/showpost.php?p=138650&postcount=23 ...after seeing that comparison, many redusers spoke up and said R3D2DPX was poor quality, and they would not use it.
The following day, 1/17 David responded with an updated R3D2DPX version http://www.reduser.net/forum/showpost.php?p=139204&postcount=86
complete with other still frame examples. I'm not going to comment myself on what those still frame examples showed but look at them yourself, if you like.
At that point, Jim objected to the existence of R3D2DPX and there were quite a few rather emotional posts. The following day, 1/18, R3D2DPX was withdrawn, and the thread was closed. So ended that short chapter in RED history. What can we learn from it?
Probably lots of things, but the one I'd like to highlight is that development of useful tools can proceed very rapidly, if given the chance.
They clearly need very little Red resources, as they have been doing this for a long time. I don't see the issue with adding them unless this has to do with agreements with Apple and Assimilate. In that case...