currentTime is wrong - has +4 seconds offset

[Alekscs]

New version has same issue as previous. But two versions back works good. Playing starts from 0 second but currentTime reports 4th second which is of course bad - there should be 0 sec. I wrote a bit about this here (plus code which is responsible for it):
#72 (comment)

[danii-nebot]

Hi Alekscs, I am not seeing this issue with the latest version from #72 in any of my tests playlists.

Please notice that the code you pointed out as responsible for this issue is not there in #72 anymore - the if(!timestampReseted){ line is back in there. I agree removing that line was a very bad move as it was messing up with the timestamps, although I just saw issues when seeking and discontinuities.

Could you provide a playlist in which you're seeing this issue after #72 ?

[D3adKnight]

@Alekscs, maybe you give your stream for tests?

[Alekscs]

Thx for reply. Right - new release has good code "if(!timestampRested).." Hmm that's making more strange issue right now. Please check this stream how it's works for you:
http://fryzjeri.cluster015.ovh.net/hlsaac/aac.m3u8

[D3adKnight]

4sec timestamp present in stream initially.
In early releases I set initial timestamp to zero, so this part of code has been removed. I'll try to get it back.

[danii-nebot]

Hi all, I am too seeing 4sec timestamp initially in that stream, but my player reports currentTime just fine - I mean beginning from 00:00 as it should be. Not sure what could be going on there...

I've noticed something weird as well: this playlist reports a total duration of 42 seconds but ends after just ~31 seconds of playback.

[Alekscs]

Thx for testing. 31 seconds is ok - 42 seconds coming from bad values in m3u8 file (sorry for not fixed values). I'm going to check more about timestamp.