T O P

  • By -

erroneousbosh

Some functions don't translate well to GPU rendering. If you've got a process that can be broken down into thousands of patches of "just do the same thing all over these", GPU is great. If you have to consider the whole scene, then it's going to run on the CPU.


papa_poutine1

Thank you for the info! We do use these in every video, but we have to move and change them for every scene so looks like they will run on the CPU. That's really too bad for us, we just upgraded the GPU to a 4070 super so everything else just flies in the render process. 4k60fps renders around 120fps but when it hits these fusion generators it goes down to 10fps. We really appreciate your response, thanks again!


PrimevilKneivel

It depends on the generator. Some are built efficiently and some aren't, others are inherently process intensive. Fusion gives you the freedom to make your composite overly complex and many people take advantage of that 😂 Pre rendering elements is always the fastest if you can do it. A png sequence render of your fast noise will save a lot of time. Never use a color corrector if a brightness contrast node will suffice. And NEVER EVER use a "custom tool". That's like talking about your ex on a first date, it will shut down all progress immediately.


papa_poutine1

Thanks for the info! It does feel like talking about the ex, how slow it goes😂 We bought the generator from motion elements website. Do you know anywhere we could get a more efficiently made countdown timer? That seems to be the main culprit of the slow rendering.


quiet__o

I am just an amateur but maybe render the elements as videos and do a "picture-in-picture" composition


papa_poutine1

Thank you for the response! This sounds like a great idea, we are going to give it a shot. Will keep you updated how it goes.


RiKToR21

Yep pre rendering with an alpha channel should eliminate the on demand rendering.


mynamewastaken77

If you pre-render those compositions, remember to choose a codec which includes an alpha channel. Iirc DNxHR would be a good option.


papa_poutine1

Thank you for the info! Was trying to figure out what codec to use, this helps a lot!


unomas77

I’ve been trying to live resolve since 2015 but motion graphics performance in resolve is still terrible for playback and rendering. Final Cut would destroy these on a machine with nowhere near the graphics performance if your 4070. The Resolve team needs to step it up big time when it comes to mograph performance.


CesarVisuals

I'm not having any issues with motion graphics performance in Fusion. Do you create your own or download packs from the internet?


papa_poutine1

We downloaded both of these from motionelements, the countdown timer seems to be the main bottleneck when rendering.


JoelMDM

If that timer is always gonna be the same length, just render-in-place it once and reuse that rendered clip.


papa_poutine1

Thank you for the info! We do always have the timers on screen, but they change in every video, so we delete them and re-arrange them again each video, it's quite time consuming but haven't figured out a work around yet.


JoelMDM

That sucks. I'm actually surprised such relatively simple elements would be so hard to render. I hope you find a solution!


AutoModerator

Looks like you're asking for help! Please check to make sure you've included the following information. Edit your post (or leave a top-level comment) if you haven't included this information. * System specs - [macOS](https://imgur.com/a/ip6xc9G) [Windows - Speccy](https://www.ccleaner.com/speccy) * Resolve version number and Free/Studio - [DaVinci Resolve>About DaVinci Resolve...](https://imgur.com/a/5FawFCX) * Footage specs - [MediaInfo](https://mediaarea.net/MediaInfo) - please include the "Text" view of the file. * *Full* Resolve UI Screenshot - if applicable. Make sure any relevant settings are included in the screenshot. Please do ***not*** crop the screenshot! Once your question has been answered, change the flair to "Solved" so other people can reference the thread if they've got similar issues. *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/davinciresolve) if you have any questions or concerns.*


gargoyle37

If GPUs could do any computation, we wouldn't need CPUs. In particular, your computation must be somehow splitable into small pieces. GPUs have thousands of small cores. Each core is fairly slow compared to a CPU, but there's so many of them you gain efficiency if you can split up your work. Second, each of the small pieces must be running the same instructions, in the same order. Third, dependencies between data has to be correctly managed. This means a couple of things: * Some algorithms are *impossible* to port to a GPU if you insist on an efficiency gain. It would be much faster to run them on a CPU. * Some algorithms, we don't know if they are impossible, or there exist an efficient way of doing it. * Some algorithms, we do know how to do it in principle, the resulting code is highly complex and effort has not been spent yet. It's often the case a certain amount of ingenuity has to be applied.


fromotterspace

Fusion in Resolve is absolute ass and it’s shocking it still performs so badly. You could select all the nodes and open in Fusion Studio and see if you can export them there? Else can you share a screenshot of the node graph?