quietvoid

> This is interesting, if it contains code points below the mastering display black point then we would indeed expect massive problems. Maybe we should ignore the mastering metadata black...

> Stripping away the minML and maxML while leaving everything else untouched with a reencode "solves" this problem. Yes but it's not a solution. HDR10 distributed media usually has that...

> But I have a question, in order to test I would need to clear the icc-profile and this does not work in input.conf: > > ``` > F1 cycle-values...

I would make sure there's no other auto loading enabled. It works for me. mpv.conf: > icc-profile="~~/S2721DGF.icm" icc-cache-dir="~/.cache/mpv" icc-profile-auto=no use-embedded-icc-profile=no input.conf: > c cycle-values icc-profile "" "~~/S2721DGF.icm"

Any update on this? I'm interested in having the `display-p3` option.

Oh okay, I thought it wasn't being passed to VOs. Thanks.

> if you use 1 slot and 2 threads does it still hang? No, it works fine with those.

As is, this is probably ready for review. I'm just not sure how the CLI encoder should behave when the JSON metadata partially fails to parse. Also, hopefully it also...

It does appear that the current T.35 insertion code skips over some frames with `show_frame=0` and `show_existing_frame=1`. At least compared to the reference stream in https://github.com/AOMediaCodec/av1-hdr10plus/wiki, which has the metadata...

We already have a x86 build, so what you need is a build targeting Apple silicon? Such as the M1/M2. Hm, so a single binary concept exists, however: https://github.com/rust-lang/cargo/issues/8875