Has anyone here seen this noise/corruption before?
happened on set today. P65 digi back into Mac Pro 2 x 3.2 GHz w. 32GB RAM on a 250 SSHD. 10.6.8
Capture 1 v. 6.6.2
below is a zoom at 100%. I can't show more because these files are unreleased. Any suggestions? Just started happening out of the blue, 3rd shot into the day. Restarting the back would make it go away for a few frames then it would return. Switched FireWire cables. Did not seem to appear at 50 or 100 ISO, but only at 200 which is where we needed to shoot. However, only fired off a couple test frames at 50 and 100 ISO.
Restarted the computer. Prayed and smoked a cigarette and problem went away.
Faulty back or FireWire port? Divine intervention?
http://imgur.com/hcAo9.jpg
Capture 1 v. 6.6.2
below is a zoom at 100%. I can't show more because these files are unreleased. Any suggestions? Just started happening out of the blue, 3rd shot into the day. Restarting the back would make it go away for a few frames then it would return. Switched FireWire cables. Did not seem to appear at 50 or 100 ISO, but only at 200 which is where we needed to shoot. However, only fired off a couple test frames at 50 and 100 ISO.
Restarted the computer. Prayed and smoked a cigarette and problem went away.
Faulty back or FireWire port? Divine intervention?
http://imgur.com/hcAo9.jpg
0
-
If I had to guess I would say it was "dirty power" where a fluctuation in power from the computer causes interference in the file transfer. ISO 200 could have just been the frequency of power demand via the firewire cable that caused the conflict. Hard to say without a RAW file but I would suggest in the future, should you come across such an error, you untether the back and take an identical test shot to CF card using battery power to rule out the tethering process. 0 -
smart idea. wish i had thought of it in the heat of the moment! 0
Post ist für Kommentare geschlossen.
Kommentare
2 Kommentare