osmf-hls-plugin icon indicating copy to clipboard operation
osmf-hls-plugin copied to clipboard

currentTime is wrong - has +4 seconds offset

Open Alekscs opened this issue 12 years ago • 6 comments

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): https://github.com/denivip/osmf-hls-plugin/pull/72#issuecomment-30758859

Alekscs avatar Dec 19 '13 19:12 Alekscs

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 ?

danii-nebot avatar Dec 20 '13 12:12 danii-nebot

@Alekscs, maybe you give your stream for tests?

D3adKnight avatar Dec 20 '13 15:12 D3adKnight

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

Alekscs avatar Dec 20 '13 18:12 Alekscs

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.

D3adKnight avatar Dec 23 '13 13:12 D3adKnight

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.

danii-nebot avatar Dec 23 '13 14:12 danii-nebot

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.

Alekscs avatar Dec 23 '13 14:12 Alekscs