Programmers Support: Davinci Resolve Error Report

Hi programmer team,
I will set this new topic here from time to time to help you with programming. Davinci Resolve is a fantastic program, which unfortunately has many big mistakes. These errors reduce the good quality of the program interface, the great documentation and the good ideas in this program. Detected errors are quickly fixed. Therefore, here are my little first reports for you.

Important setting:
Menu Playback: No Proxy Mode, No Render Cach, Fusion Memory Cach On. Use Optimized Media if Available (default).

1. Error report:
Memory Management and program stability:
Resolve attempts internal objects (possibly nodes or other storage objects) across the memory limits of the computer system. This even destroyed the Windows operating system in versions 16.0 to 16.2.5. Starting with version 16.2.6, only the program itself crashes. The error can be avoided by permanently observing the Windows task manager and finishing Resolve at about 80% Memory load and then restarting, then loading the last project and continuing with its work. After the reboot, Resolve's occupied memory is approximately 60-50% of the previous load. A simple timeline with approx. 80 clips can be edited in three reboots.

2. Error report:
Simple cuttings
Resolve internally generates incorrect section data that causes the rendering process to be canceled after a program has been re-edited. (see screenshot 1)

Cutting and Cross Dissolve Error

Davinci-Error-Transformation Error.jpg (303.21 KiB) Viewed 1218 times

The error can be corrected by moving the green marked section slightly to the left and right and then placing it roughly to the desired starting position. Then the error is fixed and a rendering process can be performed without errors. However, if you re-call the project, the same error reoccurs for all cuts. Even if the project is saved after the correction, the error does not disappear. It reoccurs each time the project is called. This makes the error very reproducible.

3. Error report:
If a rendering process is started in the Deliver page and consists of multiple clips, Resolve stops rendering from time to time. The following message is then issued for this purpose (seen screenshot). After the cancellation, however, the cutter no longer recognizes where an error occurred. A "deliver protocol" would be very helpful by logging all the steps of the rendering process. However, it would help if the clip number is displayed in the error message so that you can see which clip caused the cancellation.

Davinci Resolve-Error Message.jpg (17.13 KiB) Viewed 1013 times

[Shrinivas Ramani]

A clear indication of your hardware and driver setup and a link to a diagnostic log archive would be a good start for any issue report. Please check the FAQs for what information we find useful.

Thanks
Shrinivas

A clear indication of your hardware and driver setup and a link to a diagnostic log archive would be a good start for any issue report. Please check the FAQs for what information we find useful.

Thanks
Shrinivas

I will be happy to support them.
My Hardware:
CPU FX9590, RAM 32 GB, VRAM 2x24 GB, HW-Drive 18 TB (RAID 1), 2 x Graphics NVIDIA Quadro 6000 (2x 24GB VRAM). OS: Windows 10, Drivers: latest.

Please read the latest update here for new big errors.
Thank you in advance.

Error Report 4:
Here's an error when just cutting a timeline. There are four clips, the first clip has a length of about 1 second. The second clip has a length of about 3 seconds. The second clip is frozen to a still image. Here's the result.
The timeline cannot be exported because the rendering process stops with the error message described. It is not clear at which clip the process is aborts. The problem appears to arise during the transition from the still image to the video. Conversely, there is no error.
1. Screenshot: the normal view
2. Screenshot: setup
3. Screenshot: the result: Image fades to black. Normaly the cross desolves to the other image.

Davinci-Error-Freeze Frames-Normal.jpg (57.86 KiB) Viewed 975 times

Davinci-Error-Freeze Frames-set.jpg (57.21 KiB) Viewed 975 times

Davinci-Error-Freeze Frames-error.jpg (53.6 KiB) Viewed 975 times

Davinci-Error-Freeze Frames-error2.jpg (55.03 KiB) Viewed 975 times

Image fades to black. Normaly the cross desolves to the other image. If the cursor is positioned after the transition, you can see that the video sequence is not displayed. This error can be traced during all transitions from the still image to a video.

Bypassing the error: If you select the interface of the two clips in the transition and move this interface slightly to the left and right, then position the interface back to the old position, the error is gone. If you save the project and then call it again, the error is present again and a rendering of the sequence is not possible. Only for this one sequence have already been reworked four times 86 clips, only to bypass the error and enable a result. This is very annoying.

This error has also been verified on our other computer with other hardware (but also NVIDIA graphics cards). It is therefore independent of the hardware.

Such simple errors of the program increase the workload with Davinci Resolve Studio into the gigantic. In addition, the effort for error documentation and dialogue with the manufacturer (forum) is added. This does not make the program usable for professional applications!

...A clear indication of your hardware and driver setup and a link to a diagnostic log archive would be a good start for any issue report...
Thanks
Shrinivas

