After Update to Studio 20

Hello everyone,
I would like to describe my brief experience of switching from Davinci Studio 19 to version 20. First of all: unfortunately, I succumbed to the temptation to install the new Davinci version 20. That was a big mistake. My active project no longer works. But first things first.

After switching from version 19 to version 20, I loaded my active project. In this project, 88 clips are carefully pached. So all the things that don't belong in the movie are removed. The work takes about two weeks. After the update, all patches are no longer executed! I go to the Fusion page and see that the notes are all red. Where is the error? I create a new project. I insert a single clip into the Media Page and create a timeline. The clip looks good. Now I open the Fusion page and insert the LatLongPatcher node. This node is of central importance for editing 360° films. This node refuses to work in the new Davinci. It does not work. No matter what settings are set, it turns red the moment a connection is made with the MediaIn.

I have already stopped working on the project, as a downgrade from 20 to 19 is probably not possible. I very much hope that an update will be released soon that will no longer contain such trivial errors. PS: The very old error GPU memory overflow, which is always present in all upgrades, is still present. My system has 128GB RAM, 124TB drive space and available GPU RAM of 88GB on two NVidia P6000. However, Davinci Studio 20 crashes completely when 24GB are exceeded. "The same state as after every update."

I hope that my tips are helpful and contribute to an improvement.
Result: Back to Version 19 and waiting for 20.x or 21 or ...

Sounds like the type of thing that logs would help with

This isn't the process for posting program issues. Please follow the official post at viewtopic.php?f=21&t=90190

A) Never upgrade mid-project
B) Always back up your database before upgrading so you can revert

Not following the outlined processes will make life difficult.

Is 88GB VRAM on the GPUs a typo, I assume you mean 48GB (2x24)? Even so, having two GPUs won't allow Resolve to use both GPUs for a total of 48GB per frame. Essentially it will use a single GPU per frame but can alternate GPUs for consecutive frames, giving a performance gain for long-running operations. Nowadays the gains aren't as clear and often a single modern GPU will be faster in the last 3-4 major versions of Resolve depending on the task.

Are they hooked up as recommended by BMD, with all monitors connected to a single card (and no Nvlink used?)

Hi Roger Magnusson,
thank you for your post and your questions. It is correct that 2x24 GB is physically present on the cards. The Windows 11 task manager and other similar tools show a total memory for the graphics cards of 87.8 GB. I assume that this additional memory is shared with the RAM and a shared memory is used by the graphics cards as required. However, the settings and configuration have of course been implemented exactly as recommended by Blackmagic Design. I had the device set up in this way. The platform is an MSI MEG 790 ACE, 128 GB RAM, Intel i9 14900K (32 CPUs), which is also LSI-capable and supports both graphics cards in parallel mode (Davinci support parallel processing of mulity graphic card systems also). The mashine is the main render mashine vor 8 or 12 k video production. All videos rendert in 16:9 relation, it means a minimum of 7680x4320 pixels, 444 12 bit and Dolby vision. Of course, the monitors are only connected to one card. Both cards are also connected internally by a corresponding bridge. Overall, the system does a very good job. Once you get used to the fact that Davinci simply has to be closed after a few steps and then restarted, it's not nice, but it works. If you don't pay attention to this behavior, the program crashes so violently that sometimes a system restart is necessary. But that's not my problem. I've gotten used to it. My problem is that version 20 no longer executes essential nodes in the Fusion Page correctly or these nodes simply don't work. This is serious, but can unfortunately be observed again and again with the release changes. Unfortunately, I made the mistake of upgrading to a new version too early. It was my mistake, even though I have the experience. What I find so unfortunate about this outstandingly good program from Davinci Resolve is that this great program suffers from these known conversion errors. New functions are nice, but software stability and reliability are even more important, especially for professional use.

Best wishes and here's to a new release, which will hopefully be coming soon.

Hi Mads Johansen,
What do you mean by protocols? Davinci has many protocols. I don't think protocols will help here. This is an easy-to-verify error. I was able to reproduce the error with version 20 using several clips with the following parameters:
Format : VC-3
Codec ID : AVdh
Codec ID/Info : Avid DNxHR
Duration : 30 s 30 ms
Bit rate mode : Constant
Bit rate : 6 987 Mb/s
Width : 7 680 pixels
Height : 4 320 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 29.970 (30000/1001) FPS
Color space : YUV
Bits/(Pixel*Frame) : 7.027
Stream size : 24.4 GiB (100%)
Writing library : DNxHR 444 12-bit

Many thank for your post und replay.

Hi GalinMcMahon,
I apologize for putting my post in the wrong category. I'll take a closer look next time. I'm just very disappointed that the widely advertised update has such fundamental errors and is therefore unusable for me. Perhaps there will soon be an update that fixes the fundamental errors in particular.
Thank you very much.

Hi Mads Johansen,
What do you mean by protocols? Davinci has many protocols. I don't think protocols will help here. This is an easy-to-verify error. I was able to reproduce the error with version 20 using several clips with the following parameters:
Format : VC-3
Codec ID : AVdh
Codec ID/Info : Avid DNxHR
Duration : 30 s 30 ms
Bit rate mode : Constant
Bit rate : 6 987 Mb/s
Width : 7 680 pixels
Height : 4 320 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 29.970 (30000/1001) FPS
Color space : YUV
Bits/(Pixel*Frame) : 7.027
Stream size : 24.4 GiB (100%)
Writing library : DNxHR 444 12-bit

Many thank for your post und replay.

I wanted the Diagnostics logs, never said anything about protocols

Both cards are also connected internally by a corresponding bridge.

As far as I know Blackmagic Design has always recommended NOT to enable SLI as DaVinci Resolve doesn't support it. I don't think that's changed. From the FAQ: "Note; VRAM is not accumulative if you have more than one GPU and you should not run SLI."

They did add support for NVLink around Resolve 17 but without memory pooling (GPU memory isn't combined). However, as far as I can tell the P6000 doesn't use NVLink, just SLI. SLI has 50 times lower bandwidth compared to NVLink and you should disable it and disconnect the bridge as it will give you worse performance.