Sensible Error Messages for Unsupported Codecs

Resolve Free on Windows doesn't support 10 bit h.265. I am fine with that as a business decision to drive customers to the the paid version.

What I find completely unacceptable is the lack of error messages for unsupported files.

We see tons of posts here and on the subreddit for people opening 10 bit files in windows and getting distorted images. Or on Linux H.264/5 they get audio only and no image. But there is no indication from Resolve that this is intentional and expected.


If I tried to open a .zip file in Microsoft Office, it is going to say 'Hey buddy, I can't do that for you', Resolve, nope, puke some garbage to the screen and let the user be confused. Completely absurd.


Black Magic, please add sensible error message popups for unsupported files. (Like every other software on the planet has done for decades)

Here are some posts of users with this issue;

viewtopic.php?f=21&t=183786

viewtopic.php?f=21&t=196372

viewtopic.php?f=21&t=191230

viewtopic.php?f=21&t=166242

viewtopic.php?f=21&t=182992

viewtopic.php?f=21&t=178292

viewtopic.php?f=21&t=173353

viewtopic.php?f=21&t=200369&p=1047429#p1047429

viewtopic.php?f=21&t=203390

viewtopic.php?f=21&t=204959&p=1064759#p1064759

viewtopic.php?f=21&t=211103&p=1095018#p1095018

viewtopic.php?f=21&t=218615&p=1134843#p1134843

viewtopic.php?f=21&t=220492&p=1143196#p1143196

viewtopic.php?f=21&t=221802&p=1148684#p1148684

https://www.reddit.com/r/davinciresolve ... esolve_18/

https://www.reddit.com/r/davinciresolve ... e_footage/

https://www.reddit.com/r/davinciresolve ... e_footage/

https://www.reddit.com/r/davinciresolve ... s_in_only/

https://www.reddit.com/r/davinciresolve ... t/l05sxu6/

https://www.reddit.com/r/gopro/comments ... ?context=3

https://www.reddit.com/r/davinciresolve/s/gzgkECB50H

Resolve Free on Windows doesn't support 10 bit h.265. I am fine with that as a business decision to drive customers to the the paid version.

Black Magic, please add sensible error message popups for unsupported files. (Like every other software on the planet has done for decades)

Seconding ZRGARDNE request for adding sensible error message popup ie: prompt that D-Cinelike isn't supported. Hobby use here, but there are those that use the DJI Mavic mini 3 pro for pro shooting. So, it would be possible that those users could convert to paying customers.

I agree there should be error messages when Resolve rejects a media file, not just in this specific instance but in general. As is, nothing happens and there's no feedback, it's unclear to the user if an error has even occured.

I've just had a problem with Resolve rejecting some video files due to an almost invisible special character in their title. Granted this is trivial, there's no reason for anyone to ever have special characters in a file title, and if you do then it's easy to fix; but it's hard to notice and frankly never occured to me, i thought it was a more common issue like variable frame rate or something. It led me to convert ad re-convert those videos in every software i could think of for hours, when all i had to do was rename the files.

So yes, even a generic error message would have clued me in to vaguely the right direction, or at least away from the wrong direction.

Yeah, that's been suggested before. I would love to see a message that said something like:

"This format is not supported in the free version of Resolve.
Please purchase a license for Resolve Studio to enable this feature."

or words to that effect.

I also wish that when the program is installed or first launches, it goes out and does a CPU, GPU, and VRAM check and warns, "Sorry, your system will not function optimally with Resolve." I'd rather it do that than have the user blithely move on and then run into a session they can't ever render on that machine.

I also wish that when the program is installed or first launches, it goes out and does a CPU, GPU, and VRAM check and warns, "Sorry, your system will not function optimally with Resolve." I'd rather it do that than have the user blithely move on and then run into a session they can't ever render on that machine.

Yes

Laptop owners with iGPU only, install resolve for Linux and are so confused when nothing works.

Would be much more sensible for the software to check at install and refuse to install because of the lack of discrete GPU.

+1 Yes indeed.

Given that unsupported codecs still work sometimes in the free version, having an error message would make it much easier to understand when they don't work.

Likewise, at the risk of moving toward a more complicated product stack, I personally would have a strong interest in a product that keeps all the functionality of the free version but adds additional codecs from the Studio version. I don't need any of the additional functionality in Studio, but due to the cameras I have, I am using 10-bit H.265 regularly.

I ran into the same issue. Thanks to the Reddit community I've found out the reason. So +1 from me for a nice error message on not supported formats.

Just adding another voice requesting some sort of error message when attempting to import unsupported file types. Resolve's behaviour is inconsistent here. For ProRes Raw files, the files appear in the Media Pool but there is only audio which confuses users.

For some relatively new types of stills files such as AVIF and JPEG-XL, compressed files which are particularly geared towards HDR display, nothing happens. There is no error message and nothing appears. Some types of older DNG files open whereas other newer DNG files don't (e.g. Apple ProRAW DNG files), again with no error message. Ideally Resolve would be updated to support these stills file formats but some sort of error messaging would be welcome in the meantime.

Would be nice +1

Same Problem, same issue +1,

I'm having trouble with DNGs, I've tried converting using Adobe's DNG Converter and DxO Pure Raw 4. I see in the supported filetypes document that DNG is supported for stills, but I get a Media Offline notification. The Original RAW files are from a Sony in ARW format, does this make a difference?
My current workaround is to bring the DNGs into After Effects and export as EXRs in 32bit.
Anyone know why my DNGs don't work?

** I'm currently working in Studio 20 Beta