HLS.nextLevel / AUTO cause skipping

Nobody has claimed this yet.

Hello,

Firstly, really congrats for this work and doing something that changes the online video community! It's such a pity HLS isn't implemented natively on desktop.. Anyway.

I am having issues with FlasHls's level switching logic.
What usually happens is that audio skips one segment behind with freezing image when an AUTO level switch or manual via HLS.nextLevel = index is being made.
This doesn't happen on every switch though but it is often enough.
Of course it is very disturbing.

I reproduce it on a custom Clappr build with level control UI support that uses smooth switching (HLS.nextLevel) but this issue also reproduces for example here with AUTO:
http://www.flashls.org/latest/examples/osmf/GrindPlayer.html?src=http%3A%2F%2F176.9.1.233%2Fflashlstest%2Ftest.m3u8
- Start playback
- Manual switch to lowest quality (it is done via currentLevel from which i've seen as it is instant)
- Put it in AUTO and wait for the switch
- Usually the first time seems to be a good aligned one but retry the manual/AUTO 1-2 times, usually second AUTO switch is bad
I am seing it on latest Mac OS X / Chrome.

The source, http://176.9.1.233/flashlstest/test.m3u8 seems to run perfectly on iOS/OS X, no issues at switching points. also latest mediastreamvalidator reports everything good.

I assume there is something wrong with the logic in StreamBuffer.nextLevel at least for manual switches but my knowledge is still to low to figure out how that code works. Is this actually used also for AUTO?

Thanks again.

Start by reading the StreamBuffer.nextLevel logic and tracing how HLS.nextLevel, currentLevel, and AUTO switches are handled. Reproduce the issue with the linked test.m3u8 stream using the listed manual/AUTO switching steps. Done means repeated level switches no longer leave audio one segment behind or freeze the image.

Written by the indexing model from the issue text.