Lawrence A

It looks like the subtitle is saved to file based on what the provider thinks the language is. If it thinks it's English but not hearing impaired it'll get saved...

I've done some thinking into handling AVC and HEVC profile levels more accurately and I think the way HEVC is done now, combined with per-device raising or lowering of the...

You haven't listed your device. Maybe it doesn't support those profiles?

This is because the Android emulator doesn't claim support for HEVC Main 10 or AVC High 10: ``` Media type 'video/avc': Decoder "OMX.google.h264.decoder" supports profile/levels: [ 65536/65536 (ConstrainedBaseline/5.2), 1/65536 (Baseline/5.2),...

That's Google's software decoder you've quoted. If I remember correctly, `c2.android.avc.decoder` is an alias for `OMX.google.h264.decoder`. If you keep looking you should find the hardware decoder. Could you post the...

For AVC, those logs say it supports up to 5.2 High but doesn't support High 10 at all. For HEVC, it supports up to 5.1 Main 10. The device page...

This is odd. The only thing I can think of is that MediaCodec is reporting a lower level than is really supported, causing transcoding. But even that I can't believe...

I don't think this affects the behaviour, but @nielsvanvelzen cherry picked the first commit in that PR for v0.16.5 rather than all of them. Therefore v0.16.5 contains the initial unfixed-up...

Is there any chance you can run `dumpsys media.player` in an adb shell and attach the result? This should dump exactly what MediaCodec reports as supported on the device.

> ``` > Decoder "OMX.Nvidia.h265.decode" supports > profile/levels: [ > 1/131072 (Main/High 5.1), > 2/131072 (Main10/High 5.1), > 4096/131072 (Main10HDR10/High 5.1) ] > ``` This shows that the device is...