Version 2.4 Release: April 2008

View the entire changelog here. You can also subscribe to our Update RSS feed. You can also try our trial version. For more info on the trial version, please fill out our contact form.

Version 2.4 has been confirmed to work with the current RED beta build 16. Soon we will be introducing our queue system for red media, and a windows version.

Version 2.2 introduces support for the new directory structure introduced in RED build 15. This version now supports the old and new directory structures, even in a mixed environment. So your data is always copied, now matter which build version you shot on.

With the 2.0 series of the R3D Data Manager comes a lot of improvements, including a complete overhaul of the underlying source code. The improvements make the system 20% faster than before, and provide more options and error checking to make sure your data copied over correctly. In addition, this version introduces a tracking and audit feature, recording scene, RED MEDIA and other info to project files.

R3D Data Manager Planned Features

Future versions of R3D Data Manager will include:

Copy Multiple Sources Sequentially
There may be a way to setup multiple sources and then have the R3D Data Manager simply go source by source and copy them to the destination. It would add new RED Media to the queue and transfer them when previous copy operations have finished.

Work on R3D Files in Memory
There may be a way to work on each R3D file in the system RAM, thereby reducing the amount of time it takes to transfer a file by a signifigant amount. Instead of 2 reads from the source RED Media, there would only be one read. In addition, we could write to the destinations at wire speed, not limited by latency or bus speeds from the RED Media.

RedLine Integration
We plan to include support for creating renders of R3D footage to Quicktime, using spare processor cycles when you are not transferring. This will enable you to make offline renders for editing and distribution right from your copy station, while it is working. Render to ProRes, DVCPROHD or any other supported format, and save it to any destination.

Rename Quicktimes To Include More Useful Info
With this tool, you can copy the camera-generated quicktime moves to new files that include more useful information, such as including slate number and Take. We are currently proposing a file be named: A001_C001_010108_S039_T001_P.mov for example, with S corresponding the Scene/slate number and T corresponding to the Take number. This will make it far easier to find shots by file names. You can input this data via a new window with an easy to use interface.

Project Management
Create and store project info for later use, and browse project info, including transferred files and destinations.

Final Cut Pro Integration
Create Final Cut Pro XML files for easy import into final cut.

Ideas That May Become Features

We are still developing these ideas and working on if they are viable. As such, these may or may not make it into a final release version in the future.

Quicktime Renders using LOOK Files
There may be a way to import LOOK files generated in RedAlert or RedCine to be imported and used for Quicktime Renders.

Your Features
Suggest some more features, and they may make it into the next version of R3D Data Manager.