-
Major source media damage during print to video…
While outputting an SD Prores 422 project this afternoon, audio slipped during playback so we stopped down and we restarted our system. Upon restart 90 % of the media in the project was corrupted. Not just missing media, but the physical quicktime files have been corrupted, including all render files, capture scratch and even after effects outputs files. We have transferred the files to multiple computers, tried exporting, everything you can imagine. The corruption stays with the file whereever it goes. The source files are of various codecs from prores to animation to avid meredian. I’ve looked at many posts that completely eliminate the possiblility of fcp causing damage to a source file. I would agree based on my knowlegde base, but I have a project that appears on the surface to dispute that. We can recapture all of the affected media, but that is not the point.
I’m just completely lost as to how it could happen. All of the affected media is on a RAID 5 Sata array. No other media on the drive was affected besides the media that was in the timeline. I’ve run disk warrior on the array with no success. The commonality of the damaged files in FCP. Am I missing something obvious here? And to define corruption, the image have green bars that glitch in and out of the picture and audio comes and goes every couple of seconds. This corruption exists everywhere the files go Mac or PC. Here are the system specs…
FCP 6.0.4
OSX 10.5.4
2X 2.8 Ghz Quad Core
8 GB Ram
Sonnet 6TB Fusion R800RAID SystemThanks in advance for your thoughts.
Stephen
-
8 Replies
-
How full was the drive?
-
Have you opened the ATTO Config Utility to see the state of your array?
Sounds like your hard drives are in the state of failing or failed.
Have you called Sonnet?
-
The array has 3.8 Gigs free.
-
There’s your culprit. You must maintain 10% free space on a drive for proper operation.
Otherwise, nasty IO errors can result, as you’ve encountered.
-
Sorry, I’m braindead tonight. That should have been 3.8 TerraBytes free. The array is about 80% empty.
-
OK. Did you open the ATTO Configuration tool and look at the status of the Raid?
Jeremy
-
The atto util shows the array in good health with all drives functioning. I’ll still give Sonnet a call to see if they have seen issues like this. Do you know if there is any considerable difference in storage activity between the print to tape process as opposed to scrubbing and watching video directly out of the timeline? We had been working through final tweaks with the producer for hours through direct timeline viewing and the problem only arose after our first attempt to print to tape. Not sure if this has an bearing on the strain put on the HD array. That being said, the content was SD encoded at Prores HQ. The Sonnet array should eat that for breakfast as far as throughput is concerned.
-
[Stephen Fink] “Do you know if there is any considerable difference in storage activity between the print to tape process as opposed to scrubbing and watching video directly out of the timeline?”
Nothing considerable that i know of, but I don’t know all the ins and outs of it.
[Stephen Fink] “That being said, the content was SD encoded at Prores HQ. The Sonnet array should eat that for breakfast as far as throughput is concerned.”
Yes. I wouldn’t think it’s something with the codec, more about something went wrong on the Raid or raid card. Any power surges or anything weird about your setup?
Reply to this Discussion! Login or Sign Up