Harry Clark
Well-known member
Just FYI...
On the job today with my Red One. My DAM, following my advice, used AASync to copy the data from my drives to the client/ editor/ backup drives (rather than just drag-and-drop in OSX Finder)
Because he's a thorough guy, he checks each and every shot folder on the destination drive, plays back the proxies, etc. At the end of the day, the last card did not successfully copy. No warning from AASync. Just Pete's careful checking. Out of 5 shots, 3 did not have the .r3d files, just useless proxies. However, the files were fine on the card.
After some quick troubleshooting we discovered that the destination drive was nearly full and that, rather than warn us (as the Finder would have done), AASync simply chose some random large files to omit from the transfer.
Nothing in the AASync log file. No warning.
Very disturbing.
EVERYONE BE CAREFUL OUT THERE.
Cheers,
Harry
On the job today with my Red One. My DAM, following my advice, used AASync to copy the data from my drives to the client/ editor/ backup drives (rather than just drag-and-drop in OSX Finder)
Because he's a thorough guy, he checks each and every shot folder on the destination drive, plays back the proxies, etc. At the end of the day, the last card did not successfully copy. No warning from AASync. Just Pete's careful checking. Out of 5 shots, 3 did not have the .r3d files, just useless proxies. However, the files were fine on the card.
After some quick troubleshooting we discovered that the destination drive was nearly full and that, rather than warn us (as the Finder would have done), AASync simply chose some random large files to omit from the transfer.
Nothing in the AASync log file. No warning.
Very disturbing.
EVERYONE BE CAREFUL OUT THERE.
Cheers,
Harry