DaVinci Resolve 17 and 18 not loading video files

Hello,
Recently I downloaded not only Resolve 18 but 17 just to do some basic video editing, and whenever I load in the file, there is no preview, the play button doesn't advance the timeline, and there is no video or audio. When loaded into shotcut the video loads just fine, and I have tried both MP4 and MKV on all sorts of codecs. I'm using H.264 currently which should be compatible. Not sure what the issue is.
Thanks

Try some BRAW clips. Report back.

https://www.blackmagicdesign.com/products/blackmagicraw

Cameron, more info would be helpful. What OS, GPU, amount of RAM, etc, do you have? H264 files in either an MP4 or MOV container should be no problem.
Does your computer meet the minimum specs for running Resolve?

System Specs for 18.xx.jpg (134.34 KiB) Viewed 3400 times

The 2GB of VRAM for the GPU is the barest minimum you can get away with for editing HD. A GPU with a lot more VRAM will work much better.

Hi Cameron
Sorry you're having trouble. The most common causes of initial trouble are:
- Using an older machine that doesn't have a powerful enough GPU (Resolve uses the GPU for video operations and can't fall back on the CPU), and
- Using an unsupported codec

Of course it could be something different but these are good places to start.

Sounds like you think your codec is OK. I'd suggest trying out an editing codec though just to rule this out. Jim has suggested BRAW. ProRes and DNxDR are typical good choices. Shutter Encoder can help you move between codecs.

Cameron, more info would be helpful. What OS, GPU, amount of RAM, etc, do you have? H264 files in either an MP4 or MOV container should be no problem.
Does your computer meet the minimum specs for running Resolve?

System Specs for 18.xx.jpg

The 2GB of VRAM for the GPU is the barest minimum you can get away with for editing HD. A GPU with a lot more VRAM will work much better.

Hi, Im running a 6700XT 12GB, a Ryzen 5 5600G, 32GB 3200 MHz RAM, and windows 10.

Hi Cameron
Sorry you're having trouble. The most common causes of initial trouble are:
- Using an older machine that doesn't have a powerful enough GPU (Resolve uses the GPU for video operations and can't fall back on the CPU), and
- Using an unsupported codec

Of course it could be something different but these are good places to start.

Sounds like you think your codec is OK. I'd suggest trying out an editing codec though just to rule this out. Jim has suggested BRAW. ProRes and DNxDR are typical good choices. Shutter Encoder can help you move between codecs.

Hi,
I'll check the codec with the conversion, as I don't think its a low hardware problem for me, my system is a new mid range build.

Hi Cameron
Sorry you're having trouble. The most common causes of initial trouble are:
- Using an older machine that doesn't have a powerful enough GPU (Resolve uses the GPU for video operations and can't fall back on the CPU), and
- Using an unsupported codec

Of course it could be something different but these are good places to start.

Sounds like you think your codec is OK. I'd suggest trying out an editing codec though just to rule this out. Jim has suggested BRAW. ProRes and DNxDR are typical good choices. Shutter Encoder can help you move between codecs.

Alright, so I couldn't convert into BRAW or any of the codecs you listed with shutter encoder, but I was able to switch into DNxHD and DNxHR and had the same issue.

You can't convert into BRAW.

I'm saying download the BRAW clips from the link I posted and test those. Set your clips aside for a moment and test the BRAW.

You can't convert into BRAW.

I'm saying download the BRAW clips from the link I posted and test those. Set your clips aside for a moment and test the BRAW.

Ah I see, sorry about the confusion. The problem persists with the BRAW file as well.

Clearly your media isn't the problem. That's a good thing to know!
If you post your logfiles and a .nfo from your system someone here will probably be able to tell you what's going on.
See the pinned items at the top of the forum for how to do that.

[Dwaine Maggart]

In the Resolve Help menu, select "Create Diagnostics Log on Desktop"

This will place a Resolve log file named similar to this on your Windows desktop: DaVinci-Resolve-logs-20181228_140434.zip (You may not see the .zip extension if your system is set to hide known extensions).

Then open Windows System Information and do a File - Save (Not a File Export), which will generate a .NFO file.

Place both those files on a file sharing site and provide links to the files here.

If you are a new Forum user, you may not be allowed to post URLs. If this happens, just put a space near the front of the URL, so the system doesn't think it's a URL.

Clearly your media isn't the problem. That's a good thing to know!
If you post your logfiles and a .nfo from your system someone here will probably be able to tell you what's going on.
See the pinned items at the top of the forum for how to do that.

https://www. dropbox.com/s/fdnzwi4mg8fdhk4/DaVinci-Resolve-logs-20230206-165235.zip?dl=0
https://www. dropbox.com/s/kea0bno18xjkeuy/Windows%20info.nfo?dl=0

There ya go, both log files should be in that drop box.

[Dwaine Maggart]

Open Windows Device Manager, select Display Adapters, right click Virtual Desktop Monitor and select Disable Device.

Now does Resolve work any better?

And is there some reason you are using Resolve 17.4.6 instead of the current 18.1.3 version? It's possible that 17.4.6 doesn't like the current AMD 22.11.2 driver you have installed.

Open Windows Device Manager, select Display Adapters, right click Virtual Desktop Monitor and select Disable Device.

Now does Resolve work any better?

And is there some reason you are using Resolve 17.4.6 instead of the current 18.1.3 version? It's possible that 17.4.6 doesn't like the current AMD 22.11.2 driver you have installed.

Disabling it fixed it! Not sure why that caused it not to work but thats fine by me.
Im on 17 because a friend suggested it might be more stable and work better since 18 wasnt working for me. I'll probably switch over to 18 now.

Hi,

I'm having the same problem, but I don't have a virtual display monitor. Any ideas as to what is causing this? Here's a link to my diagnostic logs:

https://drive.google.com/drive/folders/ ... sp=sharing

[Dwaine Maggart]

@Eric: I need a Windows System Information .NFO file. Open the Windows System Information app and select the File - Save menu to make the .NFO file.