Increased render time when using the takes system

[tobydalsgaard]

Was rendering a project with 3 different takes which I have used a ton in the past. Watching it render though it was taking up to 50 seconds between each frame preparing before it actually started rendering. I shut the computer down and optimized the scene and tried it again and got the same result when queuing up all the takes, roughly 1 minute 30 seconds per frame. When I did a test without using the takes renderer it was roughly 45 seconds per frame and almost no time spent preparing between frames.

Just wondering if there is a reason for this. Last night I was rendering out 900 frames for each of the 3 takes but in previous builds of Octane I have rendered out 1800 frames with 5-10 takes and never had any negative impact on my render times.

Scene size was between 6-8Gb depending on what was active in the scene.

Let me know if there is any more info you might need to duplicate the problem.

A. Windows 7 Ultimate Build 7601: Service Pack 1
B. 4x 1080ti
C. 64 GB Ram
D. 397.64
E. Octane Standalone 3.08
F. C4D Plugin 3.08
G. Cinema 4D R19.053
H. See above
I. Not applicable

[aoktar]

I'm trying understand your problem. Are you switching takes on every frames?

[tobydalsgaard]

I'm trying understand your problem. Are you switching takes on every frames?

No. I am simply using C4D's take system like I always do. I have 3 different cameras each assigned to a different take that is 900 frames. In the takes system you then put a check mark next to the ones that you want to render and it then will queue up the next take after the one before it has finished rendering.

The problem is that Octane is taking longer to process each individual frame when I use the takes system to render. Between each frame it hangs up on Start Rendering for about 30 seconds before showing the Rendering Samples at the bottom of the picture viewer. I have attached an image with a test that I just ran.

The first render in the image is using the takes system to render. Render Marked Takes to Picture Viewer to be more specific.

The second render was done by using the normal Render to Picture Viewer.

The setups are 100% the exact same. Samples, size, total frames, nothing happening in the background, using 4x 1080tis and using 4 more 1080ti's through network rendering.

If I wasn't always rendering really long sequences I wouldn't notice this type of thing, but when you render 900 frames and each one is 20 seconds longer then it should be it adds 5 hours to your total render time.

I have uploaded a second image showing the exact same same test but using standard renderer. On the top is the Render Marked Takes to PV and the bottom is normal Render to PV

[aoktar]

Let's check a sample scene if you mind to share. Otherwise no luck to know that.

[tobydalsgaard]

aoktar I will PM you a link to the scene.

[aoktar]

I'm testing that. But i have two advices for optimisations. See...

[tobydalsgaard]

I'm testing that. But i have two advices for optimisations. See...

Thanks aoktar. Yeah the subdivision thing I just forgot about for this project but I didn't know about the Geometry Update to help speed things up, went ahead and read up on it on your website