Problems loading media in 17.1.1

Good Day

I'm experiencing some issues after upgrading to 17 that I did not have in 16. Basically, all media I try to import (regardless of filetype or source) cannot play back. I can see the audio waveform in the preview, but the image in the thumbnail is black and when imported to a timeline the play button turns red. This is the case with new projects as well as opening old projects. I also tried footage captured on my Ursa, as well as my Canon and some stock I downloaded.

I am brand new to editing in general and to Resolve in particular, so I would assume this is user error, however I can't seem to find any guidance on what settings to fiddle with.

Any ideas?

[Shrinivas Ramani]

Hi Roedolf

Can you give us some context on your OS, hardware, drivers, and add some detail on what codecs/camera sources you use, what action you take and where you see the issue (e.g media pool thumbnail, source viewer, timeline)

Please see the FAQs to determine what information will serve as a good starting point.

Regards
Shrinivas

Hi Shrinivas,

Sure:
I run Windows, on a Intel machine (i7, but nothing special) drivers did not change since last week (when I could work on V16 without issues). Only variable that changed is the upgrade to V17.1.1

Where do I see the issue: All of the above. I can see the file created in the media pool, but the thumbnail is black (the red scrub line follows the cursor when I mouse over, but no image loads in either the thumbnail or the preview screen.

When dragging a clip to the timeline, it is simply a blue bar, and trying to play the clip results in the play button simply turning red.

The videos are sourced from a Ursa 4k (Prores 422), but the problem occurs for any media from any source. Whether it is stock downloaded from the web or .avi files shot on my canon dslr. Even opening up a project I worked on last week renders the same problem.

I can upload some screenshots if there is a method I can share them.

Thanks for the prompt response.

[Peter Chamberlain]

Please follow the FAQs info re what to post and how

Thanks guys, I got it sorted by uninstalling and reverting to 16.2.8.

It nuked my database, but since I'm a dabbler it's not a crisis.

I'll give the upgrade a shot once om on my new PC in a few months, as I'm not going to go through this rigmarole twice.