[Dan Thompson]

Alright so the new render was done in about 2 hours and no issues whatsoever!

Problem solved! Thank you so much!

[Dan Thompson]

Wow I did not know that, and I think you might’ve just saved me so much time!

The reason my render is so slow is because I have this complicated custom script that gets progressively heavier on the CPU the further you are in the timeline.

I have a feeling it’s also what makes the multi frame rendering fail.

I was wondering if there’s a way to just calculate the values ahead of time but I haven’t looked too it!

Anyway I’ve tried converting this expression to keyframes, it literally took an hour lol!

I’ve now turned multi frame rendering back on in hopes that the issue is gone.

I’ve tried rendering as a PNG sequence but the estimated render time just kept going up and was already reporting more than 6 hours.

Anyway so now I’m back to ProRes with multi frame rendering, hoping that it’ll turn out flawless!

I’ll update again when it’s done.

Thank you!

[Dan Thompson]

Just finished another 15 hours render and it came out without any issues, so it seems like multi frame rendering is indeed the cause of the problem unfortunately.

I’ll try rendering to a PNG sequence, from what I understand it should be somewhat faster as well.

I do have one question though, the entire project is just a single scene and it has a bunch of wiggle expressions, will those give the exact same values over multiple renders?

If not then the cut will be visible.

Thanks!

[Dan Thompson]

Another update, I tried rendering with multi frame rendering disabled.

It took over 15 hours, but at least it didn’t have any dropped frames.

Though I’m not sure if it solved the problem or I just got “lucky” with that specific render.

Any other ideas I can try? 15 hours render time is a bit of a problem for me.

Thanks!

[Dan Thompson]

Hey guys, just tried replacing the H.264 with ProRes, unfortunately that didn’t make a difference.

Any other ideas?

[Dan Thompson]

There’s one footage file that’s used as an overlay effect, its very minor and I’ve used it in other projects before with no issues, but I’ll try to encode it to ProRes first.

I do have multi frame rendering on, but I have no third party plugins at all.

I’ll update here tomorrow, thanks!

[Dan Thompson]

Or maybe create a custom keyboard shortcut for this specific parameter?

[Dan Thompson]

Is there a way to save my current setup after I’ve done this to all my layers?

It seems like I need to do this every time I launch the project.

[Dan Thompson]

Thanks!

[Dan Thompson]

Thanks a lot, Dan!

It worked like a charm. I think I even managed to add a base speed to your code by adding “+(time*mult2)” to the final outcome. I also added the smooth expression to the audio keyframes to make it less reactive and more average.

Side question, is there a way to apply expressions like smooth on the layers that are referring to the audio keyframes rather than on the keyframes layer itself? So that I can use different smooth parameters for different layers and parameters? Or do I have to duplicate the layer?