DASH/Widevine Performance on 2017-2019 Devices

Web App Development
1

Hi,

we are working on several apps using Widevine with DASH for live- and replay-streams.

Across the board we see the same issues (with Shaka, Bitmovin, Dash) that the VST for such streams on 2017-2019 devices is comparably slow.

Our observation shows that after the Device has loaded Manifest, Segments and did the license request there seems to be a 3-4 seconds gap where everything is “ready” but no playback started yet.

CPU/Memory are not in dangerous areas also.

Any pointers or comments on how to optimise such a setup on these devices?

Are there recommendations on the DASH-configuration and/or encoding?

Are there known issues around this?

Thank you very much

2

We support HTML5 MSE/EME, not DASH. (See Streaming Protocol and DRM.) If you are using an HTML5 MSE/EME player, DASH support is up to the player. If your player supports DASH, you can use DASH. But this means that DASH is processed by the player, not webOS TV. Therefore, in most cases, we cannot help you. If you are currently using a third party player solution, please contact the solution support. Thank you.

3

What is the LG recommendation for live and catchup then on such TVs?
HLS+PlayReady?

4

To use PlayReady, you should use HTML5 MSE/EME, not HLS. Please refer to Streaming protocol and DRM combination. Thank you.