For your information, I would like to inform you that I have had a dialogue with one of her specialists for about 8 weeks. After I reported many bugs directly to you, he recommended that I join this forum and publish the bugs here. I am following the recommendation from her house/company.

In this context, I have sent my hardware configuration, screenshots, bug reports and other information several times.

Have you ever sent these?

Logs
DaVinci Resolve has a function to generate diagnostic logs that can be analysed to look for problems. It is important to get the logs from DaVinci Resolve, generated immediately after a crash. OS generated diagnostics and logs are of little use. Please post a link to these logs on the forum - this will often give others a chance to assist you. If you are unable to post a link, put a space in the path so the forum doesn't think its a link, eg. my logsarehere. com

You can grab logs by restarting DaVinci Resolve and choosing “Create Diagnostic Logs on Desktop” from the Help menu.
If you have automatic crash reporting enabled, adding your contact details and description would help us contact you if we need further details.

If you cannot launch DaVinci Resolve after a crash, please follow the steps below:

Mac OS:
In Finder, select "Go to Folder..." (⇧⌘G by default), type the path /Library/Application Support/Blackmagic Design/DaVinci Resolve/ and hit Enter. Run the CaptureLogs application.

Windows:
Go to C:/Program Files/Blackmagic Design/DaVinci Resolve/ and run CaptureLogs.bat application

Linux:
From the Applications menu, under DaVinci Resolve, select DaVinci Resolve Capture Logs

Note: Additional information - including the NFO file for Windows users and the SPX file for MacOS - is often useful. Please check the Posting on the forum section on how to obtain this information.

...A clear indication of your hardware and driver setup and a link to a diagnostic log archive would be a good start for any issue report...
Thanks
Shrinivas

For your information, I would like to inform you that I have had a dialogue with one of her specialists for about 8 weeks. After I reported many bugs directly to you, he recommended that I join this forum and publish the bugs here. I am following the recommendation from her house/company.

In this context, I have sent my hardware configuration, screenshots, bug reports and other information several times.

Have you ever sent these?

Logs
DaVinci Resolve has a function to generate diagnostic logs that can be analysed to look for problems.....

Hi, many thanks for this input.

I know these settings and use them intensively. I sent many crashes directly to Blackmagic Design.
The question, however, is, in my view, when these fundamental errors will be corrected. I would like to talk about mistakes that are at a higher level. But simple errors in editing, memory management or pointless ads, I find very regrettable and they hurt the reputation of the company at the end of the day.

I have counted for you the crashes since Fri Jul 10 16:46:19 2020 - Uptime 04:37:10 and to this day. There are 89 logged crashes! I have purchased several licenses. This is not funny for a program for which I have paid several hundred Euros. I have been suspended from purchasing additional hardware such as Blackmagic Design control consoles because of these huge errors.

Have you ever sent these?

Logs
DaVinci Resolve has a function to generate diagnostic logs that can be analysed to look for problems. ....
If you have automatic crash reporting enabled, adding your contact details and description would help us contact you if we need further details.
...

Here my Debug Report for all details from yesterday.
Please let me know, if you have any solutions. You can contact me directly within this forum. Thank you in advance.

One of the interesting error messages is, "Read outside clip bounds". This should not allow a program to allow an internal process to attempt to work outside data boundaries. This level cannot be influenced by a program user or should a program not allow and intercept such errors, if such a thing should be possible at all by an user operation.

Hi developers,
Mr. Ramani,
today I spent my whole day of work with the error analysis of Davinci Resolve. A day for you. Please check the following:
Creates a clip and cuts it after a second with Freeze Clip, so that the Freeze Clip is about one second long. Just delete the video part. Then all that remains is the freeze clip. For example, drags the Freeze Clip to 5 seconds. Then you go to the Deliver Page and render the clip. I use the H265 with NVIDIA. Result: the clip is not as long as you defined it. It is only a few frames long. That is the ERROR. In a project where I have a transition from a freeze frame to a normal clip, the rendering process stops precisely because the previous freeze frame is never as long as you see in the timeline. It is only a few frames long, so the render process internally reaches into the empty and crashes or aborts. Very big mistake.

[Shrinivas Ramani]

Hi Kay

When generating diagnostic logs after a crash or a bug, please go to Resolve's Help menu, click on Generate Diagnostics log on Desktop and use that archive. Zipping individual files offers us very little insight into the setup.

From the zipped text file, I can see some concerns with the graphics setup.
I would like to check if
a. the P6000 and M6000 are in SLI/NVLINK configuration? if so, please use them as individual cards. If the instability persists, please try with only the P6000 connected.
b. if you have tried clean-reinstalling the latest drivers for the graphics cards form the nvidia website.

Also, when rendering edits - including freeze-frames - please ensure you're rendering as a single clip and not as individual clips. Please refer to the manual to learn more about the difference between these render settings.