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

Long long shot

Cédric Laty

Well-known member
Joined
Jun 12, 2009
Messages
142
Reaction score
0
Points
0
Age
52
Location
France
Website
www.lamplighter-films.com
Hi there,

I have a question.
Considering the heat (cause of bugs) and the maximum size of a 640gb red drive, what is the maximum shot lengh you can do with a Red One ? In hours of course !

Excuse my english.

Cheers

C
 
320 gig hard drives get you about 2 and a half hours of of 4K footage....so double that, but I would be wary about putting that much onto a drive at one time.....a test might be in order to see how the system handles it.
 
If you shoot 2K at 2:1 aspect ration at Redcode 28, and framebase 23.98 fps, you could theoretically jam 29 hrs on to a single 640Gb drive.

If you set 4KHD instead, you get almost 8 hrs on a 640Gb drive.

Personally I have done 2hr+ takes in 4K to 320Gb drives on multiple occations.
 
If the environment is not too hot then yes you could shoot 7 hours (whilst being aware of the the warnings above that you are putting all your footage into one place, which is a high risk if something goes wrong).
 
No. It is the same risk as several takes on a single drive. Red One records long takes in 2Gb chunks.
 
Thanks Pawel for the expanded explanation (you really ought to have a reputation for being particularly correct :tongue_smilie:!). I agree with your point, namely, keeping a truck load of footage in one place is a risk.

BTW it must be getting close to seal season soon?
 
No. It is the same risk as several takes on a single drive. Red One records long takes in 2Gb chunks.

True, but when the camera crashes or loses power during an extended take, many times some of the earlier 2GB chunks will become inaccessible or corrupt. Not common, but it does happen. Long takes make me nervous... even if it's just from my memories of the early days! :)
 
Thanks guys for all the infos !
YES, the environment will be hot unfortunately !
I have to figure out a "cooled box" or something.
Do you think i can consult someone at RED ?

cheers
 
well you will want to run your fans high, they will be noisy but you'll have to work around it, also they make cooling packs for cameras, i'd check them out and keep them fresh, just to be safe.
 
Do you think i can consult someone at RED ?

There are many experienced RED users here willing to help and this is the best forum to ask questions. The guys from RED are monitoring these messages and, I'm sure, if you were not getting the information or getting wrong advice they would chime in.
 
True, but when the camera crashes or loses power during an extended take, many times some of the earlier 2GB chunks will become inaccessible or corrupt. Not common, but it does happen. Long takes make me nervous... even if it's just from my memories of the early days! :)

would RedUndead fix those corrupt files? if someone is in a situation where they have to shoot non-stop, they might need to take that risk if they don't have the ability to shoot two cameras in tandem
 
I regularly shoot in excess of 1 hour; and often up to 2 hour single takes, as do a number (many?) of shooters here.
 
I regularly shoot in excess of 1 hour; and often up to 2 hour single takes, as do a number (many?) of shooters here.

james, do you ever have audio_record_fault errors or sata_trans_fault errors with your drives? if so, does RED Undead fix it for you?
 
as Far as i am aware red undead doesn't do anything to the R3D file it's self, but rather rebuilds the library file from the Reddrive/ram/card. Allowing you to recover it if you accidentally deleted it. But if you have written on the drive again you may have written over it and therefore you wont be able to recover it.

There are outher third party programs that rebuild files with some cleaver algorithms for files that have been over written or corrupted but this may take days to process.

Errors caused when the camera is recording will be recorded on the drive as an error. that means there was no state when the file was not corrupt but was corrupt at the time of writing, and there for no software can recover what was never there in the firstplace.

But if it is a corrupt drive then the data has a possibility of being recovered.

Earlier builds where less reliable than the current builds which are considerably better. there are no guarantees that it will not go wrong but as stated above it is quite sold now. The biggest risk you have is a crash from over heating or vibration. If you put the fan on high and use cooling packs and perhaps and extremal desk fan or small wind machine to add to further ventilation.

I would if I could run of mains power supply but through a UPS/APC (uninterrupted power supply). because even if you use the duel battery plates you may knock it whilst changing batteries and power the camera down.

And to the issue of having large amounts of data on a drive. ofcourcse is never a wise idea and if you can download regularly that is always perfectible. but it seems to be a circumstance where your recording one single shot, so it isn't possible and therefor a mute point. I would go for the 640 drive that way you can get the leanth of time you want but not have do down grade you resolution and sensor size to squeeze it on.

also It worth a note that if you think that vibration might be a issue whist your recording then I would consider the red ram at 1 hour for 4K (120gb)

I also know some other ways to keep the camera cool PM if you want to know how, as there not nessarly red friendly but could save the day in jam.
 
If I had to capture a 7hr shot, I might try and persuade that a 2nd rig as a backup is in order. Cheap insurance if it's a one time event.

You have talent that can stay "on" for 7hrs!? Any chance spilling the beans of their agent's number?
 
Back
Top