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???

One of the biggest differences I see is that it doesnt do checksum verification - only byte based comparisons. So once the red media is erased, you will have no way of ever re-verifying the r3d file again. Basically, if you plan on archiving at all, you should have a checksum to verify that the data is correct. It is also a requirement of most bonded shows that a checksum - from the source media - be generated.

edit: I forgot to add that we have a couple of nifty features on the horizon. Automated renders and a queue system are around the corner - currently in beta testing.
 
Hi Conrad !

One question: If I do the checksum verificationI see the process bar going to 100 percent and if it is finished I get no response message. Would it be please possible to get a popup window like when all the media is copied?

thx
rainer
 
Question for current users:

We are having issues with our MacBook Pro Kernel Panicking on us during the transfer of files in R3D Data Manager and I've narrowed the issue down to something in the chain of Sata devices. So, I was hoping to see if anyone who has been successfully using the software has used the Tempo SATA ExpressCard/34 from Sonnet without any issues and/or what SATA expresscards folks have used with success in conjunction with R3D Data Manager.

Any info would be great!
 
I just picked up a Sonnet Tempo card recently but have not tested yet with R3D Data Manager. I will be doing that soon though.
 
rainer said:
Hi Conrad !

One question: If I do the checksum verificationI see the process bar going to 100 percent and if it is finished I get no response message. Would it be please possible to get a popup window like when all the media is copied?

thx
rainer
Click to expand...

Ive mentioned before that this will be in a future version. It does alert you now if there is an error.
 
Conrad, please one more question....

when I do the checksum creation, then copy, and after that the checksum check, it does it with the camera disk again. The backup disks are in idle and doin nothing... should it not check the checksums from the cam drive with the backup drives???? confusing a little bit....

thx
rainer
 
Is there a way to copy select files and folders only?

For instance, I had a checksum error on 2 files. Seems like I should be able to go back and copy just those two files or folders but the app seems to limit me to the root R3D directory.

I also would like to see the destination paths be editable. I change the destination folder for every reel so I can give some real world names to the footage. So the whole preferences thing doesn't save me any time as I have to remove the path and add a new one by browsing to the new folder every time. Kinda annoying.

Also, when you get an error there should be a one click method to either recopy those files or take you to those files and folders so you can inspect them quickly to see if they are corrupt.

The whole checksum creation button is unclear to me. Do I have to that before I start the copy every time? I think that button should be eliminated and happen automatically when the Start Copy button is pushed if the checksum option is chosen.
 
ingramworks said:
Question for current users:

We are having issues with our MacBook Pro Kernel Panicking on us during the transfer of files in R3D Data Manager and I've narrowed the issue down to something in the chain of Sata devices. So, I was hoping to see if anyone who has been successfully using the software has used the Tempo SATA ExpressCard/34 from Sonnet without any issues and/or what SATA expresscards folks have used with success in conjunction with R3D Data Manager.

Any info would be great!
Click to expand...
I had kernel panics with that card using Leopard and sold it as a result. Had nothing to do with R3D Manager as I wasn't using it. Most eSATA ExpressCards have the same chipset and I tried another one (Rex RS30 or something) with same chipset with same results.

Haven't used eSATA cards since then and went back to FW800.

If anyone can recommend a card with a different chipset in it to those two it'd be appreciated....

HTH

Paul
 
rainer said:
Conrad, please one more question....

when I do the checksum creation, then copy, and after that the checksum check, it does it with the camera disk again. The backup disks are in idle and doin nothing... should it not check the checksums from the cam drive with the backup drives???? confusing a little bit....

thx
rainer
Click to expand...

I'm pretty sure it does that while you're copying. You don't need to check the checksums again after the copy.
 
rainer said:
Conrad, please one more question....

when I do the checksum creation, then copy, and after that the checksum check, it does it with the camera disk again. The backup disks are in idle and doin nothing... should it not check the checksums from the cam drive with the backup drives???? confusing a little bit....

thx
rainer
Click to expand...

I dont get why you are doing a checksum check again. As long as you have the option enabled, it will do it on each destination immediately after the copy has finished - namely from 50 to 100% done on each destination. In fact, once each destination says "checking checksums", you could remove/unmount the source red drive.
 
joelnet said:
Is there a way to copy select files and folders only?

For instance, I had a checksum error on 2 files. Seems like I should be able to go back and copy just those two files or folders but the app seems to limit me to the root R3D directory.
Click to expand...

You are thinking of it backwards. Instead, just delete the offending destinations that had copy/checksum errors. select "ignore all" in the "if RDC folder exists" option, and hit copy again. It will find the deleted folders and only copy those. Since you deleted the ones that had errors, it will effectively just re-copy those.

The whole checksum creation button is unclear to me. Do I have to that before I start the copy every time? I think that button should be eliminated and happen automatically when the Start Copy button is pushed if the checksum option is chosen.
Click to expand...

