Resurrecting this because I finally got around to trying it: unfortunately, this didn’t work well for me. I get a lot more opportunity to tweak the color palette, but I haven’t gotten one that turns out quite right yet, which makes me think this approach would need about as much tweaking as manually figuring out the parameters to copy over HDR metadata.

Additionally, Tone-mapping requires using zscale to make the inputs linear, which requires compiling with --enable-libzimg, which Arch linux and most docker containers I’ve found don’t do. I managed to create a docker container that installs ffmpeg-full from the AUR, but that was a whole complicated affair, unfortunately, and takes forever.

Lynne
@pganssle Do you want to keep it HDR or do you want to convert it to normal? For the former, you'll want to use a compatible video codec (av1, hevc...

I think this actually boils down to this bug: trac.ffmpeg.org/ticket/7037

If I had more time to play with OSS and more experience in this domain I might jump on it. Probably in the meantime I’ll try to cobble together a script to mostly-automatically carry over the HDR metadata in transcodes.

This looks more like what I was looking for at the time: codecalamity.com/encoding-uhd-

I’ve written a little Python script wrapping the advice here and it seems to be working very well (though I haven’t tried it on any non-HDR and non-x265 content…)

QOTO: Question Others to Teach Ourselves. A STEM-oriented instance.

An inclusive free speech instance.
All cultures and opinions welcome.
Explicit hate speech and harassment strictly forbidden.
We federate with all servers: we don't block any servers.