Closed mark-weber closed 3 years ago
These error messages (com.google.android.exoplayer2.upstream.HttpDataSource$InvalidResponseCodeException: Response code: 404) are fairly commom in the underlying Exoplayer implementation. They usually indicate corrupt subtitle data or a problem accessing the server. We're not seeing the same issue in the web player, as I understand it. I will investigate further...
Oleks Z to check whether changing permissions will resolve this
@sinewave440hz please try this URL to confirm that the issue is not on the player side:
https://stream.mux.com/NbkiX02nuM8oFYI00b3HlxPi3TyqVJCrH3U01AsdWpggvI.m3u8
We have confirmed that there is no issue with the player. Not that we're seeing subtitles, but that's a problem with the actual displaying of the text. I am in the process of re-working the Android bitmovin component to fix that (need to embed the player and subtitle views in a layout container, quite simply).
About half day remaining.
Emily to provide design details for subtitle display.
When I started the video on bitmovin player and chose a subtitle track I got an error. "Input does not start with the #EXTM3U header." I guess it is related to bitmovin players manifest encode.
I need the link to the correct manifest file with subtitles for checking and testing playing video with subtitles on Android bitmovin player. I need to be sure that that link works on web bitmovin player for example.