Steve Mayhew

Having it default to original behavior with a setter to enable the refresh (and set the time) sounds fine to me. It is possible this issue is limited to Android...

No worries. Feel free to force push or whatever you need, branch is yours know. We’ll update our side so code matches On Mon, Oct 21, 2024 at 10:55 AM...

Sorry @tonihei I missed seeing your comment (I think you need to @stevemayhew to make GitHub notify me) Let me work on getting you access to the DASH-IF working group...

@tonihei Here's the document that DASH-IF is working on: https://github.com/Dash-Industry-Forum/DASH-IF-IOP/blob/master/specs/live2vod/01-live2vod.inc.md We are not voting members anymore, but this is completely the wrong approach if we want to avoid what this...

I would say, for now, keep this pull request "DRAFT". We have this work-around in our code base, but it would be far better if origin vendors would get in-line...

@mayurk2 the issue is `AdsMediaSource` itself, the doc comment says it all: ```java /** * A {@link MediaSource} that inserts ads linearly into a provided content media source. * *...

> The limitation obvious to me is in `AdsMediaSource` indeed. First off, this would be about supporting multi-period as the content source, while the inserted ad streams still must be...

I'm interested in progress on https://members.dashif.org/wg/Interoperability/document/4873. I'm working on getting ExoPlayer to work correctly with what this means to the user seek timeline. Also Dash.js could use some tuning in...

Also noticed... The position discontinuity caused by the `MaskingMediaPeriod` here: ```` 08-27 15:50:50.410 16684 16775 D MaskingMediaPeriod: selectTracks() - 66568544 override positionMs: 0 to preparePositionOverrideMs: 3571568, preparePositionMs: 0 ```` Is...

@marcbaechinger I've got the fix for this, writing up a pull request now. I have the code change, just want to add test cases too.