-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Media 3 Exoplayer bug fix (Android 14 / API 34) #44
Comments
Exact issue: Which seems to be related to the calculated video width & height does not match the actual one. |
facing same issue here |
I could see the player worked a few times by only keeping the basic code to set up the player. However, the result was inconsistent and sometimes did not work. I tried to forcefully invalidate the view (because, obviously, it is due to the player getting the wrong screen dimensions) but could not fix it. As I mentioned in the Google's issue ticket - since the same piece of code and the library worked on previous Android versions, it can be difficult to say our code / the exoplayer has a bug. If that's due to OS changes, it can be difficult for us to fix/diagnose. Right now, I can only leave this issue open. |
For me it work with a condition. If i'll use RESIZE_MODE_FIXED_WIDTH for example i have to set the container with fillMaxWidth() and not fillMaxSize() |
I'm having the same issue with stretched video; additionally, for me it seems like |
For this code base, I have been able to confirm two findings:
Therefore, I believe something is wrong when the player tries to get/calculate the view's screen size on API 34+. If there is a bug, it might be a compose/ other OS bug rather than the exoplayer library's since, again, the same player works well on API 33. This makes it difficult to investigate further. Another possibility might be due to my complex activity setup—I use Single Activity to implement the player and PIP, so it might be my fault for accidentally overriding some configuration changes. I plan to comment out all other extra features in my project to see if the player would work again. |
Tested again by elevating media3 to 1.4.0-alpha02. As expected, this does not solve the problem. |
We are getting closer to the root cause (that Google has yet face the reality): Video is cut on the edge when using Compose and uses RESIZE_MODE_ZOOM - Only Android 14 |
Root cause identified. The workaround will be available in media3 We don't have access to
|
I'm glad you found the issue and look forward to this workaround. Thanks for your efforts regarding this. |
…-android-14 (#44) media 3 exoplayer bug android 14
The update to |
But you still need |
Setting |
Same here. I have the same issue with the version Btw, this problem happens only with 2 of the sample video I am working with. It does not happen with a third video with better quality. Maybe it is because the video couldn't stretch to the whole screen? I am wrapping the player over a vertical view pager. Another interesting finding is that while the video of the first page works fine, when I scroll down and scroll up (go to another video and go back to it again), the same video will resize and shrink. |
Thank you for your sharing. However, this is not a place to report any issues if you believe the root cause is different. I would suggest you report it back to Google for your case. |
We should have got most of the PIP implementation right, but we'd better follow the official doc for every minor step to make sure the implementation is right and stick to the recommendations.
On Pixel 7 the player looks to scale the video 1:1 then crop 50% vertically. That's a sign shown when we disabled the control display.
The text was updated successfully, but these errors were encountered: