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 :)

R3D data manager???

I purchased it this morning but haven't gotten a reply with the download information. I'll let you know how it looks.

-Chris
 
We have had several beta-testers, including a couple of prominent members of the pro video coalition. We have received feedback from them and incorporated it into our product.

In addition, we have several features that I think will make this a valuable tool, including quicktime renderings and FCP importing with scene/take info. Those will hopefully come out in a few weeks, and will be a free upgrade to all users.
 
Can you use multiple CF reader in firewire daisy-chain with your software. (http://www.lexar.com/readers/pro_reader.html)

The only requirement is a mounted file system. As long as your computer can see each card, so too can our program.

If you are wondering if you can do 2 copy operations at once, I think you'll find its not really feasible. Since you are pushing so much data around, your bottleneck is always the pipe you are using - firewire, eSATA, etc. So making 2 copy operations at once will take about 2.1 times longer than doing a single card separately. (The extra .1 is for bus overhead) For example, if it takes you 5 minutes to offload one CF card one at a time, it would take you 11 minutes to offload two cards at the same time. So its actually faster to go one at a time.

However, if you are doing card to card transfers, then there is no issue.
 
what is the difference to aasync...aasync is free

Aasync uses a sftp overhead, even with local copies. So it adds about 10% to the workload of the copy process, and would take about 10% longer.

In addition, aasync doesnt provide any sort of accountability or audit trail. Ive already run into a situation where a bond company required this from a feature I shot.

In addition, aasync doesnt provide any method for determining if a shot has already been copied or not. It simply copies files, which means that if the RED happens to create a take with the exact same file name, it will overwrite or discard your data - meaning you lost a take! And yes, I have already had this situation occur with the red, where it mistakenly went back a roll number, and there were matching filenames with different shots. R3D Data Manager will create a new folder automatically by default, unless you select a different option.

And then theres the future upgrades. We are already working on version 3, which will include quicktime rendering and scene/take info for import into FCP. In fact, attached is a screen shot of the quicktime renders window, in its current incarnation.

8155_1205989414.jpg


And these future upgrades are free for all users. So while aasync may be a good utility for remote copies, Id rather have something RED specific that can handle the finicky nature of our business.
 
We have had several beta-testers, including a couple of prominent members of the pro video coalition. We have received feedback from them and incorporated it into our product.

In addition, we have several features that I think will make this a valuable tool, including quicktime renderings and FCP importing with scene/take info. Those will hopefully come out in a few weeks, and will be a free upgrade to all users.

One of those features is that you donate $5 to help preserve forests!!! Amazing. I love you guys! We need every company and group doing this! Thank you.
 
However, if you are doing card to card transfers, then there is no issue.

Exactly, its for "batch" transfers...

In the "color space" section, do you think in the future we could put the .LOOK file create in the Redone (or Redcine) ?

How long does it take to process 4K R3D to ProRes 422 HQ on a 2.5 GHz Macbook pro in your software for exemple ?


thanks
 
I've been using Rsync on OS X. It's a good option for the copy, but does lack and more advanced features.

Any plans for a Windows version Photocon?

As of right now, we are feeling the waters for windows support. One of the big issues is that there isnt very good red support for windows, for some of the more advanced features - such as quicktime renderings. RedCine is only supported for mac right now, so there wouldnt be a way to run this on windows yet.

So the short answer is that we may do a more 'dumbed down' version for windows, that wouldnt have those additional features until its supported by the big guy.
 
Exactly, its for "batch" transfers...

I dont mean to get picky here, but a batch transfer wouldnt work, and would have the same limitations as being slower than if you transferred one at a time.

Right now, the software is setup to handle one source (Red CF card, Red Drive, or a previously copied R3D folder on any medium) to one or more destinations. I really feel that multiple sources at once would be slower and not worth the time.

However, it does bring up a great idea - multiple sources sequentially. For example, mount 3 CF cards, then copy card 1, then card 2, then card 3. Ill look into that.

In the "color space" section, do you think in the future we could put the .LOOK file create in the Redone (or Redcine) ?

Thats another good idea. Lets see how this all plays out in the future. Ive heard of RED encrypting certain items in the latest builds, so if they encrypt this look file also it maybe difficult to incorporate the look file into this software.

How long does it take to process 4K R3D to ProRes 422 HQ on a 2.5 GHz Macbook pro in your software for exemple ?

Still working on the exact code, but you can expect similiar results as to what redline and redcine process. We are using red's official tools to do this, to maintain compatibility with R3D file structure changes and future upgrades.
 
We've been using the Data Manager during tests for a feature - I'll put updates here once we're actually shooting.
We are running on Build 15 release version.

So far, we have made a few suggestions and they have been incorporated into the program within a day or two - the response has been fantastic.
My concern is of how much use the "Project Information" files are. These are the text files that hold whatever info you have about scene, roll/reel #, cf #, etc.
These currently live with each CF cards' folder.
Personally, I believe that if this data could all be written into 1 file per day, it would make searching through it much easier if you are trying to find clips from a specific card, or scene.
Also, these files need unique names - no use to me having 100 files named Project Information.txt.

Having said all that, the program is simple to use, and is speeding up my on-set process. I haven't had any issues with the copying process yet.

Brie Walsh
Data Wrangler
 
I installed R3Ddatamanager. That you can start mutiple copy processes saves your time that you don't have to wait till the first is ready and start the second. To generate checksums is also nice for verifying. But I don't know if I'm doin something wrong with this checksum feature, but thinking the software it self is not compairing the checksums... seems at the first look....
 
Great program... love it

When do you think that the render feature will be available? I am especially intrested in creating QT proxies from REDline with certain color corrections. DO you think this will be available in datamanager
Marcus Vasques Osorio
 
My concern is of how much use the "Project Information" files are. These are the text files that hold whatever info you have about scene, roll/reel #, cf #, etc.
These currently live with each CF cards' folder.
Personally, I believe that if this data could all be written into 1 file per day, it would make searching through it much easier if you are trying to find clips from a specific card, or scene.
Also, these files need unique names - no use to me having 100 files named Project Information.txt.

The ProjectInformation.txt file is placed in the directory root for each destination. So if you just use the same destination, the ProjectInformation.txt file will be appended with each copy process. Then you would only have one ProjectInformation.txt file (one per destination at least).

Thanks for the kind remarks.
 
I installed R3Ddatamanager. That you can start mutiple copy processes saves your time that you don't have to wait till the first is ready and start the second. To generate checksums is also nice for verifying. But I don't know if I'm doin something wrong with this checksum feature, but thinking the software it self is not compairing the checksums... seems at the first look....

The checksums are absolutely checked at the end of each copy process at each destination, to make sure they match the source. This is, of course, as long as you have the option "check copied checksums" enabled.

You can see that during the copy process after it get to 50% done, it will say "Checking checksums in ..." for each destination.

In addition, you will find files "md5sums-*.txt", where the * is a unix time stamp, in addition to the "md5sums.txt" file. Each of those unix time stamped files contains the md5 sums from after a copy process. So if you copy a RDM directory 3 times, you will have 4 text files - the "md5sums.txt" and a "md5sums-*.txt" file for each copy process.

So as long as you have "Check copied checksums" enabled, all the above will happen on each copy process.

Of course, at any time you can check the checksum of any RDM folder, by selecting the containing folder as the source (as if you were to copy from it) and clicking on "Check R3D Checksums".
 
Great program... love it

When do you think that the render feature will be available? I am especially intrested in creating QT proxies from REDline with certain color corrections. DO you think this will be available in datamanager
Marcus Vasques Osorio

Thanks for the comments.

We are working on copying to/from ram for each RDM folder, which should speed up data transfers by about 30%. In addition, we are working on a way to create a queue - for those of you using cards - so you can load up many CF cards and have the program transfer them one after the other.

Then we will work with the quicktime renders. Right now we have the GUI laid out, and have completed some of the redline test renders. However, theres a lot of work to be done there still, so its a little bit off in the future. We will get it out.

Thanks.
 
Back
Top