Known Issues for DaVinci Resolve
Resolve requires a lot of GPU VRAM for temporal effects (all versions)
Current versions of DaVinci Resolve are very demanding when it comes to the GPU memory resources, especially when Temporal Noise Reduction (a built-in filter in Resolve) or third-party OFX plug-ins doing temporal processing (like Neat Video) are used. This may become a problem when working with large frame sizes, like 4K and larger. For 4K timelines, Resolve officially requires at least 8 GB of GPU memory (on one GPU). Resolve may experience a shortage of GPU memory even when those requirements are met, and especially if they are not met by the hardware. When that happens, Resolve will show an error message: "Your GPU memory is full. Try reducing the timeline resolution …"
To avoid such a problem please either run the software on a machine with larger GPU memory or decrease the timeline resolution. It may also help Resolve to not run its processing on the same GPU that is used to drive the display. What has also been reported as sometimes effective in such cases is to increase the Pre-allocated System Memory value in Resolve Preferences from 4GB to 8GB or higher.
Incorrect order of frames with retimed clips (Resolve 17 and possibly other versions)
Resolve serves to Neat Video incorrect frames or frames in an incorrect order when (1) the source clip is retimed in the project or (2) the frame rates of the clip and timeline are different. This then shows up in the output video as a stutter or partially reversed motion.
A possible workaround: go to the Edit page, select the clip, right-click to open the context menu and select "Render in Place".
Temporal effects are not supported by Resolve on adjustment clips, compound clips and more (all versions)
Current versions of DaVinci Resolve do not support correct operation of temporal effects applied to:
- an adjustment clip;
- a compound clip;
- the whole timeline instead of a clip;
- a nested timeline as a clip.
Do not apply temporal effects, including Neat Video, to those elements in Resolve to avoid incorrect rendering results.
The safe place to apply temporal effects, including Neat Video, is an individual clip in the timeline.
Applying two temporal effects does not work correctly (Resolve 18 and older)
If a temporal effect is applied after another temporal effect in Resolve, then the processing applied by the preceding effect may be lost in the final output. For example, if the built-in Deflicker is applied first and then Neat Video is applied to the same clip, then the flicker is not reduced (the result of Deflicker is lost). This seems to be caused by a bug or functional limitation of Resolve itself.
While the problem is being investigated by the developers of Resolve, we recommend to not apply two temporal effects together in Resolve for now.
Resolve does not serve adjacent frames if "Video field processing" is enabled (Resolve 16.1.1 and higher)
DaVinci Resolve 16.1.1 and higher do not provide adjacent frames (fields) required by Neat Video during render if the "Video field processing" option is enabled in the project settings.
A possible workaround: disable the "Video field processing" option in the project settings and instead set the scan type to "Interlaced" (if you work with interlaced video) in Neat Video itself.
Resolve crashes with "Video field processing" option enabled (Resolve 16 up to 16.1.1)
DaVinci Resolve 16 have a bug that causes a crash when a plug-in of certain class (plug-ins doing temporal processing, Neat Video is one of those) is used and the "Video field processing" option is enabled in project settings.
A solution is to disable the "Video field processing" option in project settings and instead set the scan type to "Interlaced" (if you work with interlaced video) in Neat Video itself.
Update: this problem has been fixed in Resolve 16.1.2
Incorrect processing of interlaced footage with "Video field processing" option (Resolve versions prior to 14)
Versions of DaVinci Resolve prior to 14 version do not behave as expected by Neat Video if the following conditions are met: (1) video is interlaced,
- the "Video field processing" option is enabled in Resolve. Resolve deinterlaces the interlaced video data in such a situation and that makes it impossible for Neat Video to correctly apply noise reduction to individual fields in the video stream.
A solution is to disable the "Video field processing" option in Resolve and instead set the scan type to "Interlaced" in Neat Video itself.
(The "Video field processing" option in Resolve also has another negative side effect: memory utilization of Resolve increases and render time increases too; also, never use that option with progressive video data.)
Adjacent frames not available (non-Studio versions of Resolve 14 and 12.5)
Non-Studio versions of DaVinci Resolve 14 and 12.5 do not provide adjacent frames required by Neat Video v4 (or newer) to display them in the main window of the plug-in. Those missing frames are marked with "N/A" in the thumbnails shown in the main window of Neat Video. This does not affect previewing and rendering in Resolve, this only affects the preview inside the Neat Video window.
The current (central) frame is still provided correctly, so it is possible to build a noise profile and check preview of some of the filters inside Neat Video. To evaluate the complete preview including results of all filters, it is necessary to Apply (to close Neat Video window) and then check results in Resolve preview. This is caused by the above limitation of specified versions of Resolve. This limitation is lifted in newer versions of Resolve.
DaVinci Resolve Studio 14 and 12.5 do provide the adjacent frames (although in reduced bitdepth) to the plug-in window, as described below.
The Studio versions of Resolve 14 and 12.5 work differently than non-Studio versions (and differently than older versions of Resolve Studio/non-Studio):
- the Studio may serve 8-bit data (to plug-in's window) instead of 32-bit data; that is reflected in Neat Video window; non-Studio version still serves 32-bit data;
- the Studio may serve adjacent frames to the plug-in's window (in addition to the central frame), so Neat Video may show the results of all its filters in its own window.
Update: Both DaVinci Resolve Studio 15 and DaVinci Resolve 15 (and newer versions) serve adjacent frames to the plug-in's window (in addition to the central frame), so Neat Video can show the results of all its filters in its own window.
Stuttering and other errors while rendering in CUDA mode (Resolve versions 10.1, 10.1.1, 10.1.2)
DaVinci Resolve 10: the versions 10.1, 10.1.1 and 10.1.2 of Resolve have a bug that shows up when plug-ins of certain class (plug-ins doing temporal processing, Neat Video is one of those) are used. As a result of that bug, the rendered video may stutter and contain other rendering errors. This issue only affects Resolve working in CUDA GPU mode. The OpenCL GPU mode is not affected.
Update: The problem has been fixed in 10.1.3 version of Resolve. Please update to 10.1.3 or newer.
Reduced resolution of the frame in Neat Video window (Resolve version 10)
DaVinci Resolve 10: the host application may sometimes send a reduced resolution version of the current frame to Neat Video when you try to build a noise profile for the clip. To work around that please do the following: close Neat Video window, return to Resolve, click into the preview area in Resolve and only then proceed to open Neat Video window.