If the checksums are not being automatically done when the source is selected (i.e. BEFORE you even press the "start copy" button), then you are doing something wrong. The source checksums (ie. on the Red Drive or CF card) are done automatically when R3D Data Manager detects you selected a valid Red Drive. So while you are entering other info, its already creating the checksums.
 
I use a Sonnet Dual eSata Expresscard adapter and it works fine. Certainly no kernel panics!
Conrad,
Terrific program! An "estimated time remaining" countdown would be a welcome addition.
Cheers,
Harry
 
Photocon said:
You are thinking of it backwards. Instead, just delete the offending destinations that had copy/checksum errors. select "ignore all" in the "if RDC folder exists" option, and hit copy again.



If the checksums are not being automatically done when the source is selected (i.e. BEFORE you even press the "start copy" button), then you are doing something wrong.
Click to expand...

Ok, got the re-copy part. Thanks. But considering I've got a zillion years of computer experience and my first reaction was just to go select the 2 bad files...

The best solution would be to have the program flag files that were not copied properly and offer to show the destination files in the finder and offer a one click "copy these files again" option. I really don't want to have to do any thinking if I have a bad copy.

If checksums are automatic why is a create R3D checksums button right next to the select source dialogue? Sounds like it would be rarely used. If so, consider moving it to a menu item and call it recreate R3D Checksums. Right now it feels (to me anyway) like it is part of the process due the prominent placement of the button.
 
Hey, just an update to my earlier post about issues with the Sonnet Tempo ExpressCard. Following Photocon's post, we returned that crad and ordered the Rosewill eSATA ExpressCard (model RC605) and have tested it without any issues.

While I haven't used it on set yet, I tried multiple scenarios of how I may need to copy while on set with Mags loaded with lots of shots, a few shots; doing checksums, not doing them; verifying them and not all without any hiccups at all.

With our hardware (MacBookPro, 7200 RPM drive, Lexar FW800 CF Reader, Rosewill eSATA ExpressCard, dual 500GB G-Tech G-Drive Qs) my numbers are currently showing an average 1:2 copy rate on Mags that I do checksums on (4 mins of footage takes about 8 mins to copy) and a close 1:1 copy rate without checksums, although this has a variation of anywhere between 10 to 30 seconds.

I can't say this is 100% rock solid, but it is consistant with what I've been experiencing so far and well within a workable time. I also can't guarantee that the Rosewill will work for everyone, but it is working for us. Like Paul (visceralpsyche) our laptop had Leopard on it and I wouldn't be surprised if that was part of the issue.
 
It would be very useful in a future version to be able create and verify checksums after copying, when checksum was not switched on during copy. Often under the pressure of a shoot the time penalty for copying with checksums may be too much. I'd like to be able to point the app at a Red Drive and a copy folder at the end of the day and have it create and compare checksums. Obviously this only works if you haven't erased the Red Drive! I personally prefer not to erase drives until the end of the shoot, and do regular incremental backups.
 
Nick Shaw said:
It would be very useful in a future version to be able create and verify checksums after copying, when checksum was not switched on during copy. Often under the pressure of a shoot the time penalty for copying with checksums may be too much. I'd like to be able to point the app at a Red Drive and a copy folder at the end of the day and have it create and compare checksums. Obviously this only works if you haven't erased the Red Drive! I personally prefer not to erase drives until the end of the shoot, and do regular incremental backups.
Click to expand...

You can do that, in a way, right now.

You can disable checksums and then create them later using the "create R3D checksums" button.

You can disable checksum checking after copy, then select a destination RDM folder as the source and check the destination checksums then.

The only thing you cant do is have R3D Data Manager copy the md5sums.txt file to the RDC folders. It only does that during a copy process. So you would need to copy those to the destination directories manually.

In the future actually, there will be no penalty for the source checksum. That will be done automatically while the file is read.
 
Photocon said:
You can do that, in a way, right now.

You can disable checksums and then create them later using the "create R3D checksums" button.

You can disable checksum checking after copy, then select a destination RDM folder as the source and check the destination checksums then.

The only thing you cant do is have R3D Data Manager copy the md5sums.txt file to the RDC folders. It only does that during a copy process. So you would need to copy those to the destination directories manually.
Click to expand...

That's what I have been doing, but if I don't get a chance to create checksums until the end of the day there can be a lot of files to copy manually to different folders. I need to get more up to speed on writing shell scripts to do that kind of thing!

Photocon said:
In the future actually, there will be no penalty for the source checksum. That will be done automatically while the file is read.
Click to expand...

That will be extremely useful - always creating checksums at the earliest opportunity, but not verifying them until time allows, without the time taken to read the source file twice. I look forward to the update.
 
You must log in or register to reply here.
Back
Top