Copy Entire Contents Of Mag To Hd

[dino g]

News Flash:

I know many of you just copy the folders containing the r3d files + the proxies which the camera makes onto a hard drive to extract/ingest your/clients footage.

DO NOT CONTINUE TO DO THIS

new procedure, and you will thank me for this later...

create a folder on your hard drive called MAG<#>, i.e. MAG1, MAG2, MAG3....or what ever you want to call it to designate a specific CF Card.

put the entire contents of each mag <CF CARD> into that folder as the copy of the footage.

those 3 other files the camera makes will come in handy one day real soon.

thank you for reading this.

 

[Mike Prevette]

I have the "option" key on my camera laptop taped green, and big letters P-touched onto the laptop that explain how to copy entire volumes. This really should be the ONLY WAY of doing this. I can't tell you how many calls I get from people that fucked up a P2 volume by not copying the whole thing. I would assume one the red it would be even more important.

 

[Mark L. Pederson]

News Flash:

I know many of you just copy the folders containing the r3d files + the proxies which the camera makes onto a hard drive to extract/ingest your/clients footage.

DO NOT CONTINUE TO DO THIS

new procedure, and you will thank me for this later...

create a folder on your hard drive called MAG<#>, i.e. MAG1, MAG2, MAG3....or what ever you want to call it to designate a specific CF Card.

put the entire contents of each mag <CF CARD> into that folder as the copy of the footage.

those 3 other files the camera makes will come in handy one day real soon.

thank you for reading this.

I (and others) have requested that the camera make a root folder on the mag at format (REEL_A001 or MAG_A001, etc.) for this, and a few other reasons. And PLEASE don't use finder to copy - use a sync app with a checksum verification.

 

[I Bloom]

I (and others) have requested that the camera make a root folder on the mag at format (REEL_A001 or MAG_A001, etc.) for this, and a few other reasons. And PLEASE don't use finder to copy - use a sync app with a checksum verification.

Which sync app are you using?

 

[donatello b]

i've been testing a Nexto & Hyperdrive (space)units with 160gig 5400 rpm laptop drives in each ... with both units powered by internal batt & using a extreme III 2 gig card .. 1 gig of data ( 252 files) .. the nexto transfers in 1:23 ... the hyperdrive in 2:02 ....
nexto takes 1:19 to full verify for a total time of 3:42 to copy & verify... hyperdrive 2:34 for a total time of 4:56 to copy & full verify ....
i have used them with 8gig RED cards but didn't time the transfers - the larger the files the faster the transfer ( so two 1 gig files will transfer a little faster then 70 files ( that equal 2 gig) ...

basically the difference :
Nexto is a 2 step process to copy & verify .. you 1st copy the card - then pull out the CF card .. you then put it back in and it will verify ....
the hyperdrive is 1 step - you set it up before hand to copy & verify .. you put the card in and it will copy a file & then verify it - copy a file -verify etc ..
on both units you have the choice to either full verify or only verify the 1st 128k of each each file ( the hyper also gives choice to random verfiy ) ...
the nexto only accepts CF cards .. hyperspace takes many different memory cards

both units had to be returned when i received them .. nexto because it wouldn't charge the internal batt .. hyper because the verify button didn't work .. no problems returning the units .. both replacements work ...

http://www.nextodi.co.uk/prod_nd2525.html
http://www.hypershop.com/shop/index.php

 

[Mark L. Pederson]

Which sync app are you using?

trade secret for the moment. what do you like? DOUBLE checksum pass is the move -
We just tracked an issue to a RAID 1 enclosure - we are abandoning that method for two individual copies with checksum to separate drives.

 

[I Bloom]

trade secret for the moment. what do you like? DOUBLE checksum pass is the move -
We just tracked an issue to a RAID 1 enclosure - we are abandoning that method for two individual copies with checksum to separate drives.

Interesting. Think its the specific enclosure or a general issue.

Meanwhile here's a little checksum wrapper, you might use for direct comparison of R3D files on a Mac.
http://www.macupdate.com/info.php/id/23168

If you duplicate this program in your applications folder you can run two instances at the same time and thus compare a CF card to its copy.

Also most of what you need is already built into Unix and part of OSX. So if you gain some familiarity with the Bourne Again Shell you can do transfers using the Terminal.
If you have that kind of mind I recommend doing this because it's an all keyboard task, and it lists files as they are being transferred. Dragging files from one finder window to another is subject to slippage.

Ian

 

[dino g]

trade secret?

come on, we are in this together, and you guys are 3000 miles away from us and we are sending you business, certainly this is not going to turn into an us and them marketplace right away.

we are all trying to push this forward and share info, i have been doing that for free and my payback is more understanding on the part of the client. and then a greater likelihood of getting the gig.

personally, i am loosing too many jobs to 35mm or the varicam because the executive producers catches wind that the director and dp want to use RED and the exec gets scared and pulls the plug...

so if you figured something out, please share; that is what this specific thread is about, i may know something that you may not or do not, but since i can not say anything specifically right now, i wanted to let you all know/ warn you/ that if you are not saving the digi mag files, you should start doing so.

 

[Mark L. Pederson]

trade secret?

come on, we are in this together, and you guys are 3000 miles away from us and we are sending you business, certainly this is not going to turn into an us and them marketplace right away.

we are all trying to push this forward and share info, i have been doing that for free and my payback is more understanding on the part of the client. and then a greater likelihood of getting the gig.

personally, i am loosing too many jobs to 35mm or the varicam because the executive producers catches wind that the director and dp want to use RED and the exec gets scared and pulls the plug...

so if you figured something out, please share; that is what this specific thread is about, i may know something that you may not or do not, but since i can not say anything specifically right now, i wanted to let you all know/ warn you/ that if you are not saving the digi mag files, you should start doing so.

