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

Feature request

B

Brook Willard

REDuser Sponsor
Joined
Dec 28, 2006
Messages
5,392
Reaction score
3
Points
38
Age
41
Location
Burbank, CA
Website
www.brookwillard.com
Hey guys,

An incident on set today reminded me of something I've been wishing for in the camera for a while. It's a thought I was going to put in the Epic section as a request, but since the concept is very technically similar to the camera's pre-roll functionality... I think it could be doable on the RED ONE as it stands today.

If a camera is destroyed in a shot [or, most of the time, if the camera loses power during a shot], the R3D file will not read properly and is often no good.

It'd be awesome if there was a mode where the camera closed the R3D file every frame, 5 frames - whatever is possible - it'd save shots like these. It'd also let the camera work more effectively as a crash camera. Since it costs less than an Eyemo and has no moving parts, it'd be a dream-come-true as a crash camera.

I don't know if it's technically feasible to be a constant function... or if it would have to be a special function for certain shots [if there was something that made it unusable in a normal situation]... but it'd be a fantastic feature. I feel like it should be possible.

If it's not possible with the hardware in the RED ONE, it'd be a wonderful feature to add to the Epic line of cameras.
 
Brook Willard said:
Hey guys,

An incident on set today reminded me of something I've been wishing for in the camera for a while. It's something I was going to put in the Epic section as a request, but since the concept is very similar to the camera's pre-roll functionality... I think it could be doable on the RED ONE as it stands today.

If a camera is destroyed in a shot [or, most of the time, if the camera loses power during a shot], the R3D file will not read properly and is often no good.

It'd be awesome if there was a mode where the camera closed the R3D file every frame, 5 frames - whatever is possible - it'd save shots like these. It'd also let the camera work more effectively as a crash camera. Since it costs less than an Eyemo and has no moving parts, it'd be a dream-come-true as a crash camera.

I don't know if it's technically feasible to be a constant function... or if it would have to be a special function for certain shots [if there was something that made it unusable in a normal situation]... but it'd be a fantastic feature. I feel like it should be possible.

If it's not possible with the hardware in the RED ONE, it'd be a wonderful feature to add to the Epic line of cameras.
Click to expand...

Noted. We'll check to see if this is possible. Stuart?

Jim
 
  • Thread starter
  • Moderator
  • #5
Clayton Harper said:
You can also use the make quicktime wrapper function from Red alert.

Always nice to be able to do when your battery is popping off at the wrong time. :beer:
Click to expand...

True, but the R3D doesn't always last up until the appropriate moment. Sometimes it's a few seconds earlier, sometimes a few minutes... sometimes the R3D crashes the relevant applications.
 
Good idea.

I liked Ted's story at NAB of the "accidental crash camera" after a stunt car mistakenly overshot it's target and landed on it. The ACs finally dug it out to find it still rolling.

Now THAT needs to be next years NAB Reel Credits!
 
Brook Willard said:
True, but the R3D doesn't always last up until the appropriate moment. Sometimes it's a few seconds earlier, sometimes a few minutes... sometimes the R3D crashes the relevant applications.
Click to expand...

Closing the file on every frame would do very bad things to your disk throughput.

The frames do actually hit the disk but it's the filesystem that may or may not be properly updated. If you ever have an issue where that happens and you need to recover the file, we can likely pull it out.
 
Why not just release a tool which intelligently closes the r3d after the fact?

Should be very easy if you are willing to sacrifice guaranteed file compatibility for all time.

It might be harder to retrieve audio, but extracting the necessary frames shouldn't be an engineering nightmare. Overall that would be a much simpler and more direct approach. Especially if you're willing to lose up to 5 frames. The only corrupted frame should be the last one.

After all. The camera does it automatically when you press "stop".
 
Deanan said:
Closing the file on every frame would do very bad things to your disk throughput.

The frames do actually hit the disk but it's the filesystem that may or may not be properly updated. If you ever have an issue where that happens and you need to recover the file, we can likely pull it out.
Click to expand...

Be great to release a utility (with no guarantees perhaps) but something that people could try and recover files with, should this occur.

I know it's been talked about before, any updates there?
 
This could be solved by a buffer-logic board that you connect between the camera and the drive. The board is passive and not do anything with the communication, UNTIL the camera have been offline more time (milisec or sek) than allowed. Then the board kicks in and just sends all file closing commands needed for the file system of the drive.

..or this can be build in a special edition of reddrive that is "crash secure" :)
 
Closing files every frame

Closing files every frame

As Deanan says, it would do very bad things for your data throughput, so you wouldn't want to do that normally.

But we can take a look at the practicality of an optional mode that you could select for stunt / explosion applications.
 
Brook Willard said:
Since it costs less than an Eyemo and has no moving parts, it'd be a dream-come-true as a crash camera.
Click to expand...

Costs less than an Eyemo? I have 3 Eyemos, none of which cost more than $300-$400. I'll sell you one of my Eyemos for slightly less than a RED!
 
Deanan is absolutely right. I would also like to add that as long as you see a clip on the media you should be able to load it in any of the apps, BUT, it might take a while. So be patient!
 
You must log in or register to reply here.
Back
Top