bit depth beyond 8-bit?

Hi, as far as I can tell the profiles for hevc and av1 are all 8-bit, right? Would you consider adding 10-bit profiles? Thanks!

[EdvinNilsson]

The plugin currently only supports 8-bit depth and 4:2:0 chroma subsampling.

I am considering adding more options for bit depth and chroma subsampling in the future. However, one limitation of plugins for DaVinci Resolve is that you cannot change the pixel format for an encoder with the encoder settings; instead, you need to register a separate encoder for each combination of bit depth and chroma subsampling (i.e. pixel format).

[s0mebodyhelpme]

This would be really nice. I have HDR 10 bit videos that I can't quite use without the ability to export them in 10 bit.

[s0mebodyhelpme]

By the way, wouldn't something like the following achieve what is essentially a 10-bit vaapi render? Just asking since I've found myself having trouble exporting videos I've edited in davinci since there's a lack of 10-bit hardware accelerated options. Also how would one integrate the (aforementioned) following into the source code?

ffmpeg -init_hw_device vaapi=foo:/dev/dri/renderD128 -hwaccel vaapi -hwaccel_output_format vaapi -hwaccel_device foo -i bar.mkv -c:v hevc_vaapi -qp 25 -color_primaries bt2020 -color_trc smpte2084 -colorspace bt2020nc -color_range full -compression_level 0 -profile:v main10 out.mkv

[EdvinNilsson]

If you really need 10-bit VAAPI right now, you can make the following changes to the code and then follow the build instructions:

• Replace the pixel format AV_PIX_FMT_NV12 with AV_PIX_FMT_P010 for a VAAPI encoder, for example in h265_encoder.cpp on line 10.
• Replace the 8 with 10 in ffmpeg_encoder.cpp on line 53.

Note, this will break all other encoders and you will only be able to use the VAAPI encoders you changed to 10-bit.

[s0mebodyhelpme]

@EdvinNilsson thanks! this works for me. Appreciate it a lot as well as the effort you've put into this.

[s0mebodyhelpme]

@EdvinNilsson hello. sorry for the ping, but videos exported with this seem to not be detected by YouTube as HDR, while the raw videos are detected properly. Could it be the lack of main10 profile parameter parsing or something else? I've been fiddling with the settings for HDR and I can't seem to get it to trigger for YouTube when checking the editor section in the video upload. Output colorspace should be recognized by YouTube and it is recognized by mpv, but it just isn't getting detected as HDR by YouTube.

Edit: Had to edit the source code with the help of Google Gemini but I figured it out. The color metadata of the encoder needs to be modified for HDR.