-
-
Notifications
You must be signed in to change notification settings - Fork 495
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
0.17.1 player crashes on DTS 7.1 direct playback #3868
Comments
Please share the app crash logs. |
Not really sure how to get them since it's on the chromecast. The server side logs don't show the crash they just show the disconnect from the media when it crashes. |
When the app crashes it always reports those logs to the server, available in the dashboard. Without logs I can't do much. |
Hmm, to be clear the entire app isn't crashing just the player. "encountered too many errors" is the toast. Does the player crash report to the server? Can you point me to where that is? I'd be glad to provide it if it's something I have. |
My logs look like below, to me seems like all the server knows is playback stopped.
|
I also just noticed that DTS bitstream option is now missing. I still see a DD bitstream option though. Could this be the root of the issue? |
Then it is not a crash, just a playback failure. In which case you used the wrong template and didn't provide any media info.
This option did nothing and was therefor removed. The app claims DTS support when the audio behavior is set to direct stream. |
Sorry... wasn't intentional. How would you like me to proceed? Should I provide more info in this thread or would you like to delete/close this and I'll try again with the proper template? |
I am facing the same issue on 0.17.3 and server version 10.9.8. Here are my logs. Exception which causes playback error in ExoPlayer:
Media info:
This movie contains also a stereo track in Italian, but I'm not able to select it because the player refreshes completely after an error. No playback error occurs when preferring extension renderers (see 186ab31; don't know if this fixes OP problem too). This also avoids audio transcoding on the server. This error line in the above log
seems to be irrelevant, becuae it's there also when the movie plays correctly. |
Similar issue with playback on the Android TV app since updating. Other clients work fine. This is happening on two different "Chromecast with Google TV" devices.
Jellyfin server 10.9.9 other content plays fine though I know that these particular episodes have a subtitle codec that my device doesn't support (special fonts? I guess? It's ASS subtitles) so they are always burned in, when it works. It also seems that if I start the episode on another device, then resume from the ATV, it works. EDIT it's not exactly the same but I think there's an overarching issue in 0.17 where media that was previously transcoded is now unsuccessfully trying to DirectPlay. Opened #3898 (thanks rickysixx) |
I think your issue is off topic here @anthonymag. I do not see any error in your logs and I highly doubt that anime use DTS as audio codec. I guess it's better if you create a new issue (maybe there might be some already regarding ASS subtitles though). |
Are you able to direct play DTS audio on 0.16.11 using ExoPlayer (not LibVLC)? |
Both ExoPlayer and LibVLC worked without crashing in 0.16, earlier builds in ExoPlayer crashed with DTS very similarly to this, but I don't recall what build as it wasn't big deal with LibVLC as a fallback. |
Closing as duplicate of #3896, as they appear to be the same issue. |
Describe the bug
Changing audio from direct to downmix to stereo allows successful playback. Media with other audio formats work without error.
Prior to the latest release I could also select LibVLC for playback when Exoplayer failed to play media. However that option seems to have been stripped out in the latest build.
Logs
No response
Application version
0.17.1
Where did you install the app from?
Google Play
Device information
Chromcast 4k
Android version
12
Jellyfin server version
10.9.9
The text was updated successfully, but these errors were encountered: