2024-02-01, 03:54 AM
I have managed to capture more logs related to this. Perhaps this is a bug with ExoPlayer on the Android TV client. If it is, I can create an issue on Github. However, I do not know for certain whether it is a bug as I do not really understand what is happening in the logs.
I've tested with two different series episodes of anime with my Android TV player set to ExoPlayer. Both of them have .ASS subtitles. The only difference that I can see is the amount of audio, subtitle tracks, and possibly fonts between them.
The Baki episode produces 2 different transcode logs before I backed out of ExoPlayer. If I did not back out, it would continually try transcoding until I manually backed out. I found it does not matter whether or not the ffmpeg process returns a 0 or 137 code. During this time, no playback error seems to be reported in ExoPlayer, the screen is black, the progress bar does not move, and the play button is in the "paused" state.
The Attack on Titan episode produces 2 different transcode logs as well but it actually plays.
I have tried to remove the excess audio and subtitle tracks in the Baki media using MKVToolNix, but the problem persists. Using LibVLC is not ideal as the subtitles are never shown even with the Burn subtitles option set to "All".
What is the difference between these two pieces of media to cause such consistent behavior? Is there any reason that two transcode logs are generated for the media that actually plays? For almost everything else that is not anime in my library, there is only ever one transcode log generated.
jf-server-log.txt (Size: 24.95 KB / Downloads: 103)
exo-1-aot-transcode-log.txt (Size: 16.79 KB / Downloads: 97)
exo-2-aot-transcode-log.txt (Size: 26.79 KB / Downloads: 74)
exo-1-baki-transcode-log.txt (Size: 23.75 KB / Downloads: 86)
exo-2-baki-transcode-log.txt (Size: 21.62 KB / Downloads: 94)
I've tested with two different series episodes of anime with my Android TV player set to ExoPlayer. Both of them have .ASS subtitles. The only difference that I can see is the amount of audio, subtitle tracks, and possibly fonts between them.
The Baki episode produces 2 different transcode logs before I backed out of ExoPlayer. If I did not back out, it would continually try transcoding until I manually backed out. I found it does not matter whether or not the ffmpeg process returns a 0 or 137 code. During this time, no playback error seems to be reported in ExoPlayer, the screen is black, the progress bar does not move, and the play button is in the "paused" state.
The Attack on Titan episode produces 2 different transcode logs as well but it actually plays.
I have tried to remove the excess audio and subtitle tracks in the Baki media using MKVToolNix, but the problem persists. Using LibVLC is not ideal as the subtitles are never shown even with the Burn subtitles option set to "All".
What is the difference between these two pieces of media to cause such consistent behavior? Is there any reason that two transcode logs are generated for the media that actually plays? For almost everything else that is not anime in my library, there is only ever one transcode log generated.
jf-server-log.txt (Size: 24.95 KB / Downloads: 103)
exo-1-aot-transcode-log.txt (Size: 16.79 KB / Downloads: 97)
exo-2-aot-transcode-log.txt (Size: 26.79 KB / Downloads: 74)
exo-1-baki-transcode-log.txt (Size: 23.75 KB / Downloads: 86)
exo-2-baki-transcode-log.txt (Size: 21.62 KB / Downloads: 94)