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

Render Time Calculator

Vigen Vartanov

Vigen Vartanov

Banned
Joined
May 2, 2007
Messages
1,288
Reaction score
0
Points
0
Age
42
Location
Tbilisi , Georgia
Website
sarke.ge
Good day. I have question about render time. Now first time we have big footage 20 min. We need to render it out to HD 1080 , QT TGA.
We render it on 4 CPU , 4 Gb MacPro , it takes about 23 Hours , and problem is that we can not make 1 big file , we make 10 small parts.
Sow can we calculate render time , we have another 8 core machine , and we like to now what will be deference with 4 core and 9 core render time.
Did some body test it , or have same problems with big footage.


Thanks.
 
I get 15-16x on my 8 core Mac Pro. So it would take me maybe 5.5 hours max to do a full debayer for 20 minutes of 4K.

When you're doing renders you have to make sure that your display setting matches the debayer setting to get the fastest render times:

Set display to 1/2 High for Standard Render
Set display to Full High for Full Render
 
kenn michael said:
When you're doing renders you have to make sure that your display setting matches the debayer setting to get the fastest render times:

Set display to 1/2 High for Standard Render
Set display to Full High for Full Render
Click to expand...

Really? Didn't Jim at one point say exactly the opposite? That we should set the display settings to the lowest and also scale the window down to the minimum so that the processors wont waste power refreshing the display..

Confused now...
 
Kjetil Haugen said:
Really? Didn't Jim at one point say exactly the opposite? That we should set the display settings to the lowest and also scale the window down to the minimum so that the processors wont waste power refreshing the display..

Confused now...
Click to expand...

that´s what I understand too !
 
There was a couple of tests showing that Ken is indeed right. You have to do dual processing of preview and files if the display settings don't match the render settings.

Gunleik
 
That's the issue. If you're rendering out at Standard or Full with 1/4 High display settings, it will take MUCH LONGER to render than matching the display setting with the debayer quality. This is why it is taking 23 hours to render 20 minutes. It shouldn't take that long.
 
kenn michael said:
That's the issue. If you're rendering out at Standard or Full with 1/4 High display settings, it will take MUCH LONGER to render than matching the display setting with the debayer quality. This is why it is taking 23 hours to render 20 minutes. It shouldn't take that long.
Click to expand...

Wow you're right. Rendered 2k DPX from 4k material 15% faster on my macbook pro. It didn't matter if the display was scaled down all the way or if it was set to 1:1. Thanks kenn
 
Is there a render time rule of thumb to go by?

Is there a render time rule of thumb to go by?

I really need to get some solid information about this issue.

Is it realistic to say that 1 hour of red footage will take 15 hours to render before it's usable?

The most recent film I did has 100+ hours of footage. That would over 2 months just to render if it were shot on RED!

If this is true then I'm going to have to reconsider using Red.

Can some kind soul point me in the right direction?
 
usable for edit or for final output? As far as I know, you shouldn't need to do a final best-quality render of 100 hours of footage just to have something to edit, unless your finished work is 100 hours long...
 
So here's the deal. 15x is for the Full debayer - highest quality image. You would never want to render all your raw footage in this mode.

I render my dailies in Standard to a 2K ProRes HQ file. This takes about 3x on an 8 core machine. This is not highest quality, but unless you can see aliasing on high detail areas and you're finishing for broadcast or DVD, you can online with this (or the 2K QT proxies that come off the camera instantly).

Once your cut is finished, then you can conform and render out just the clips you need with handles (either with Scratch or Ian Bloom's wonderful Crimson) at full debayer to 4K or 2K DPX files.

When I first got my camera, I was cutting from my 1K proxies in FCP instantly (no render or transcode time), but got comfortable doing the 3x transcode and one-light color correct pass from RedCine. Standard (3x) looks great no doubt about it, but Full is how Graeme designed it, and on certain material (as well as noise prints) there IS definitely a difference.

No need to reconsider Red. Just get comfortable with the workflow and you'll LOVE it!
 
What Mac Pro configs are people using?

I'm about to grab one, wondering if the extra $$ for 3.2 GHz gives a noticeable difference (I will be processing a *lot* of footage). Also wondering how much RAM at the max RedCine uses up.
 
RndmAxess said:
I really need to get some solid information about this issue.

Is it realistic to say that 1 hour of red footage will take 15 hours to render before it's usable?

The most recent film I did has 100+ hours of footage. That would over 2 months just to render if it were shot on RED!

If this is true then I'm going to have to reconsider using Red.

Can some kind soul point me in the right direction?
Click to expand...

Just as the last film you did didn't do full 4K frame scans of all the dailies, neither do you need to make full renders of all your footage.

Ideally you will do your offline from the QT Reference files, or from a lower quality conversion (although the QT Ref is quickest). Once your edit is locked off, then you go back to the R3D files and generate high-quality output for mastering, as you would go back and rescan at 2k or 4k the 35mm neg for a DI process.

The timeframes are probably not inconsistent either.

For film, with a realtime Telecine and then digitise from tape, you're looking at a minimum 2x runtime (although you can perceivably go from Telecine straight to NLE).

For final DI scans the speed will vary, they'll probably be faster than 15x runtime, but they probably won't be realtime.

Our current workflow, taking QT Reference into Avid, and then generating 2K DPX of finished edit it pretty reasonable. Footage for a ~4min Music Video took around 3.5 hours to make DPX (which we did overnight).
 
Biba said:
QT Reference to Avid ? My client have Avid System Windwos based. Can i give him footage qt proxy ?
Click to expand...

No. The proxies just works on Macintosh based systems at the moment.
Transcode the footage in Compressor to quicktimes with Avid codec and give him an ALE from MetaCheater and everything should run smooth.
 
Ok , we make same last time.
Also managers are killing me with question , they want to put render time in all rental projects. They need to now time of render for 1 min :)
Like 10 min - xxx min for final render.
Now i'm checking it with my footage , may be somebody did it also .
Thanks .
 
for the 8 core:
1 minute of 4K takes:
3-4 minutes at Standard (1/2 RES debayer)
15-16 minutes at Full

Draft is practically realtime when rendering to standard def, but it's a bit TOO draft for me :)
 
RndmAxess said:
I really need to get some solid information about this issue.

Is it realistic to say that 1 hour of red footage will take 15 hours to render before it's usable?

The most recent film I did has 100+ hours of footage. That would over 2 months just to render if it were shot on RED!

If this is true then I'm going to have to reconsider using Red.

Can some kind soul point me in the right direction?
Click to expand...

Yes but that's footage, right? No one wants to sit through a 100+ hrs feature :innocent: .

Basically your suppose to edit it through the quicktime proxies that's created. At this moment you can't really edit with the 4K 16:9, but everything else seems fine and except for a few sudden crashes in FCP it works. It's not 100% stabile yet but hopefully will be very soon.

So that leaves the render time for finished project only.

fred
 
You must log in or register to reply here.
Back
Top