I've been working on Davinci for 2 weeks now. On the whole, I'm very happy with v17 and, unlike most other editing software, I'm very comfortable with it.
Nevertheless, I have a question, currently I have a Ryzen 7 3700X and an AMD RX 5700XT. Have recorded footage of a game that I recorded in AMD AMF HDR10 (H265 10bit YUV 4:4:2). So far I was able to edit everything without any problems and edit the colors and desired, but when exporting there is a problem.
I want to export the video only in H265 10bit. But the result is always 8bit. Have now since 9h me read through everywhere and tried to find a solution.
Currently I am that I should export it in Dnxhr 10bit what but at 25min just 240GB are and is absolutely moronic. The other thing is that H265 is supported by AMD only in 8bit and is possible by NVIDIA in Main10 (10bit).
But since I have a video format in H265 10bit this should be possible, so why doesn't Davinci show me this Main10 option to go crazy. Am I doing something wrong? do I now have to buy a video card for 900€ so I can export a video?
Can you switch to native encoding? On the Mac it helps, but I don't know if it's the same for Windows. If not, go for the intermediate route and do the encoding with Handbrake. It's better anyway. After that, you can kill your master file if you don't wan to future-proof your work.
My disaster protection: export a .drp file to a physically separated storage regularly. Please visit digitalproduction.com/author/uliplank/
Studio 19.1.3 2017 iMac, MacOS 13.7.4, eGPU MacBook M1 Pro and M4 Pro mini, MacOS 14.7.5 SE, USM G3
Okay understood, then only DnxHR is possible. Too bad then Davinci is not usable in the end. First render in a 200GB file and then with Handbrake again in a smaller format which all together takes 4h hours instead of 15min, is unfortunately not a good workflow.
Davinci should tell you in advance that you better have an Nvidia graphics card. Look at me then times premiere.
Funkeratto wrote:Davinci should tell you in advance that you better have an Nvidia graphics card. Look at me then times premiere.
Blackmagic should inform every single person that downloads Resolve about the hundreds of variations in things it can or cannot do, often times simply because the hardware or os doesnt support things (and thus is out of control for Blackmagic), or...
you should do your homework before you start using something..m
Last edited by Wouter Bouwens on Mon Apr 12, 2021 2:14 pm, edited 1 time in total.
CPU: Intel Core Ultra 7 265K 3900 GPU: Gigabyte RTX 4090 V2 Motherboard: Asus Rog Strix Z890-F Gaming Wifi RAM: 128 GB Sharkoon Fury DDR5 SSD: Samsung 990 EVO plus 2TB m.2 NVME OS: Windows 10 Pro
Still, since Resolve knows the capabilities of the system it’s running on, it would be very helpful if it could show a list of which features are currently available or not. The way it is now you often have to guess.
roger.magnusson wrote:Still, since Resolve knows the capabilities of the system it’s running on, it would be very helpful if it could show a list of which features are currently available or not. The way it is now you often have to guess.
That would indeed be handy. Something like a list of supported codecs perhaps?
Oh wait....
Shrinivas Ramani wrote:
Funkeratto wrote:I want to export the video only in H265 10bit. But the result is always 8bit.
That's cute. Of course I know that document and that's not what I mean at all.
BMD:s list isn't granular enough, and at some point it will be incorrect. Since Resolve already knows your hardware capabilities it should be able to tell you for instance if 4:2:0, 4:2:2 and 4:4:4 H.264, H.265, VP9 decode/encode etc can be hardware accelerated in various bit depths on the hardware it's running on. Then add an explanation for those that aren't enabled.
This goes beyond just codec support, it could show the same type of info for certain features, like the one's that can use Tensor cores.
roger.magnusson wrote:That's cute. Of course I know that document and that's not what I mean at all.
BMD:s list isn't granular enough, and at some point it will be incorrect. Since Resolve already knows your hardware capabilities it should be able to tell you for instance if 4:2:0, 4:2:2 and 4:4:4 H.264, H.265, VP9 decode/encode etc can be hardware accelerated in various bit depths on the hardware it's running on. Then add an explanation for those that aren't enabled.
This goes beyond just codec support, it could show the same type of info for certain features, like the one's that can use Tensor cores.
While that would be really handy, it sounds way too complicated to create. There is an almost infinite amount of possibilities in hardware combinations, os specific features and limitations, and codecs. And an insane amount of different hardware. The team they would need to create such a thing would have to be larger than the team they have now for developing Resolve
CPU: Intel Core Ultra 7 265K 3900 GPU: Gigabyte RTX 4090 V2 Motherboard: Asus Rog Strix Z890-F Gaming Wifi RAM: 128 GB Sharkoon Fury DDR5 SSD: Samsung 990 EVO plus 2TB m.2 NVME OS: Windows 10 Pro
You're misunderstanding. Resolve is already doing it, it's just not shown to the user.
I'm not asking them to make an offline list of hardware and its capabilities.
Resolve is already programmatically probing your hardware and the driver APIs to know what to enable. If you don't have H.264 encoding hardware acceleration for example, it's not shown as an option for rendering.
I'm asking for a report/log of the hardware/driver probing, visible to the user inside Resolve in an easy to use way.
Ah, now I understand. But the OP was complaining about not knowing the possibilities of resolve in combination with his hardware BEFORE het started using Resolve. What you propose would be nice, but would only tell you your hardware sux for Resolve after you've already bought it?
CPU: Intel Core Ultra 7 265K 3900 GPU: Gigabyte RTX 4090 V2 Motherboard: Asus Rog Strix Z890-F Gaming Wifi RAM: 128 GB Sharkoon Fury DDR5 SSD: Samsung 990 EVO plus 2TB m.2 NVME OS: Windows 10 Pro