LOL!!

I was breaking iBloom's chops - there are many copy utilities with checksums - many are free -

We are using AAsync right now on the feature but testing a few others at the shop -

 

[I Bloom]

trade secret?

come on, we are in this together, and you guys are 3000 miles away from us and we are sending you business, certainly this is not going to turn into an us and them marketplace right away.

we are all trying to push this forward and share info, i have been doing that for free and my payback is more understanding on the part of the client. and then a greater likelihood of getting the gig.

personally, i am loosing too many jobs to 35mm or the varicam because the executive producers catches wind that the director and dp want to use RED and the exec gets scared and pulls the plug...

so if you figured something out, please share; that is what this specific thread is about, i may know something that you may not or do not, but since i can not say anything specifically right now, i wanted to let you all know/ warn you/ that if you are not saving the digi mag files, you should start doing so.

That's how Mark answers questions when he thinks you might have a better answer than his. :shifty:

My current workflow is to use terminal to copy files between volumes with the cp command. Once the files have copied, I check them over manually, with two finder windows, keeping an eye on file sizes. I have two copies of SuperSFV in on my dock that I run as two different instances. If it all looks good I drag the contents of the CF card into one SuperSFV instance and the contents of my new folder into the other SuperSFV instance. I then visually compare checksums. This also works for P2, but it's obviously a little slow and meticulous.

Update: My currrent workflow is a program called AAsync that I discovered in the series of tubes. This new tool is really going to put me ahead of all my competition. On the west coast they haven't even heard of this shit.

 

[Mark L. Pederson]

Update: My currrent workflow is a program called AAsync that I discovered in the series of tubes. This new tool is really going to put me ahead of all my competition. On the west coast they haven't even heard of this shit.

terminal hackin' smart-ass!

 

[dino g]

wow, impressive, seems like i have got to put on my computer geek hat and try and figure out what they hell you just said.

thanks for that.

 

[I Bloom]

wow, impressive, seems like i have got to put on my computer geek hat and try and figure out what they hell you just said.

thanks for that.

AAsync sounds like a good solution, I had been looking into something like it because my method is difficult to train people on. But I will say that on the flip side anytime you are incorporating an automated tool you need a human sanity check as well.

One other tip is that Finder does a slightly different calculation of file sizes between FAT32 (your CF card or Red Drive) and HFS Plus (a Mac OSX formatted drive). If you do a spot check between two finder windows you will discover a difference in file size of about .1MB

I think I need to get one of these CF reader hard drive units for december though. Anyone know where you can pick one up in NYC? B&H?

IBloom

 

[Mark L. Pederson]

One other tip is that Finder does a slightly different calculation of file sizes between FAT32 (your CF card or Red Drive) and HFS Plus (a Mac OSX formatted drive). If you do a spot check between two finder windows you will discover a difference in file size of about .1MB

I don't trust finder for sensitive data movement - ESPECIALLY in Leopard at the moment - I could just be paranoid - but I have seen things that scare me in the world of OSX finder ....

 

[I Bloom]

I don't trust finder for sensitive data movement - ESPECIALLY in Leopard at the moment - I could just be paranoid - but I have seen things that scare me in the world of OSX finder ....

That's true. You might also try this move:

Open the terminal.
type: cd /Volumes
type: ls
there will be a list of mounted drives
type: cd RED*ONE
(use * for filenames with spaces)
type: ls -altR | less
("-altR is not alt+R its letters A L T R. That character in the middle is the one above the return key)

Open another terminal window next to that one:
type: cd /Volumes/My*Drive*Name/My*Copy*Folder*Name
(put in the names of your drive and the entire copied Red cf card folder)
type: ls -altR | less
(Pressing "q" gets you out of less.)

If you start seeing spooky sh*t on Finder, (which actually happened on a Red shoot) use the terminal instead. Thirty Five Years of Unix developement never lies.

How to copy in terminal is a trade secret though. I'm gonna be first to market with that.

IBloom

 

[Mike Prevette]

I think you forgot " rm *.* "



EDIT: THIS IS A JOKE DO NOT ATTEMPT

 

[I Bloom]

That's almost not funny Mike.

With -fR it's not.

 

[reality]

\rm -rf is cooler

 

[ChristopherKenworthy]

To checksum or not

To checksum or not

I don't trust finder for sensitive data movement - ESPECIALLY in Leopard at the moment - I could just be paranoid - but I have seen things that scare me in the world of OSX finder ....

Could you elaborate on the Finder issues? You've started to me me paranoid, even though I've used the Finder to copy countless TBs of data without a single problem. Is the Finder notoriously rubbish at this? I've tried AAsync, but found that it slows the workflow to an impossibly slow level (even with a top of the range Mac.)

If I offload the CF, and watch the rushes every night and they play back OK, do I really need to checksum? What's the worst that can happen if I don't?

 

[Mark L. Pederson]

Could you elaborate on the Finder issues? You've started to me me paranoid, even though I've used the Finder to copy countless TBs of data without a single problem. Is the Finder notoriously rubbish at this? I've tried AAsync, but found that it slows the workflow to an impossibly slow level (even with a top of the range Mac.)

If I offload the CF, and watch the rushes every night and they play back OK, do I really need to checksum? What's the worst that can happen if I don't?

I can't say for certain that mac osx finder will ever fail you - but I have personally seen this ... and it hurts -

http://tomkarpik.com/articles/massive-data-loss-bug-in-leopard/

Not sure why you say AAsync is "an impossibly slow level" - we are shooting a feature right now and making TWO copies of 130G per day off of 8G CF cards with AAsync - and it's going like butter -

Do you really need checksum?

Well ... do you REALLY need insurance?

Not unless you have problems. Then it's pretty handy.