-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[YouTube] Videos take a while to load and buffer frequently on some resolutions #10183
Comments
This was a previous issue which has now resurfaced. I have previously posted this bug on #6424 . Now for me it only buffers while viewing in 720p and buffering goes away when changing any other resolution even higher ones. One connection I found is that the videos that has 60 fps format are having this problem in 720p. However 720p60 is working without buffering. Dk if it's related. And changing to 3gp or WebM is a temporary band aid which may not work always |
I can confirm that on the Fire Stick 4k Max the buffering issue happens at 720p/30, as that is my default resolution for YouTube stuff, and when I switch to 1080p the problem goes away. This is a reasonable workaround but I tend to run up against my 1.28TB monthly limit so hopefully the 720p issue can be resolved. |
I typically watch videos at 1080p, but see this issue at 720p and 1080p, 30 or 60. My current work around is to download the videos, but to get decent d/l speeds i have to use all 32 threads on my s20fe. |
Ok so today I thought I would see if the issue is still present, and to my suprise videos are no longer buffering. So what ever YT broke a few days ago it appears to have been fixed? I will continue to test till the end of the week, and then mark the issue as resolved if applicable etc. |
I'm also experiencing the buffering issue with 720p on both of my devices. |
Experiencing the same issue, though I'm glad I checked here for a workaround. Changing the video quality is also fixing the issue on my end. |
I have the similar issue, just see the comments being loaded and then nothing, even the network activity stops. The change to other resolution for streams doesn't help. |
Ok so "I think" I found whats causing the buffering for me atleast, and I only found this by accident. I have "adaway" installed for blocked ads, when I want to installed anything from google play (because I have connectivitycheck.gstatic.com blocked), I have to disable it temperarily. It was I forgot to re-enable adaway and then to user newpipe that it dawned on me. With Adaway enabled newpipe will as per the OP get stuck buffering a video what whats seems indefintly. If I close newpipe and disable adaway and open newpipe the buffering issue goes away. Downloading videos works regardless if adaway is enabled/disabled, however I think download speeds are reduced with adaway enabled. I had had Adaway installed for years like this, and newpipe has only recently started acting up. Checking the manual list fo blocked urls the one I have temp undirected is " youtubei.googleapis.com ". With Adaway enabled the aformentioned url block disabled newpipe works as expected. |
I use nextdns and youtubei.googleapis.com is not blocked. but issue still persists. |
Fixed by TeamNewPipe/NewPipeExtractor#1076. |
Checklist
Affected version
0.25.1
Steps to reproduce the bug
Open any subscribed video and its will take a while to load the thumbnail and then after loading it will get stuck on buffering after a few seconds.
Expected behavior
Open any subscribed video and it almost immediatly load the thumbnail and then start playing the video.
Actual behavior
Open any subscribed video and its will take a while to load the thumbnail and then after loading it will get stuck on buffering after a few seconds.
Screenshots/Screen recordings
no screenshot/recording its a streaming/buffering issue.
Logs
no log, its a streaming/buffering issue.
Affected Android/Custom ROM version
Android 11
Affected device model
S20FE
Additional information
This only stated happening as of UK lunchtime yesterday.
The text was updated successfully, but these errors were encountered: