Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

AA Sync Warning!

Harry Clark

Well-known member
Joined
Dec 29, 2006
Messages
1,791
Reaction score
0
Points
36
Location
NYC
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
 
Scary.
I'm getting to the conclusion that only specialized apps for the red workflow will cut it.
Also I read there are universal red/P2/SxS/photo ingest applications in development but I don't know if/when they're out, and if they'll have the appropiate features (security, checksum verification, logging, multiple paths etc)
 
That's how we caught it. Of course.
Just seems like an odd thing that a program whose ONLY PURPOSE is to ensure a perfect copy fails to do so...
:)
Harry
 
Scary.
I'm getting to the conclusion that only specialized apps for the red workflow will cut it.
Also I read there are universal red/P2/SxS/photo ingest applications in development but I don't know if/when they're out, and if they'll have the appropiate features (security, checksum verification, logging, multiple paths etc)

The R3D Data Manager does all of that - security, checksum verification of all destinations, logging, and multiple destination paths. And it does it right now. The next version will add a source queue so you can setup multiple sources and it will process them one at a time. Future versions will also automate R3D downconverts.
 
Photocon, how are you advancing on doing the checksum + copy operations reading the media only once?

Also... would your app be usable for non-red contents, such as SxS, P2, RAW photos, etc? Just make the file handling generic and then maybe add the format-aware features as a toggle? It would be great as a universal ingester tool.
 
Photocon, how are you advancing on doing the checksum + copy operations reading the media only once?

Also... would your app be usable for non-red contents, such as SxS, P2, RAW photos, etc? Just make the file handling generic and then maybe add the format-aware features as a toggle? It would be great as a universal ingester tool.

Right now, the app is only for R3D data, not other data.

This next release will implement the queue system I discussed above. After that we will work on the copying via RAM. However, to use this feature you will need a mac with 4Gb of RAM.

Just as a further update, we are also working on a windows version right now, and hope to have that app out of testing within the month. And we have started working on automated QT downconverts, and should see that feature out within the month also.
 
Back
Top