-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Automatically show closed captioning/hard of hearing track based on accessibility settings #5749
Comments
Thanks for the detailed description of the problem. I think there are two enhancements in here that need to be addressed:
Does that summarize your proposal correctly? |
Yes, that's sounds like it would solve my problem. Just a clarification for one scenario: |
Yes, that's my understanding of the |
Great! |
It should also be possible for apps to do everything that they need in the case where they get subtitle/caption settings from somewhere other than So I think |
This is auto-enabled now and also be set triggered manually by using |
…tings This option allows to set the preferred text language and role flags based on the user's accessiblity captioning settings. Issue:#5749 PiperOrigin-RevId: 270233205
Hi,
I'm using ExoPlayer for playback of DASH-content. I'm looking for a way to
The DefaultTrackSelector has an API to setPreferredTextLanguage which works fine for displaying subtitle tracks.
However, my app needs to support both subtitles and closed captions and my problem is that if I use setPreferredTextLanguage it will always display the closed captions since these are using the same language code.
The CaptioningManager, https://developer.android.com/reference/android/view/accessibility/CaptioningManager, offers an API to read accessibility settings. From what I understand, ExoPlayer uses this setting to determine the styling of the closed captions but not to determine whether text should be shown or not.
Is there any way to get the ExoPlayer automatically enable closed captioning based on accessibility settings? And that setPreferredTextLanguage only applies to subtitles and not closed captions?
Thanks,
Martin
The text was updated successfully, but these errors were encountered: