Truckee Lynch
Forum Replies Created
-
We have not run into the problem for a while so we haven’t invested any more resources to tracking it down. At one point we were able to recreate the issue by saving a pro-res file after it was opened in quicktime, even though nothing had been changed in the file. Aside from removing quicktime from your workflow(if it is indeed their.) I haven’t got many other suggestions than that unfortunately.
-
Your situation appears to match ours exactly.
We didn’t change anything with XSAN.
What do you use for metadata tagging or logging? Does anything scan you San and assign metadata?
Apparently this last time we think the culprit was actually Cinema Tools. All the files that got corrupted had their metadata read and rewritten by Cinema Tools.
We also found that the corruption consistently happens between the first and second minute of footage, we’re assuming it’s the same block of bits getting corrupted and how compressed the footage leading up to the bit rot determines how far into the file you see it.
If we learn anything more, I will reply to this thread. Please do the same! We would love to know we solved this problem once and for all.
If you want to reach me directly my email address it truckee (at) vafitness (dot) com
-
Not really. We stopped using Adobe Bridge and the problem went nearly completely away. However at roughly the same time we also changed our workflow in a few other ways.
A couple of weeks ago we found that it began happening again, although not on the same scale. Perhaps 3 files not 50. This time, something else, CATDV or Compressor, had recently touched the files.
Our best guess is that the header data is written somewhere near the image data and that some poorly written operations occasionally flip bits in the image data. Either that or some .mov files are written poorly making them susceptible to this kind of corruption.
Do you have a similar problem?
-
We’re pretty sure this isn’t the issue because the files are fine when they are rendered, and display the same way (with the gnarly little rectangles) across multiple computers. Leading us to believe that no one graphics card could be the issue. At some point when the file is just sitting on the SAN something(or someone I suppose) corrupts it. Cosmic rays? Goblins? Adobe Bridge? All three?
-Truckee