DaVinci Resolve Troubleshooting

Richard Bennett
Filmora Stories
Published in
4 min readDec 9, 2020

DaVinci Resolve 17 by Blackmagic Design is a powerful video editing software that comes with a highly advanced color correction tool so that the users can edit, color correct, and finish in one comprehensive system.

Featuring more than 1000 new enhancements along with 250 cool features, DaVinci Resolve 16 is the most preferred software of professional editors and colorists. However, you may encounter some issues including failed to encode the video frame sometimes. In today’s post, I'm going to share some important tips about how to troubleshoot on DaVinci Resolve 17.

Part 1: Common Import Issues in DaVinci Resolve

Part 2: Crashes at Editing/Rendering in DaVinci Resolve

Part 3: Crashes at Exporting 4K in DaVinci Resolve

Part 1: Common Import Issues in DaVinci Resolve

Let’s start with the common import issues you might encounter.

  1. Volume not visible

This is the first and most problematic issue you might come across while using DaVinci Resolve. The volume might not appear in the library. For instance, your hard disk might be in the F volume, but you might not be able to view that.

Solution: The first thing you need to do is ensure that the drive is being recognized by your PC. In some cases, the computer doesn’t recognize the drive when the format isn’t correct. If your drive is recognized by the computer, then you need to go to Preferences and check your media storage location. Now click on the add button and introduce your hard drive by clicking on it. Any changes made in the Preferences are auto-saved in the library of your software.

Media File Not Visible

There are times where you get to see the folders, but on opening them it shows nothing inside.

Solution: Play the video in your video player to check if the video is corrupted. In case you can view the media files, then you have to move on to troubleshooting. Check if the file format/codec is supported by DaVinci Resolve in the ‘DaVinci Resolve Supported File Formats’. If you want to work on a video file that is incompatible with DaVinci, then you need a video converter, such as Wondershare Video Converter Ultimate to convert your media file into a high-quality format which is supported by it. Or, you need to edit your video footage with another video editor, such as Wondershare Filmora, which supports multiple formats.

Crashes due to ‘No CUDA Hardware Acceleration Detected’ error

Situation: Importing files after system diagnostic

DaVinci Resolve is very demanding in terms of the hardware environment, therefore ensure that your configuration (especially the GPU configuration) meets the requirements of the system. Any modern GPU like AMD, NVIDIA, or Intel supports the CUDA 2.0 and OpenCL 1.2 and should therefore work perfectly with DaVinci Resolve.

Solution: The first thing you have to do is make sure that your graphic card supports CUDA 2.0 standard. You can find this out by visiting the website of the manufacturer of your graphics card. In case it’s supported, then you need to update the card driver and launch DVR. If it still doesn’t work, then you might need to replace your graphic card. The NIDIA cards which have been manufactured post-2010 are known to support CUDA 2.0 and higher. The other option is to choose an alternative for the DaVinci Resolve to edit and color correct your videos.

Broadly speaking, the storage and the GPU are the 2 factors you need to look into before running DRV. Apart from that, the RAM and CPU of your system are also important. While 8 GB RAM is the minimum requirement for running DRV, you would do better with 16 GB RAM. You can find the right configuration in detail in the DRV configuration guide.

Crashes due to ‘No OpenCL Hardware Acceleration Detected’ error

This problem might appear while importing files.

Solution: Go to Preferences, click on Advanced and then add the lines as mentioned below. LsManager.3.NumGPUs = 1 LsManager.3.GPUMapping = 0 LsManager.3.GPUMappingEnable = 1 Local.GPU.Mode = CUDA

Make sure to save the preferences before you re-launch DaVinci Resolve.

Crashes due to Quick Time Decoder/Encoder Initialization failed errors

Apple has stopped supporting Quick Time for Windows which is why Windows users need to uninstall Quick Time from their computer.

Part 2: Crashes at Editing/Rendering in DaVinci Resolve

Crashes on all forms on clip change speed

This happens when you try to add a speed filter on the footage in the timeline.

Solution: What you need to do in this situation is unlink the audio of your footage before altering the speed.

Crashes after rendering 70%

There are instances where the rendering abruptly stops every time at about 75% in the case of 7.5GB files.

Solution: Check the configuration of your graphics card and get it replaced if needed.

Part 3: Crashes at Exporting 4K in DaVinci Resolve

Situation: DRV stops functioning while exporting QuickTime H.264 at 3840x2160 /25 fps on Windows 8 PC.

H.264 support is limited to only 2048 x 2048 pixels on Windows 8 for decoding and encoding.

Solution: Switch to Windows 10 to fix this problem.

Note: Davinci Resolve is awesome, but it requires a high hardware performance. And if you are looking for some alternatives, HitFilm Express, and Lightworks are good choices.

--

--