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

Timelapse is Pretty Nice

Nick Pasquariello

Well-known member
Joined
Dec 23, 2010
Messages
1,010
Reaction score
0
Points
0
Location
Providence, RI
I was driving home tonight, and right in front of me was an AWESOME full moon with PERFECT clouds. Installed the new software, blackshaded, tried the new frame summing and frame averaging, and then went into timelapse, all within about 45 minutes. Caught some great stuff:


I need to play around with the settings a bunch more. With the timelapse on 1 frame, 8 second intervals, it looked like it was merging 8 frames together (frame summing and averaging was off [tripple checked]EDIT: See below. This didn't actually happen. So, I'll have to do a lot more testing to learn what all the settings do. The clip above was the next shot: 1 frame per second, 1 second exposure per frame.

But! SO FUN. I f*$&ing love how much better my camera is now compared to 10 months ago when I received it. Which is now my go-to reason when someone asks me Why Red and Why Not Canon/Black Magic/Arri/Sony: their cameras don't get better for free.

And more than showing off (since the clip above is my fumbling and not at all perfect [my backfocus may be off, too. Hmph.]) I'd love to see what others have done with this, and also love some input on what the various settings do, and any thoughts on best utilization.
 
Last edited:
I know right! :)

I still haven't messed with Frame Averaging yet. Not really even sure what it does or why it does it haha.

But here is my first timelapse with Epic, happened to have an amazing sunset to play with...

2second intervals @ 1/96shutter, 50mm FD @ f/11 and HDR @ 4stops.

 
That's just . . . stunning, Tehben. It doesn't even look real. It also kind of looks like the opening shot to a live-action Lion King; the color palette looks painted.
 
If frame processing is off then time lapse will not combine frames in any manner. Time lapse and frame processing are separate functions. If you feel that it is not working this way please open a support ticket and send in a log and short clip. We will be able to confirm your settings from the log and see if there is a bug or not causing what you saw.
 
I know right! :)

I still haven't messed with Frame Averaging yet. Not really even sure what it does or why it does it haha.

But here is my first timelapse with Epic, happened to have an amazing sunset to play with...

2second intervals @ 1/96shutter, 50mm FD @ f/11 and HDR @ 4stops.


Tehben this is sick. Straight out of LOTR. Nice FD lens!!!
 
I take it back Trent. I just went back and looked at the clip in question (for the purposes of sending it in with a log file). The way the clouds were, on my tiny monitor, outside, it looked like the image was "stuttering".

Nope, just stripey clouds. Now that I've gone back in and looked at the shot, frame by frame, and compared the clouds to itself (as well as counting stripes), I now see that what I thought I saw, I wasn't seeing. Which is good! Things are working as intended, so long as there's not user error.
 
Thanks guys :)

I wish I could compare the HDR to a regular exposure but I overexposed the A track for the shadows and then exposed the X track for the sunset so I can't really do that.
Graded in RCX on my sRGB calibrated monitor and by the time I had exported and uploaded to Vimeo it looks way darker on my laptop... still nice, but less of an HDR showcase haha.
 
When I saw people here crying about not having enough frames per second with build 4, I did not hear one of this folks complain about the fact they just got the exact same time lapse features as the EPIC x and M.

That means as a time lapse camera the Scarlet can perform exactly as the epic line of cameras.

Im not sure what some of those folks were thinking.

the time lapse mode with frame summing is a s clean as some dslr's, I have been trying to shoot night time lapse since I got one of the first red one cameras. To see a star field moving through frame on my epic with No noise made my decade.

david
 
i'm still not sure why you'd use your red as a goto for timelapse... but there are some cool shots showing up and it's certainly a welcome and much appreciated feature addition.
 
i'm still not sure why you'd use your red as a goto for timelapse... but there are some cool shots showing up and it's certainly a welcome and much appreciated feature addition.

One word - HDRx - which effectively turns your camera to 18-stop DR. Essential for TL's that have a drastic change in brightness, such as sunsets and sunrises...

I'll be getting my own Epic shortly, but will keep the Scarlet precisely for its TL's functionality - which indeed matches the Epic. This way I have one camera shooting 5K HDRx TL while the other can shoot 5K HDRx slow-mo...

Peter
 
i'm still not sure why you'd use your red as a goto for timelapse... but there are some cool shots showing up and it's certainly a welcome and much appreciated feature addition.

So far timelapse is looking pretty awesome and the workflow is surely much more streamlined. Plus having the advantage of .r3d with raw, HDR and much smaller file size compared to shooting with say a 5D.

And yes! All those Scarlets should be able to shoot HDR timelapse in 5k as well ;)
 
i still shoot timelapse on my magic lanterned canon... not the same as r3d, but still raw. i've got a fairly streamlined workflow for that, and it certainly beats draggin my red kit up a mountain.
 
i'm still not sure why you'd use your red as a goto for timelapse... but there are some cool shots showing up and it's certainly a welcome and much appreciated feature addition.

I've been experimenting a bit myself. HDRX and magic motion offer some intriguing capabilities here. Maybe y'all should try it. ;)
 
well, alright :)

but it better be worth climbing a snow-covered mountain and freezing to death...
 
i'm still not sure why you'd use your red as a goto for timelapse... but there are some cool shots showing up and it's certainly a welcome and much appreciated feature addition.

Try it, and then you'll see why people love. Shoot the same thing on your DSLR! I thought the same, but no more. And this is my thinking before get the new features in build 4.
 
1. HDRx - I have shot the same exact timelapse of Mt. Fuji sunrise with both Epic and 5Dmk-II - the Canon ran out of DR (from slightly underexposed to unusable over-expose) in a 1/3 of the time the RED did...
2. Weight - I can't remember how many TL's shot on DSLRs I have helped to grade and finish - almost always involving shake stabilization. The much heavier RED setup is rock solid for TLs exposed to the elements...
3. RAW editing and post. If You want to edit and/or grade TLs from Canon - You have to first convert them to video - loosing the RAW capabilities. Good bye non-destructive workflow. Not so with the REDs...
4. REDMOTE - the ability to hide in my car and be able to monitor the exposure histograms and other stats remotely
5. Firmware v.4 - more then ever - PreRoll - never again miss that special element of your time lapse (http://www.facebook.com/media/set/?set=a.347063302067532.80104.100002915948884&type=1)
6. RED Color Science - after seeing stuff I have shot on RED ONE years ago put through new color science (currently at v.3) - I can only imagine what is in store for us in the future...

These alone are good enough reasons for me... As Michael said - go and try it for yourself - then make up your mind. I have years of shooting TLs on DSLRs (and 35mm ARRI mind you...) - and I now use my Scarlet exclusively...

Peter
 
Back
Top