-
Notifications
You must be signed in to change notification settings - Fork 264
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
Playback freeze after auto stream quality change to audio only track and wan't recover. #466
Comments
@mangui did you checked that? |
no. not yet |
OK. |
@fixedmachine Christmas gift is a bit late this year :-) |
@mangui thanks for the fix. The freezing after switching to audio only stream is not happening so often, but it's still there I'm afraid. Stuttering and artifacts issues with this stream still exists. I've got feeling that there is also quite a big desync between audio and video after switches. There is new problem:
I'm testing with |
Hi @fixedmachine could you provide debug/debug2 logs for each of these new issues ? |
@mangui sure I'll prepare it. |
Hi @mangui,
I've got another case when the playback is stopped and wan't recover. This applies to v0.4.4.16.
It happens when there is an auto switch from a/v to audio only stream. I'm experiencing this behavior when I'm throttling bandwidth with Chrome Dev Tools up and down. The switch down to audio only stream causing freeze. Player is in 'buffering' state. CPU usage is enormously high and everything is slowed down and after some time it causing flash plugin crash (but this is caused by the amount of logs generated with debug version of flashls). There are only 1-2 audio *.ts fragments downloaded and that's it. When the bandwidth throttle is released, switch up never happens. I think that most important cue for you in this case will be this fragment of log:
It's possible to recover playback by seeking through the video or manual quality change. After recover, audio stutters (the same fragment is played 2 times). Sometimes there are artifacts (black screen with which never goes away.
What's interesting this is only applicable to auto bitrate switch. When the switch to audio only track is done manually everything goes fine in both ways (up/down).
Here is the screening illustrating this issue:
https://youtu.be/n3P7BD3SDZY
Full debug logs from the same session as the screening above:
https://www.dropbox.com/s/25ev783f5ry5x0u/flashls-debug-log-vod-freeze.log?dl=0
You can play with this stream here:
http://flashls.wlodkowski.net/osmf/GrindPlayer_vod_freeze.html
The text was updated successfully, but these errors were encountered: