Live dash not playing on shaka due to 20ms innacuracy time

[Iragne]

Have you read the FAQ and checked for duplicate open issues?
Yes

If the problem is related to FairPlay, have you read the tutorial?

N/A
What version of Shaka Player are you using?

Latest

Can you reproduce the issue with our latest release version?
Yes

Can you reproduce the issue with the latest code from main?
Yes

Are you using the demo app or your own custom app?
Yes

If custom app, can you reproduce the issue using our demo app?
Yes

What browser and OS are you using?
FF and Chrome MAc

For embedded devices (smart TVs, etc.), what model and firmware version are you using?

What are the manifest and license server URIs?

What configuration are you using? What is the output of player.getNonDefaultConfiguration()?

Default configuration

What did you do?

I play a live but the buffer associated to the live is full of hole.
This happen after the each manifest refresh

What did you expect to happen?
The playback to work and the video buffer to be fully filled without any hole into it

What actually happened?

The video buffer is full of hole after each manifest refresh.

Each next segment (Reference) that should be added into the timeline is skipped due to inaccuracy of 20ms in the manifest.
here the code associated

// Append timeline
     let newEntries;
     if (currentTimeline.length) {
       const lastCurrentEntry = currentTimeline[currentTimeline.length - 1];
       newEntries = info.timeline.filter((entry) => {
         **return entry.start >= lastCurrentEntry.end;**
       });
     }

if we introduce an accuracy tolerance of few ms all is working fine and we are not removing the next segment for the timeline.

 // Append timeline
      let newEntries;
      if (currentTimeline.length) {
        const lastCurrentEntry = currentTimeline[currentTimeline.length - 1];
        newEntries = info.timeline.filter((entry) => {
          **return entry.start >= (lastCurrentEntry.end - 0.5);**
        });
      }

or this approach but not tested on my side

 // Append timeline
      let newEntries;
      if (currentTimeline.length) {
        const lastCurrentEntry = currentTimeline[currentTimeline.length - 1];
        newEntries = info.timeline.filter((entry) => {
          **return entry.end > lastCurrentEntry.end;**
        });
      }

event if it's working with that approach i'm not sure it's correct.
I also share the manifest format

Are you planning send a PR to fix it?
If you agree on the possible approach yes otherwise i'm happy to help you to reproduce
I have already a possible solution but i'm not sure it's correct and i would like to have your adivce
I don't want to make shaka break

SegmentTemplate of the manifest at the first download

<Representation id="1" width="1920" height="1080" sar="1:1" frameRate="50" bandwidth="4423000" codecs="avc1.64002a">
             <SegmentTemplate initialization="XXXXXX" media="XXXXX" timescale="1000"  startNumber="77">
                <SegmentTimeline>
                  <S t="346554266" d="2020"/>
                  <S d="2020"/>
                  <S d="2020"/>
                  <S d="2020"/>
                  <S d="2020"/>
                  <S d="2020"/>
                </SegmentTimeline>
             </SegmentTemplate>
           </Representation>

SegmentTemplate of the manifest at the second download

<Representation id="1" width="1920" height="1080" sar="1:1" frameRate="50" bandwidth="4423000" codecs="avc1.64002a">
              <SegmentTemplate initialization="XXXXXXX" media="XXXXX" timescale="1000"  startNumber="78">
                 <SegmentTimeline>
                   <S t="346556266" d="2020"/>
                   <S d="2020"/>
                   <S d="2020"/>
                   <S d="2020"/>
                   <S d="2020"/>
                   <S d="2020"/>
                 </SegmentTimeline>

[Iragne]

I propose the following solution to address the live issue