Sean Rawls
Well-known member
- Joined
- Apr 24, 2007
- Messages
- 224
- Reaction score
- 0
- Points
- 0
- Location
- Portland, OR
- Website
- www.seanrawls.com
Hey, just got done grading some stills from an informal test we ran for an up coming short film in the beautiful Portland, OR. Our test was basically to iron out the on-set work flow, so the images aren't brilliant (mostly just really dorky).
We shot in both 2K and 4K using available light. Used Build 13. ASA 320. We used a set of Zeiss Superspeed primes. These specific stills were taken with the 85mm. Decided to try shooting 2K through 35mm lenses to use the "best" part of the glass. Sort of like shooting with full-frame lenses on a DX sensor. Not sure if others have tried this, but it might have some advantages.
Overall I am impressed with this camera and can't wait to see the images it will produce in the next few years. Shooting RAW with 35mm glass really feels like cheating. Our "test" didn't explore the DR issues and it seems highlight handling will be a shortcoming of digital sensors for the foreseeable future (curious to see what build 16 will change).
Ok now the BAD: during our test the QT proxies generated from 4k footage had some very strange interference. Basically the bottom half of the frame is covered in weird digital interference (see attached example). The .R3D files of the same footage were fine and worked in Redcine without problem. Interestingly, the proxies of 2K footage looked fine. I'm not sure if this is an in-camera problem or something to do with all the QT compatibility issues. I'm running QT 7.3.1 on a Macbook Pro. I did however, upgrade to QT 7.4 before I saw the compatibility warning. I then had to downgrade QT using the program Pacifist. Have people seen this proxy issue before? This is a pretty big problem for on set footage checks.
We shot in both 2K and 4K using available light. Used Build 13. ASA 320. We used a set of Zeiss Superspeed primes. These specific stills were taken with the 85mm. Decided to try shooting 2K through 35mm lenses to use the "best" part of the glass. Sort of like shooting with full-frame lenses on a DX sensor. Not sure if others have tried this, but it might have some advantages.
Overall I am impressed with this camera and can't wait to see the images it will produce in the next few years. Shooting RAW with 35mm glass really feels like cheating. Our "test" didn't explore the DR issues and it seems highlight handling will be a shortcoming of digital sensors for the foreseeable future (curious to see what build 16 will change).
Ok now the BAD: during our test the QT proxies generated from 4k footage had some very strange interference. Basically the bottom half of the frame is covered in weird digital interference (see attached example). The .R3D files of the same footage were fine and worked in Redcine without problem. Interestingly, the proxies of 2K footage looked fine. I'm not sure if this is an in-camera problem or something to do with all the QT compatibility issues. I'm running QT 7.3.1 on a Macbook Pro. I did however, upgrade to QT 7.4 before I saw the compatibility warning. I then had to downgrade QT using the program Pacifist. Have people seen this proxy issue before? This is a pretty big problem for on set footage checks.
