Those who have been following various threads on RED User the past few months know I've organized a team for independent testing of RED #8 in Los Angeles the Los Angeles area immediately after I receive the camera. More info will be released as we get closer to the delivery of #8, which is now scheduled for August 30. As Jim Jannard noted, that delivery date could still change. The point is, #8 will be tested immediately after delivery of the camera. Here is some info on the testing of #8:
We'll test both cine-style and EFP style setups, scores of lenses, accessories, etc. Impressions and results will be posted on RED User, HD for Indies, and some magazine articles I'll write. Various news outlets have requested information about the testing, and interviews with the testing team members. Iíll have unlimited time to work with the camera system after the testing sessions, so I will personally take a mostly hands off position in the testing, and rather let the team do their thing. Iíll shoot DSLR stills of the team at work, and I am producing the testing. The tests will not be a shootoff against other camera systems, but rather real world shooting and testing of a production RED One camera system with as many setups and lighting conditions as we can fit into 2 days, then a technical analysis of the results.
Evin Grant has accepted my invitation to direct the testing. The team is highly experienced and diverse in their backgrounds. As of now, the team members who have accepted invitations are: Me, Evin Grant, David Mullen ASC, Charles Papert SOC, Matt Uhry, Ken Corben, Haakon, Brook Willard, Alexander Nikishin, Ralph Oshiro, Daren Findling, and Jeff Kilgroe. There will also be an ace FX guy and a veteran camera technology guy, both of which will remain un-named until after the testing sessions when the results are published. I'm excited about the skill set and experience composition of the team - cine, EFP, still photo, editors, FX, camera technology, specialty cinematographers, etc. Nobody is being paid for their time spent testing Ė theyíre donating their time, something I deeply appreciate. Itís hard matching team memberís work schedules against the testing days, so it may happen that some of the team members wonít be able to attend both days, or attend at all. Weíll cross that bridge when we come to it. Weíll have a list of reserve testers we can call on as replacements, should a team member be unable to attend. If initial team members have to drop out for scheduled work, reserve list members will fill their team places.
For equipment security and crowd control purposes, the location of the testing facility will be kept secret until after the testing, when the results are published on RED User and elsewhere. The testing facility will be identified in the posted and published results of the testing. A great Los Angeles area production/post production company has donated their facility for the 2 days of testing - very cool, and very appreciated. The testing team members have yet to be told where the facility is located. Before they are told the location, they will be placed under a non-disclosure agreement. Please donít pester them for information. They will not be free to give you any info about the testing facility or its location.
More info will be released as we get closer to the testing dates. In advance of the testing, I'm having each team member submit their Wish List for parameters, setups, lenses, and accessories to test on the camera. Weíll accommodate as many of those suggestions as possible within the testing time constraints. Me and Evin will be approaching this testing the same as when we individually produce motion media projects Ė an organized testing schedule analogous to the shooting schedules used on the set or in the field. That way weíll have a good chance of getting through all the testing and analysis we have on the testing schedule. Testing team members will be asked to use all their varied skill sets, to be unbiased, analytical, and objective - while also paying close attention to aesthetics and artistry.
Nobody has asked me to organize the testing of RED #8. It was completely my own idea, and Iím donating my camera and time as I produce the testing sessions. As a purchaser of two RED One camera systems, Iím obviously curious about the hands-on results, strengths, and limitations of the system. Though Iím well qualified to test the camera myself, I feel that there is no better way to quickly answer my questions about the camera than to assemble a diverse and talented group of professionals, and then team test it. That way, the results should have a lot more dimension and depth than just myself testing out the camera. After deciding on a team testing of the camera system, the next logical thought that came to my mind, was this: Rather than horde the results and knowledge gained from the testing among the team alone, why not post it so that the rest of you who are hungry for real-world, hands-on feedback on RED One can share in the results. That was an easy decision for me. Anyone who has followed the development of RED One since it was first announced, should also know that I have continually stepped up to mentor, advise, and inform this board and others about the tech and business principles of the motion media industry, and specifically share what knowledge and insight I may have about RED and RED One. Itís been fun for me doing that and Iíve learned immensely from many of the rest of you. This testing is an extension of that symbiosis: Iím sharing this testing with you Ė and Iím sure youíll be sharing your ideas and results over the coming months and years ahead with me. Iíve been very fortunate to get an early reservation number so Iím spreading the benefits around this board to all of you. If many of you were in my position, I seriously think you would do the same thing.
Note: I'll be on location today shooting some television programming. Shortly after putting this thread up I have to head out for today's shooting. Later tonight I'll visit RED User and be happy to then answer any questions posted on this thread.