Welcome to our community

Be a part of something great, join today!

Log in
  • 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???

Photocon said:
The speed is really determined by how fast you can read/write, not the program per-se.
Click to expand...

Creating the checksums during the read/transfer would increase the speed significantly - by about a third. is this still a ways off?
 
Trevor Meier said:
Creating the checksums during the read/transfer would increase the speed significantly - by about a third. is this still a ways off?
Click to expand...

Semantics perhaps, but it does not increase the speed one iota. It just decreases the time by doing two things at once.

And it is a ways off still mostly because RAM is not a friendly place for data to be.
 
Photocon said:
Semantics perhaps, but it does not increase the speed one iota. It just decreases the time by doing two things at once.
Click to expand...

Surely it doesn't just do two things at one, it does one very time consuming thing (ie reading the source file) once instead of twice. Or am I misunderstanding?
 
Nick Shaw said:
Surely it doesn't just do two things at one, it does one very time consuming thing (ie reading the source file) once instead of twice. Or am I misunderstanding?
Click to expand...

Im not going to divulge the exact innards of how it works, especially since it is not released yet. However, suffice to say, it IS (or will be?) doing two things at once.
 
Wouldn't creating the checksums while copying remove the ability to detect random, silent, read errors? By doing a checksum and then copying the data, you are not only verifying that it was written correctly, but also much more certain that it was also read correctly. Granted, we always scrub through all the clips, and random, silent, read errors are few and far between, it's still something to think about.
 
Sorry to post off topic hear but I have a question. I want to be able to copy to 2 separate destination directories simultaneously. But when I set R3D DMNG to do so I get checksum errors at the end of the process on almost all the clips. My setup is:
2 X HDD -> express34 to 2XFW800 -> Macbookpro <- Red drive to FW800

Copying to the 2 HDD seams to always result in a checksum error at the end of the copying process. This also happens when the drives are daisy chained to each other.

Is there a way to copy to 2 separate drives at the same time?
Thanks.
 
R3D Data Manager usually exposes some sort of other unreliable system in your chain. Something is unreliable, and its causing checksum errors. I would advise to try different things to try and isolate the issue. Most issues happen with incorrectly made expresscards and/or drivers.

To be clear, R3D Data Manager is expressly designed to copy to 1, 2, 3 or 4 drives at the same time. Copying to 2 drives is *NOT* the issue.
 
Hi Conrad I know that copying to 2 drives is not the issue and there for am asking whether you can help me make it work on my system.
Copying to one of the 2 connected via the express card drives at a time works and the express card adapter seams to work fine with other software as well. Copy to 2 drives daisy chained to each other and connected via the native FW800 port doesn't work. Nor does copying to 2 drives when connected to the express card daisy chained or separately to the 2 FW800 ports on the adapter.
The Macbookpro has 2GB RAM, 2.33GHZ core 2 duo and OS X 10.4.11, any helpful suggestions would be great.
Thanks.
 
Just because your drives work with other software doesnt mean its up for the task of handling red footage. Obviously there is something in the chain that is not reading or writing the footage correctly. The ones and zeros are getting misplaced. That alone, for me, would be reason to suspect every part of the chain.

You still need to investigate the drives themselves, the cables you are using, even the computer you are using. Any one of them could be responsible for this. Have you checked the logs?
 
The drives are bran new Taurus raid II set to raid 1, the cables are new FW800 and the computer has worked flawlessly to date. I haven't read through the logs so will try a copy to 2 drives again just to get a log and read it. Will also try it with un raided drives may well have an effect.
 
I would like to praise the latest release of R3D Data manger V.3. I really like the new lay out and the queue option for source directories is great. Very happy with the new version thanks Conrad.

P.S
I will send the next log I get from a shoot with Red drives and 2 FW800 HDD as it seams as if the problem I was referring to was due to a combination of a dual FW800 to express 34 adapter and R3D DMNG.
 
are there any other programs out there that can assure me im making good copies from a red drive to my RAID or is r3ddatamanager the only one?

How long does it normally take to make copies from a nearly full red drive?

its been on zero percent for what seems like an eternity.
 
Well - a nearly full hard drive indicates bad data management, to be honest.

To make an accurate copy you need to read the file 3 times. The first reads the file to make an initial checksum, the second does the copy, the third does the verification (reading from the destination). Because of this you can expect a full Red Drive to take a day, because firewire 800 is only so fast. Hopefully you have setup your system for speed, and only are using the firewire 800 to the Red Drive, and are using SATA to the other drives.

As all your eggs right now are in one basket with all your footage on one drive. If a hard drive fails, you are out of luck. Im mentioning this because you really need to ensure that you are downloading more often. When you do, it wont take as long either.
 
Thanks for the quick response dude.

It was impossible to download the data that often on this job. A three camera shoot of an all day music festival, each camera had two red drives, every two and a half hours we would each switch to the next drive. There were five minute (at the most) breaks between each act. There was no other option with our budget (which was zero)
 
You must log in or register to reply here.
Back
Top