Redcine - Long output times

[Mike Prevette]

minutes, that would jive with what I'm getting.

[Jay A. Kelley]

Digital... Can we please get the same tests on a 2k file? I would be so grateful.. On pins and needles over here.

Jay

[Kenn Michael]

It's MUCH faster if you take the 2K QT proxy that the camera and REDAlert builds and export that to ProRes.

on my 2.66 Quad Mac Pro
6:1 using FCP and 2K QT proxy exported to ProRes 1080 HQ
44:1 using RedCine

Like Rob said on another thread, the quality using the 2K proxy is high enough for most purposes. I agree. If you need the extra oomph, then off to conform-land. :)

[Greg M]

is that 2 hours and 43 minutes or 2 minutes and 43 seconds?

2 min 43 sec

[Greg M]

It's MUCH faster if you take the 2K QT proxy that the camera and REDAlert builds and export that to ProRes.

on my 2.66 Quad Mac Pro
6:1 using FCP and 2K QT proxy exported to ProRes 1080 HQ
44:1 using RedCine

Like Rob said on another thread, the quality using the 2K proxy is high enough for most purposes. I agree. If you need the extra oomph, then off to conform-land. :)

Yes, but being the anal type...I am a freak for the highest quality possible. Prefer to take the long road and enjoy the view.

[Kenn Michael]

Yes, but being the anal type...I am a freak for the highest quality possible. Prefer to take the long road and enjoy the view.

I hear ya!

[Lucas Wilson]

Hey guys,

A couple of really, really important things to keep in mind when rendering:

1) If you're rendering Quicktimes and rescaling, do the rescaling in the Shot part of REDCINE as opposed to setting the resolution in Output. Rescaling via Project and Shot settings in REDCINE is done by the GPU and REDCINE code. Leaving your project at 4K 2:1 (or whatever) and setting a different resolution in output assigns the resize to Quicktime, which is really, really sloooooooow.

2) I'm pretty sure this is in the tutorial videos, but there is the "Full," "Standard," and "Draft" options. Full pulls from the Wavelet at 4K/High. Standard pulls from 2K/High, and Draft pulls from 1K/High.

There is a *huge* gap in rendering between Full and Standard. Do your own tests and decide what is good enough in quality for what you need. If you can at all get away with rendering at Standard, do that. Render times will be much, much better.

3) NVidia drivers on OSX are not great. That is what it is. There are specific problems rendering "Full" with NVidia on OSX. It will be an unbearably slow render. This will get better as Apple improves the drivers (Apple writes their own drivers,) but until they do, this will continue to be an issue and not a whole lot can be done about it.

4) When rendering, set your Viewer resolution at 1/4 Medium. That is just the viewing resolution and does not affect output settings. But, the image is refreshed in the viewer every time a frame renders. If you have Output settings at Draft, and the view at Full/High, it will take a really long time - not because of the render, but because the Viewer is updating every rendered frame with a full 4K/High debayer.

5) Common sense, but close any other apps when rendering. Rendering out of REDCINE is a very CPU and GPU-intensive process. If other programs are open and claiming their own chunk of memory and resources, it will only hurt the render time.

6) When rendering to DPX, TIFF, or other high-bandwidth formats - storage is a big factor. The faster the pipe, the faster the render.

----

Bottom line - rendering is ALL about figuring out where the bottlenecks are and doing what you can to minimize those bottlenecks.

Lucas
------
ASSIMILATE, Inc.
LA, CA, USA

Currently drinking: Full Sail IPA

[Greg M]

A couple of really, really important things to keep in mind when rendering:

1)

If you're rendering Quicktimes and rescaling, do the rescaling in the Shot part of REDCINE as opposed to setting the resolution in Output. Rescaling via Project and Shot settings in REDCINE is done by the GPU and REDCINE code. Leaving your project at 4K 2:1 (or whatever) and setting a different resolution in output assigns the resize to Quicktime, which is really, really sloooooooow.

This seems counter intuitive.

For my render tests I scaled in SHOT to 1080P, and then set the same setting (1080P) in output, as I assumed since I was outputting I needed to tell it what I wanted.

So, how was the resize done in my case?

[Lucas Wilson]

So, how was the resize done in my case?

By REDCINE.

Lucas

[Fergus Meiklejohn]

thanks lucas :-)