hdr10plus_tool VS Av1an

From what I gathered, it is possible to convert HDR10+ content to Dolby Vision using dovi_tool and hdr10plus_tool. But I haven't seen any tutorial on doing the opposite: taking the dynamic metadata from Dolby Vision and converting it to HDR10+. I have found posts with this question but with no solution. The replies to this one (from 2020) suggest that it is theoretically possible but that you would need more info about the DV metadata. Now, using dovi_tool, it is possible to extract the Dolby Vision metadata into a JSON file. But, while dovi_tool is able to generate a DV RPU using a JSON file containing HDR10+ metadata, hdr10plus_tool has no similar option. Is there any way to convert the DV metadata to something usable by hdr10plus_tool to inject in HEVC?

NOW, for dynamic HDR (HDR10+ or Dolby Vision), it's more involved but there is indeed a way to create encoded files with dynamic HDR metadata now by using dovi_tool for Dolby Vision, or hdr10plus_tool for HDR10+ files (or you can use BOTH on it if you have a file that is compliant with both standards). This one requires de-muxing the dynamic metadata from the isolated HEVC videostream of your source file, encoding your file an isolated HEVC stream, injecting the dynamic metadata back in to the encoded HEVC stream, then finally merging that with your MKV containing everything else. This is more complicated but here's the script for THAT...

downloaded quietvoid's HDR10Plus_Tool 1.0.0 (from https://github.com/quietvoid/hdr10plus_tool/releasesl)

You could also try converting the mkv to mp4 using ffmpeg and manually copy the HDR metadata over, which Premiere Pro then understands. It's just a bunch of tags telling the software what the pixel numbers mean. This can be done with reencoding, or maybe without if the mkv contains a video stream already in the right format and just needs to be moved into a mp4 (might not even require manually specifying metadata, maybe the converter you used just didn't support it). I'm not sure about formats like HDR10+ that have multiple metadata updates in a single video, you could use this to extract the metadata but I don't know how to pass that into ffmpeg again.

The hardware encoders are very fast and generally better than x264 (but not by as much as you'd think with the x264 slow preset).

In addition, there are threaded AV1 encoders you may be overlooking, like SVT-AV1. For non-realtime, my favorite is av1an, which also yields better quality than is possible from aomenc: https://github.com/master-of-zen/Av1an

I specifically used https://github.com/master-of-zen/Av1an with --target-quality 100 to keep the compression as close to lossless as possible (you could probably shave even more size off if you didn’t use near-lossless compression)

There's also Av1an as suggested by someone else. It's going to produce more efficient encodes because it uses chunk-based encoding to reach the required VMAF for every single chunk, but this is also slower because every chunk will be re-encoded until the VMAF target is reached. It's also a PITA to compile, has a long list of bugs, and isn't very actively developed. One of the long-standing issues is that frames have a tendency to go missing during splitting, which IME is going to keep happening when the input files aren't standardized. And thus the recommendation is to transcode the input to lossless first, which is just completely unsustainable.

i'm still trying to figure out if av1an is the breakthrough to using large CPU counts without losing quality. but it's a ridiculously poorly documented program. i haven't gotten it to run effectively yet. https://github.com/master-of-zen/Av1an

I don't know about VVC, but I've never seen a recommendation of preset 0 for SVT-AV1. The docs say "presets 1-3 represent extremely high efficiency, for use when encode time is not important and quality/size of the resulting video file is critical". It seems like 0 is the equivalent placebo preset. But if you want AV1 with coding efficiency over all else, IIRC the typical approach is to use av1an to detect scene transitions and farm out parallel encodes with aomenc.

That might be because it doesn't work.

Have you seen Av1an? It's supposed to encode to a target VMAF.

Are you using the current version, 0.4.0, from https://github.com/master-of-zen/Av1an/releases