-
Notifications
You must be signed in to change notification settings - Fork 484
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
Image freeze after 2 seeks #2177
Comments
Have you tried playing this stream without tunneling by any chance? Tunneling moves a lot of the playback logic, AV sync and decoding to a part of the output device that isn't covered by Android tests and reimplemented by every device. This usually causes a lot of compatibility issues and we only recommend tunneling on a device-by-device basis once you tested your streams work on that particular device. |
So I don't reproduce the problem without tunneling. But I can provide one more piece of information since the ticket was opened: during the 20 seconds when the logs indicate changes to isLoading (true-false), the image is frozen but the sound continues to play. And after these 20 seconds, everything stops. A new seek resets the playback. |
The problem can easily be reproduced on the media3 sample when enabling tunneling. |
In this case, it unfortunately just sounds like a device-specific issue with the tunneling implementation we can't fix. You'd need to reach out to the device manufacturer and ask them to fix the issue or (more realistically) just disable tunneling on these devices in your app. |
Version
Media3 main branch
More version details
1.6.0-alpha03
Devices that reproduce the issue
Vantiva Quartz
Vantiva Sapphire
Devices that do not reproduce the issue
No response
Reproducible in the demo app?
Not tested
Reproduction steps
Play a DASH stream with Dolby and tunneling.
Make 2 fast seek back (10 seconds).
Expected result
Vidéo plays after the 2 seeks
Actual result
Sometimes, the playback freeze on a frame.
Media
Here's the EventLogger logs :
Bug Report
adb bugreport
to [email protected] after filing this issue.The text was updated successfully, but these errors were encountered: