New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lots of requests per second to the same .ts files #930
Comments
@DavidVentura jsdelivr is hosting an old version of Clappr, can you provide the stream for testing? |
@lordcris can you try to reproduce this error at http://dailymotion.github.io/hls.js/demo/ ? |
I can't. |
Thanks @lordcris while using the https://cdn.jsdelivr.net/clappr/latest/clappr.min.js does any errors happens? |
yes, they do. |
@lordcris I think the player is canceling the request and issuing a new request, it looks legit.
The thing I've noticed was that your master playlist seems to be malformed, all bitrates qualities are pointing to the same quality (1080p), making the adaptation stream not work properly. For instance you have a 426x240 pointing to a 1080p and so on and so forth.
I think, it is trying to download multiple times the same chunk mostly because all qualities are the same single bitrate (therefore player will try to download 1.ts from multiple qualities, trying to adapt, ) you can either solve this issue, giving each bitrate its real chunk list or just point to the 1080p. |
I could reproduce it here, pasting the log for future reference. I'm gonna try to see what's happening.
|
It seems that the player is falling on a non-fatal error on hls.js and it's retrying forever (or at least many and many times) to recover. |
The hls.js error is a non-fatal "fragLoopLoadingError" |
I could reproduce it on hls.js demo page http://dailymotion.github.io/hls.js/demo/ I think this is not a clappr's problem and maybe not even a hls.js problem, it seems like a problem on your stream creation. @mangui what are you thoughts on this problem: hls.js keeps retrying to download the same .ts files over and over again. Steps:
@clappr/core Or maybe we should stop retrying after X times of a non-fatal error too. (and zeroed this X time on time_update event) You can try to force the flash usage: plugins: [Clappr.FlasHLS] |
I see. It's a stream generated using wowza media server. Do you think it's related? |
I think it is... mostly because I never faced such thing and if you use a stable stream of hls (ex: http://www.streambox.fr/playlists/x36xhzz/x36xhzz.m3u8 ) you probably will not be able to reproduce the same error. (I could not) What's the source are you using to generate this hls? (rtmp, mp4... is it in your hand? can you run a mediainfo or any other tool to help understand the problems with this input??) I don't know much of wowza to help you though. |
I get this error on a livestream, playlist generated by nginx-rtmp. Other On 24 April 2016 at 12:09, Leandro Moreira notifications@github.com wrote:
Stack is the new term for "I have no idea what I'm actually using". |
@DavidVentura it's hard to compare one player with another, for instance VLC plays almost anything it can, it "ignores" errors and even intelligently guesses things to make the video If we're able to reproduce this issue and we think this is a playback problem, we should open an issue on hls.js project. What do you think? |
this is the mediainfo of the file mediainfo Youre.the.Worst.S01E10.Fists.and.Feet.and.Stuff.1080p.WEB-DL.DD5.1.H.264-NTb.mkv Video Audio Text I send it to wowza using this command: ffmpeg -re -i Youre.the.Worst.S01E10.Fists.and.Feet.and.Stuff.1080p.WEB-DL.DD5.1.H.264-NTb.mkv -vcodec libx264 -preset veryfast -maxrate 5000k -bufsize 10000k -acodec aac -b:a 128k -strict -2 -flags +global_header -g 48 -f flv "rtmp://_:_@wowza2.atanassov.net:1935/myliveorigin/mystream" then the mediaserver transrates it in the stream you are seeing ( with the DVR option enabled) |
Try to add a gop for each 30 frames |
Can you test with this live stream? I'm seeing the 'bug' with clappr. It'll be up for about one hour and a half, after that I can reset it if you ask. The playlist seems fine.
Testing on hls.js I see 'gaps' between segments. On every gap the bug occurs, I can manually skip ahead of the gap and the video works |
Looks like it has something to do with the hls.js version being used. Can you upgrade hls.js to 0.6.1 on clappr? |
@DavidVentura nice catch :) I don't know since it's a pre-release build I don't feel comfortable, what do you think @clappr/core ? |
I agree @leandromoreira I don't think we should use the pre release because it's not been as well tested as the major version. It sounds like a bug though so @mangui might be able to backport the fix into v0.5.x if you create an issue with hlsjs. the other option is that you build clappr manually with 0.6.x by updating the package.json before you |
I suppose we'll migrate when makes sense :) |
Hi, I reach here with similar Issue on liveStreaming... after test on Dailymotion demo page, all works well with current stable relase of hls.js Some plans to upgrade? |
@cdgraff yeah we're planning to do a major upgrade that should include this (we'll try to organize and follow a flow of tasks here https://github.com/clappr/clappr/projects/1 ) |
Hi, I'm facing the exact same issue, i'm using NGINX + RTMP module and clappr. My stream has EXT-XDISCONTINUITY and after this the player just starts trying to get the same 27.ts and 28.ts over and over again. #EXT-X-DISCONTINUITY Does anyone know a solution for this ? in vlc it plays fine. |
Browser: Chrome/Firefox
OS: Linux
Clappr Version: latest from cdn
Steps to reproduce:
When playing video I get lots of request for the same files yet the video doesn't seem to play (plays, finishes a segment, gets stuck for 1-2 segments, plays a single segment... )
Did you try to reproduce this issue at http://cdn.clappr.io/: Yes, same thing
Playing the m3u8 file on mpv/vlc works wonderfully. Looks like a player issue..
Edit, this doesn't happen (multiple requests per file) on https://cdn.jsdelivr.net/clappr/latest/clappr.min.js
but does on
http://cdn.clappr.io/latest/clappr.js
The text was updated successfully, but these errors were encountered: