R3D Data Manager is an application designed to help you better manage your data workflow. With the terabytes of data that you will create with your RED system, R3D Data Manager helps to step in, making sure copies of each R3D file go to the right place, and accurately.

R3D Data Manager helps to ensure that the data you read from your RED MEDIA is the same data you have throughout your post process. With the terabytes of information you will create, its very easy for a digital zero or one to get misplaced, not to mention hard drive failures and overwrites. Any one of these issues can lead to a failure of your R3D files. We overcome this by creating checksums right off the card and passing those through the copy process. If one byte of data is missing you will know about it.

R3D Data Manager now features a batch quicktime downconversion module. Now you can convert the R3D files into Quicktime files, ready for import and editing in most major editorial systems. These downconverts can be made with a default look, or individual looks for each file. In addition you can create timecode burn-ins, masking for the shooting and/or framing aspect ratio, change render and filter settings and much more, all from within the module. Simply give the module the location of your R3D files and setup a destination, and click render! You can even copy the rendered quicktime to up to 4 different destinations, meaning you can have 5 copies of your quicktime downconverts with one click!

By gathering more information during the first on-set copy process, we can help to alleviate the search for missing shots. You can enter info about the shots before you copy them, and R3D Data Manager will record those to simple text files along with all copys of the footage. From there, editors can help search for missing shots, or for an audit log of what was transferred where.

No matter what platform you currently use to backup and archive your R3D files with, the checksums created by R3D Data Manager are platform independent. So you can use the Mac version on set, the Windows version in editorial and know that the checksums will still match. In fact, because these checksum types are industry standards, you can be confident that you can use them years down the road.