-
-
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
Update to ExoPlayer 2.12.3 #5457
Conversation
@Redirion Also, I think media2 only supports API 21 and newer, so that would require dropping KitKat support, which will definitely cut off a small chunk of users 🤔 |
@TacoTheDank we will be forced to drop KitKat support sooner or later anyway due to OkHttp 3.12.x being discontinued on December 31, 2021 |
@Stypox All okay with me lol, though I do feel kinda bad for those older phone users. The only option they really have left now is SkyTube or using a mobile browser. (Also, you should edit your comment to specify the 3.12.x LTS branch, because you scared me with "OkHttp being discontinued" 😰) |
@TacoTheDank do you have a source for the API 21 requirement of media2 for me? I wasn't able to find that info. |
@Redirion I got that idea from the answer here: https://stackoverflow.com/questions/57566102/what-are-the-differences-between-mediasessioncompat-and-mediasession-in-android Perhaps I misunderstood it 🤔 |
found something. According to this website media2 in the current version that is used by ExoPlayer requires API 16: https://androidx.tech/artifacts/media2/media2-session/1.1.0 while the media2 extension of ExoPlayer declares API 19: https://github.com/google/ExoPlayer/blob/release-v2/extensions/media2/build.gradle (this could however be overwritten by our gradle config, if ExoPlayer raises this to 21, as long as media2 stays below 21). |
@Redirion I see... 🤔 Oh btw, ExoPlayer 2.12.0 introduced two convenience methods |
@TacoTheDank they would still be able to use NewPipe legacy |
@Stypox Does Newpipe Legacy not use OkHttp? |
It does, but I think it can be kept or replaced with something else specific to old android versions |
Oh yeah, and that :) |
Is this good to merge? |
@Stypox I am a bit hesitant to merge my own PR. From my opinion I would say this is good to merge. Or would you prefer if we skip ExoPlayer 2.12 and move directly to 2.13? |
Removed a textTrack null check on a now- NonNull method Added a error type switch case (TIMEOUT)
I added a commit with a few style improvements and fixes of warnings. I tested playing some videos and enabling skip silence and everything worked as expected |
Now we seem to have the situation, that we require a third dev to approve this PR as we both contribute to it |
You could always approve each other's changes. :P |
@Redirion Were you ever invited to join the Newpipe channel on IRC? If not, could you please make a Matrix account and join it? |
679bc75
to
2aeccc0
Compare
I just tried but I may not approve my own pull request even though the last commit was not by me |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested again and everything works fine. Thanks :-)
|
Update to ExoPlayer 2.12.3
What is it?
Description of the changes in your PR
Updates ExoPlayer from 2.11 to 2.13
Note that we will have to do another PR to migrate from deprecated mediasession to media2.
However this will most likely require to also rework everything to the new MediaItems instead of working with MediaSources.
For now however this can stay and if ExoPlayer stays being compatible with mediasession we aren't in a rush.
Due diligence