When buffering is turned off, the sync goes out.

[brodiddev]

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

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

yes

What version of Shaka Player are you using?

4.10.8

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? demo app

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

What browser and OS are you using? window chrome

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.getConfiguration()?

not config

What did you do?

I set the Chrome browser limit to 5KB with NetLimiter.

There is no sync issue with hls.js played in the same Chrome browser.

When I turn off buffering on the shaka player demo page, the sync is out of sync, and the same audio is heard 2-3 times. The following two errors are mainly displayed in the console log.

What did you expect to happen?

Assertion failed: SegmentIndex.merge should not change the first reference time!
Possible encoding problem detected! Unexpected buffered range for reference shaka.media.SegmentReference {startTime: 202.3380000591278, endTime: 203.3200000591278, trueEndTime: 203.3200000591278, startByte: 0, getUrisInner: ƒ, …} from URIs ['https://6464.m4a'] should be {start: 202.3380000591278, end: 203.3200000591278} but got {start: 203.319333, end: 204.300666}

What actually happened?

Why doesn't only Shaka Player recognize the startTime and endTime of the audio fragment?

In the above issue, setting hls sequenceMode to false did not cause the sync issue. However, the error below occurs repeatedly and there is a problem with the buffer being filled and depleted over and over again. Assertion failed: SegmentIndex.merge should not change the first reference time!

Due to the large size, I sent a video of the problem to [email protected] by email.

Are you planning send a PR to fix it?