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

Slowest frame rate RED can do

RED for stopframe

RED for stopframe

I am very interested in what the RED can bring to the stopframe and pixillation industries, I would love single frame capture out of the camera.

Currently for features and commercials 35mm movie cameras (Mitchells) tend to be still used although DSLRs are making a big inroad here.

The problem with DSLRs is that you have to video-tap the viewfinder to get over the shutter problem if you want a live feed. There are also restrictions on the frame rates you can use.

If you are used to using a film camera fitted with an animation motor and controller for stopframe or pixillation, then you have control over shutter speed (typically 1/8,1/4,1/2,1 sec, 2 sec and upwards), frame rate (1,2,4,8,16,24 and upwards) and continuous run on/off, shutter capping etc

If the RED gave us single frame capture it wouldn't be hard to devise a simple electronic control system that duplicated that.

Then we would be able to do run and gun pixillation across wild landscapes!

Mike Gifford
 
But it can do 0 FPS on release, if you don't press the record button. Zero is lower then one... ;)

1 fps. This will not be enabled at 1st shipment but will be in an upgrade fairly soon after.

Jim
 
And yes, single frame capture in a picture file format would be a great feature to have.
 
Still unanswered is the question of variable data rates, and whether we'll be able to max out the throughput of the processor and storage device.

At 1 FPS, I'd think you could record an uncompressed frame.
 
Any chance to develop RED to have slower speeds than 1 fps? Something like 0.1-0.2 fps would make it possible to film stars and other phenomena in the night sky.
 
quote from stuart

quote from stuart

Any chance to develop RED to have slower speeds than 1 fps? Something like 0.1-0.2 fps would make it possible to film stars and other phenomena in the night sky.

quoted from stuart english post:

"Slow Shutter no, Timelapse Yes.

When you have a tape based recording solution or a log GOP codec, you must feed the recording system a fixed number of frames per second. RED does not have either of these restrictions, so the same visual look is achieved by operating in Timelapse mode."

but i wouldn't expect this feature enabled when cameras first ship.
 
A built-in intervalometer function would be extremely interesting. I would definitely make use of that. Preferably it would allow:
Shoot a burst as slow as once every hour.
Allow each burst to be up to a minute or so.
In single frame bursts, allow long exposure times.

RED, please incorporate this functionality eventually!
David
 
Essentially the answer is that you can do time-lapse with a maximum exposure of one second. Within that limitation, the interval in between shots doesn't really matter; with the amount of storage you'll have, it shouldn't be a problem to fire off a shot every second and then throw some away in post if you want.

I think the one-second exposure limit is a little unfortunate, especially for night footage, but what are ya gonna do? Probably someone will bring up the idea of using a 360-degree shutter and adding frames together in post: Maybe, but unless there's absolutely no latency between frames, you're going to get gaps in the streaks of moving objects. For example, a streaked taillight will have a break in it where one frame ended and then the chip started gathering light for the next frame. So maybe someone from Red could weigh in on that issue.

I'm curious about why you can't have fractional frame rates less than one, too.
 
Any chance to develop RED to have slower speeds than 1 fps? Something like 0.1-0.2 fps would make it possible to film stars and other phenomena in the night sky.

I second that desire. 1 fps is unfortunately not slow enough for celestial timelapse. And for me speeding up in post is not the same thing.

I would say it makes more sense to use a DSLR for these shots, but RED might have a lower noise floor and better bit depth (??).

IBloom
 
I would say it makes more sense to use a DSLR for these shots, but RED might have a lower noise floor and better bit depth (??).

Not if you shoot raw on a Canon, for example. I'd say the DSLR would be superior, because it's uncompressed (and we don't have an answer on whether we can write uncompressed frames to the Red's on-board storage if the frame rate is low enough).

It seems like the only real reason for doing time-lapse on the Red would be matching it to live-action shots done with the same lens/sensor combo.
 
Not if you shoot raw on a Canon, for example. I'd say the DSLR would be superior, because it's uncompressed (and we don't have an answer on whether we can write uncompressed frames to the Red's on-board storage if the frame rate is low enough).

It seems like the only real reason for doing time-lapse on the Red would be matching it to live-action shots done with the same lens/sensor combo.

I don't think that would be a huge issue. Since timelapse is rarely matching back to a scene. I agree with you and it would be better to put a RED to use shooting higher frame rates, the cost is significant.

Still it's quiet a nice feature to have. I often tack vacations on the end of away shoots in nice places. As much as I'd like to bring it I often leave my DSLR at home when I'm already packing cine gear. It's just too much to worry about. And shooting timelapse is for me a great way to relax. So I guess that's why I would hope for even slower frame rates. I guess we'll see.

IBloom
 
I still don't see why we can't have fractional frame rate and next I'll be asking why not a flash sync at 250 or more. Red is based on a DSLR and much more after all.
Is there some way to sync HMIs at all?
 
1fps-3fps is really ideal for daytime cloud formation timelapses and such.

For night celestial shooting, you generally need exposure times closer to 30 seconds, depending on the moon. Maybe Red with its amazing ISOs can cut that time down, but 1fps isn't going to be shooting stars.

The reason why it would be great to have a lot of timelapse/intervalometer features on Red is that post production on DLSR timelapses is a huge pain in the ass, generally speaking. With a video camera, though, like the HVX, timelapse is a total breeze.
 
...and we don't have an answer on whether we can write uncompressed frames to the Red's on-board storage if the frame rate is low enough.


I think Stuart said as long as the data doesn't exceed the maximum bandwidth, then it's possible.

So the answer is YES you can write 1FPS 4K uncompressed, but I'm not sure how high can you go before it overloads. 12FPS??

:matrix:
 
So the answer is YES you can write 1FPS 4K uncompressed, but I'm not sure how high can you go before it overloads. 12FPS??

Really? I didn't see that. That's good, if true. It means that there's a path for uncompressed raw data to on-board storage, which doesn't depend on the raw port.

Can anyone confirm this?
 
Back
Top