Jason Goodman
Well-known member
We were recently contacted by our good friend Charlie Parra at Denecke about some problems one of his customers was having shooting 3D with two EPICs and an SB-T. After trying sync boxes from all manufacturers, it was determined that the problem originated elsewhere, however the questions prompted us to conduct a comprehensive test of "3D sync" for the current (as of yesterday) build of EPIC.
True "3D sync" requires genlock of course, but also shutter phase sync. In addition to the camera's internal clocks being synchronized, shutter timing must also be perfectly synchronized or very noticeable visual artifacts will be present in your 3D imagery.
Tests we conducted in 2009, prior to shooting Julia X and published on REDUSER by Pedro Guimaraes, indicated that RED ONE (and RED ONE MX) never fully achieved perfect shutter phase sync. RED ONE builds later than 21 did allow cameras to be genlocked and 3D worked well up to 120fps at 2K. Many 3D films have been successfully shot with RED ONE. The small shutter phase error was generally not considered a problem and in most cases was not noticeable.
The good news is, all builds of EPIC I have seen including beta builds we used last year on The Amazing Spider-Man have exhibited absolutely dead perfect shutter phase sync. The ASM crew was instructed by RED as to which frame rates, resolutions and time bases to use in 3D for that film, and to my knowledge we did not exceed 72fps in 3D.
As always, with newer builds come new capabilities.
Last week, prompted by Charlie's inquiry, we tested as many combinations of resolution, frame rate and time base as we could think of. We have assembled the most comprehensive list of working 3D modes for the EPIC and I've posted it here for reference.
One issue of particular interest, we noticed instances where the EPIC would indicate GEN, TC and SYNC, but in fact, shutter phase was off. We did the classic test of shooting an LED timecode slate with the shutter set to 1/1000th of a second so we could see partial redraw of the LED numbers. If the numbers are not drawn exactly the same in both eyes, shutter phase is off. Here's the chart:
https://docs.google.com/spreadsheet/pub?key=0AuJAHpbX6ekpdEt4d3BOcUk1ZDFnYlNROVhLdklKalE&output=html
True "3D sync" requires genlock of course, but also shutter phase sync. In addition to the camera's internal clocks being synchronized, shutter timing must also be perfectly synchronized or very noticeable visual artifacts will be present in your 3D imagery.
Tests we conducted in 2009, prior to shooting Julia X and published on REDUSER by Pedro Guimaraes, indicated that RED ONE (and RED ONE MX) never fully achieved perfect shutter phase sync. RED ONE builds later than 21 did allow cameras to be genlocked and 3D worked well up to 120fps at 2K. Many 3D films have been successfully shot with RED ONE. The small shutter phase error was generally not considered a problem and in most cases was not noticeable.
The good news is, all builds of EPIC I have seen including beta builds we used last year on The Amazing Spider-Man have exhibited absolutely dead perfect shutter phase sync. The ASM crew was instructed by RED as to which frame rates, resolutions and time bases to use in 3D for that film, and to my knowledge we did not exceed 72fps in 3D.
As always, with newer builds come new capabilities.
Last week, prompted by Charlie's inquiry, we tested as many combinations of resolution, frame rate and time base as we could think of. We have assembled the most comprehensive list of working 3D modes for the EPIC and I've posted it here for reference.
One issue of particular interest, we noticed instances where the EPIC would indicate GEN, TC and SYNC, but in fact, shutter phase was off. We did the classic test of shooting an LED timecode slate with the shutter set to 1/1000th of a second so we could see partial redraw of the LED numbers. If the numbers are not drawn exactly the same in both eyes, shutter phase is off. Here's the chart:
https://docs.google.com/spreadsheet/pub?key=0AuJAHpbX6ekpdEt4d3BOcUk1ZDFnYlNROVhLdklKalE&output=html