quietvoid
quietvoid
So since the log doesn't help, not too sure what's happening with the first HDR signal. I guess otherwise technically it works as a first implementation. > Are you on...
Had a look at `dmesg` output.. First playback at boot: ``` Playback start? No HDR triggered [Mon Mar 15 12:54:23 2021] HDR SB:41 02 00 d0 84 80 3e c2...
You didn't provide any info from the issue template, we don't know what your OS is.
It is a `mpv-android` issue, there's no HDR passthrough support at the moment.
ExoPlayer based apps like [Just (Video) Player](https://github.com/moneytoo/Player) might work.
The default target is SDR, so I'm not sure how this is an actual issue? If you want HDR + 2020, specify it in your config: ``` target-trc=pq target-prim=bt.2020 ```
Right I hadn't understood that the issue refers to the OSD information.
At first I thought this was something about key frames vs inter frames, but there really is significant smoothing every other frame. @tdaede `--low-latency` makes the inter frame avg QP...
See https://github.com/yohhoy/av1parser/pull/14 I don't have any plan to support AV1 until the spec is finalized. Ideally we also need an encoder with support as reference.
See also https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/fe0403373964f6a5e633eb7adf9aa104cf9d59ff. It all comes from a patent, not DASH-IF's specification which refers to Dolby Vision within ITU-T.35 SEI messages.