What causes this? I am guessing overexposure, I saw that was mentioned on another thread but I just want to confirm.
I was shooting the setting sun, it was behind a bunch of houses. Not serious footage, just testing the camera.
|
|
What causes this? I am guessing overexposure, I saw that was mentioned on another thread but I just want to confirm.
I was shooting the setting sun, it was behind a bunch of houses. Not serious footage, just testing the camera.
What build? Older builds would have codec errors with significant overexposure, but that problem was solved many builds ago...
Just got the camera a couple of days ago. Build 12.
Jim,
Build 12 is the most recent ..so you may need to download the firmware from the NET
Please email this in to tech support so we can get to the bottom of it.
Graeme
Did the problem happen during recording or on playback?
Update - For whatever reason, it works now.
Camera was powered down for an hour. And before it went from outside 50 degrees to inside 71 degrees.
That is the only difference I can think of between the two times I played back that card.
It's probably worthwhile to help them trace the bug by narrowing down the circumstances under which the problem occurred:
Is there something visible in the R3D file around the time frame that the playback mechanism triggered the codec error? On footage I shot using build 10 I had a similar problem, which I attributed at the time to cold weather, in the footage you can see sections of the frame where it appears that compression couldn't complete. In retrospect, I was also dealing with snow on the ground, which caused some areas of overexposure. This is what it looked like:
Attachment 2385
My assumption was that this was a cold weather thing and fixed in the new bodies. But maybe something else has been slipping through the cracks. One other question, were you using False color, around or during the time of playback?
| « Previous Thread | Next Thread » |