Closed dewijones92 closed 1 year ago
Does it work on the computer if you try in browser? I think this is something we have solved on the next version of the web interface/server, where we send the wrong track index (it's off by one).
@anthonylavado my ras pi is far too slow to encode it - required to play on firefox. Sorry It's work correctly on my jellyfin android app - plays the correct language
Same issue as mine: #85
I experience the same problem on the most recent version on WebOS. Even in spite of me manually changing the audio and subtitle track to a different language.
Does it work on the computer if you try in browser? I think this is something we have solved on the next version of the web interface/server, where we send the wrong track index (it's off by one).
https://github.com/jellyfin/jellyfin/pull/8298 Is this the PR that solves it?
EDIT: From the looks of it no. Updated to the latest version and still no change.
Does it work on the computer if you try in browser? I think this is something we have solved on the next version of the web interface/server, where we send the wrong track index (it's off by one).
jellyfin/jellyfin#8298 Is this the PR that solves it?
EDIT: From the looks of it no. Updated to the latest version and still no change.
@tomikaka22 I think it is a webos client issue rather than a server side issue. As my android jellyfin client works correctly
The WebOS client is a wrapper around the webUI. The android client is it's own thing with a separate codebase, and separate developers.
@anthonylavado mentioned in #85 too, that something is wrong with the track indexes, and that it'll be fixed with an update to the webUI (Which WebOS is also using).
As far as I know, in WebOS 3.x and below the WebOS player can only reproduce the first audio track of a media file. If the file is re-muxed (because of incompatible container, for example) only the chosen audio track is included in the media stream and track selection works fine. However, for direct stream, the player reproduces always the first track, no matter which one gets selected before or during the playback. Could this be the issue you are seing?
With Emby, if the client is WebOS and the user selects an audio track that isn’t the first, the stream gets re-muxed instead of directly streamed. Is it possible to implement the same in Jellyfin?
I have the same problem on my C1 playing 4K HDR directly. Reported to Jellyfin Bug Report.
I have same problem on C1 with dolby tracks
Everything works fine using WebOS Browser on my C1. HEVC is playing directly and Dolby Atmos is transcoded to AAC. Perfekt. I donnot use Jellyfin App anymore.
I'm running into this on 10.8.9, it shows playing the default audio track but instead I always get some other language.
Only way ive found around it is turning on subtitles. This seems to work every time.
I just installed Jellyfin on my webOS 4 TV and happened to me with one specific show where the audio I wanted was DTS, so I just added supportsDts: false
here and it seems to be working fine now.
It seems like jellyfin-web is only saying not supported on webOS 5+: source code
This might be totally unrelated to DTS support as I think there would be no audio otherwise.
Other shows/movies that have been digitalized with a different configuration, using a different audio codec and they seem to be working fine.
This might be totally unrelated to DTS support as I think there would be no audio otherwise.
From observation, if the first audio track is selected, Jellyfin plays the first supported one. So if the first one is not supported, you could hear the second one.
I just installed Jellyfin on my webOS 4 TV
Self-built? AFAIK, we don't have a webOS 4 app in the store.
I think it still happens regardless of DTS support.
There's a script that enables regular DTS files to be down mixed to stereo and be output to the speakers. For this reason I have a fork of Jellyfin-web that disables the WebOS 5+ check, and it still sometimes switches up the audio tracks.
I just installed Jellyfin on my webOS 4 TV
Self-built? AFAIK, we don't have a webOS 4 app in the store.
At first I installed the one that dev manager offers by default then self built after I modified it.
Edit: it's a 32LM6300PLA, which should have DTS support according to LG's site.
I can confirm this issue is still present with Jellyifin app version 1.1.2 on WebOS 5.4.2-2601. No problem using WebOS browser. No problem using Edge browser on Windows.
I experienced the same issue on a LG OLED55A19LA. But I can reproduce it using the WebOS browser aswell!
Seems like its an issue with direct media playback since as soon as I get Jellyfin to start transcoding the content the issue is no longer existent (which makes sense since only the selected audio track will be kept when transcoding). I could not reproduce it yet on any other device since all of them require transcoding right now and getting anything to direct play is surprisingly difficult.
Jellyfin Server: 10.8.13 Jellyfin WebOS App: ? not sure, installed from WebOS Appstore on 2. Jan 2024 WebOS: not sure where I can find it, TV says Software Version 03.40.70 (nothing about a WebOS version anywhere)
I have the same issue on a LG Oled C2 using the latest 1.2.2 version of Jellyfin. Thing is, there is the exact same issue on Emby so there's a flaw somewhere when indexing the audio track
Hello
First I need to thank the devs for such an amazing app :) I do however have a problem I have a cat video that contains 2 audio streams - English and french The TV always plays the French audio stream - despite choosing English. FYI I don't encounter this on my Android phone client - which leads me to think it's a bug with the WebOS Jellyfin app?
Server logs
ffprobe
jellyfin version