Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

HLS - m3u8 - buffering endless

Hello.

I just upgraded from JWPlayer 6 to 7. Trying to stream a m3u8-file the player reacts strange.
I am using a playlist. The following happens:

1. starting the file the buffer symbol rorates endless in the middle of the screen
2. the bitrate choice is only available, when switching to the second playlist item, switching back to the first, bitate menu exists.
3. switching to a playlistitem, the video is loaded, but the endtime is not presen, stays zero.

Is anyone having the same problems?

8 Community Answers

Up Down

r.rentz

User  
-1 rated :

Okay, i found out a little bit.

Following could be recognized:

1. Starting with the playlist, no HD Menu is visible and the player buffers
2. Switching to the next playlist item, the HD menu appears
3. Switching to a manual bandwith, the buffering goes away
4. Returning to the first playlist item, everything is fine

By the way, the cue points that should be loaded appear from step2, although the first playlist item has cue points, too.

Up Down

mark

User  
0 rated :

Can't help without seeing your page

Up Down

server

User  
0 rated :

I've had exactly the same issue and can't upgrade to JW7 unless I resolve this.

Up Down

Todd

JW Player Support Agent  
0 rated :

Do you see the same behavior when trying your HLS stream in our Stream Tester at http://demo.jwplayer.com/stream-tester/ ?

Does the stream play perfectly in JW6? If so, please e-mail a link to a reproduction page to support@jwplayer.com

Up Down

Todd

JW Player Support Agent  
0 rated :

Or you could post a link to your test page or HLS stream here

Up Down

r.rentz

User  
0 rated :

Hello.

Can we discuss the problem in privat, because the video data is very sensitive and i do not want to post it ti public here.

Up Down

r.rentz

User  
0 rated :

Okay, i think it found out what happened. WE are using a m3u8 manifest file. A few days ago, we added a new bandwidth full hd, but the *.ts for that bandwidth is not rendered for all works, yet. So the firts bandwidth, that is automatically choosen by the jwplayer is the highest one, but that returns a 404. JWPlayer then uses another bandwidth, but the buffering does not appear. Removing the new bandwidth from the manifest, everything seems to work properly.

But i think, it is still a bug, right?

Up Down

Todd

JW Player Support Agent  
0 rated :

Are the other variant playlists loading correctly? If the individual .TS fragments return a 404, that is not a bug with our player.

This question has received the maximum number of answers.