However, there are some elements, such as callouts with tracking for which pre-rendering would not work. After creating most graphics FX in fusion, they get rendered with alpha in a variety of resolutions and frame rates. This has become a standard part of my workflow. I should also note that, with my hardware configuration, I am able to achieve smooth 2160p60 playback, with - timeline proxy resolution half - after a couple cache building passes pretty much no matter how many fusion titles and fx are on the timeline.Īlso, a couple years ago, someone suggested - pre-rendering - as many graphics elements as is reasonable. It will take me a bit of time to further try out the additional tests that people in this thread have suggested. Thank you again for everyone's high quality responses. Davinci Resolve isn't even using all of my ample available DRAM either. However, it seems everything in my system is configured as best it can be, including the Control Panel power management options mentioned elsewhere. This experience led me to believe that something wasn't configured optimally. It's been disappointing so far that investing in a 16 core 32 thread processor (AMD 5950x), and a 256bit memory bandwidth GPU with 16GB of VRAM has not appeared to have paid off (so far anyway), since Davinci Resolve doesn't seem to take advantage of the available GPU and CPU resources to their fullest. Using ProcessHacker2, HWinfo64, and Windows Task Manager, to monitor CPU and GPU usage during a Blender render, it finds all 32 of my 5950X threads and uses them all to pipeline the render, while also using the GPU to its maximum as well. However, this is quite curious software behavior on the part of Davinci Resolve.įor comparison, an application like Blender utilizes all available resources to their maximum when rendering.
Jim Simon wrote:For the most part, Resolve will use what it needs when it needs it.
0 kommentar(er)
