-
-
Notifications
You must be signed in to change notification settings - Fork 515
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
Crush when 'Pass Direct Path for external player' is enabled and starting a video with VLC #2269
Comments
Thanks for the report. I made some changes that should fix this issue in the next beta. Let me know if it doesn't. |
Unfortunately the issue is still present in beta v3 Here is a crash report:
|
Thanks for the update. We've discussed this and apparently it was decided a while back that the direct path option is deprecated and will be removed at some point. That's why I've opted to remove the feature from the client as it's broken now anyway. Next beta should work again (behaves just like now with the option turned off). |
Okay, let me raise a concern about removing this option. |
I'm sorry that this breaks your usecase. I'd advise to revisit your library structure so Jellyfin can correctly find the subtitle files. You can find our recommended structures in the documentation:
Most organizing software should be able to name all files correctly, it just might need some additional configuration. If you need help with that our community will be able to help on Matrix/Reddit/Discord/etc. |
Its not that Jellyfin does not find the subtitle files, but it just doesn't forwards it to external players. Only way I could circumvent this is to manually load the sub-file, but for this, VLC need the exact network share address where my movie file is, not an http URL Please reconsider deprecating this feature. |
So the problem isn't the deprecation of passing the direct path, it's the lack of external subtitle support in a specific video player app (VLC). At that point you should switch to another external player, embed your subtitles or just use the built-in player. |
Okay, these are valid recommendations. |
Jellyfin is a media server, not a media browser. It's supposed to always serve the media via Jellyfin itself. |
Describe the bug
Since the update to v15 whenever I open a media file I get 'Ops something went wrong..." error.
After some debugging I found out, if I turn off the Preferences -> Playback -> Pass Direct Path for external player the error goes away.
Logs
client: Jellyfin for Android TV
client_version: 0.15.0-beta.1
client_repository: https://github.com/jellyfin/jellyfin-androidtv
type: crash_report
format: markdown
Logs
Stack Trace:
Logcat:
App information
App version:
0.15.0-beta.1
(150001
)Package name:
org.jellyfin.androidtv
Build:
Build config:
Device information
Android version:
9
Device brand:
Xiaomi
Device product:
oneday
Device model:
MIBOX4
Crash information
Start time:
2022-11-16T19:36:25.592+01:00
Crash time:
2022-11-16T19:38:51.875+01:00
Application version
0.15.0-beta.1
Where did you install the app from?
Google Play
Device information
Xiaomi Mi Box S
Android version
Android 9
Jellyfin server version
10.8.7
The text was updated successfully, but these errors were encountered: