-
-
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
Some videos won't play, missing codec? #2228
Comments
Can't be, the video would fail to be displayed and end up with an exception if no supported codec was supplied. |
Any other ideas for this strange behavior? Is it perhaps possible an exception does indeed happen but ends up suppressed (via an empty |
It could be your android system. |
It could be the hardware video decoder that cannot handle the video steam properly. Particularly when playing the Try test it by setup |
Made some interesting discoveries. I installed MX Player as suggested and set NewPipe to use external player. Videos that work normally in NP work just fine in MX as well, and videos that don't work in NP don't work in MX either. MX just goes through available codec categories (SW, HW, HW+) and finally displays "Cannot play this link". Then I thought of something. My default resolution in NP is set to 480p. Just for testing I changed it to 720p. Suddenly all the videos work, both in NP and MX. Not sure what to make of that. Still think there must be a better way to handle not being able to play a video instead of just showing the loading spinner forever. I'm leaving my default at 720p for now at least. |
Ah that was the missing part. Yes 420p also failes on my device. |
same problem. |
Have this issue too, android 4.4 (honda civic head unity) |
#2415 is probably related |
Duplicate of #2415 |
It gets as far as showing the thumbnail/description/comments screen. But when I tap on the video, it just shows the loading spinner forever. This happens consistently on Android 4.4 but seems to work on Android 7.1. Maybe a missing system codec on older Android versions? Any way to remedy this, or at least detect this condition and show a warning?
Examples:
The text was updated successfully, but these errors were encountered: