Multi Period DASH with DRM

[ssenanayake]

[REQUIRED] Searched documentation and issues

Searched in Google's Exo Issues, and also in StackOverflow to see if others have encountered similar issues.

[REQUIRED] Question

We have DASH content that's Multi Period. One period is an Ad (or set of Ads) with no DRM. Then after the Ad period ends, we have the content section which contains WV DRM.

On FireOS devices there's a pause, lag between the transition from Ad period (without DRM) to Content period (with DRM).

We at CBS use the Amazon port of Exo because it has traditionally been more stable on Amazon devices and works well on pure Android devices too.

1. Can the lag be minimized ?
2. Are there any optimizations that we can do to improve the performance when transitioning from a Non-DRM period to a DRM period ?

Sample Content: https://vod-gcs-cedexis.cbsaavideo.com/intl_vms/2019/03/06/1453250627601/21048_cenc_precon_dash/stream.mpd

Content's LA url for WV: https://cbsi.live.ott.irdeto.com/widevine/getlicense?CrmId=cbsi&AccountId=cbsi&SubContentType=Default&ContentId=19A7D434-8AC8-3835-5681-54E32CBA735B

[rinoshs]

Is the lag seen in pure android devices?

[ssenanayake]

Sorry for the delayed response. There is a lag on pure Android devices too. But FireOS devices have a slightly longer lag during transitioning from Non-DRM Period to DRM Period. But we have managed to minimize the UX as much as possible.

[davibe]

@ssenanayake does exoplanet contact the arm license server again when the period changes after advertisement ?