2 hours ago
(This post was last modified: 2 hours ago by dudechill8D. Edited 2 times in total.)
I have recently discovered a strange issue that I believe to be a bug.
The way I have my library set up, I have MKVs of each film, and these files have the original encoding that the original copy had. I have another version that I have re-encoded to be more likely compatible with the devices I use and use less bandwidth/storage. I have gotten my library set up correctly so that these versions are listed under the same title.
If one of these MKVs is under it's own title (with no other versions sharing it) transcoding works perfectly on all devices.
If the MKV is under the same title as another version I have re-encoded and I try to play the MKV, jellyfin for chrome gets stuck trying to load. But this problem doesn't exist for Firefox. I have updated my browsers. I am on linux, but I tried edge in windows 11, and it has the same problem as chrome (makes sense). Also, it is only the case for most of my MKVs, but not all of them.
I have turned on debug mode and collected logs for Firefox and Chrome when a particular MKV is and isn't sharing the same title with another video file. I deleted logs for before and in-between tests for reading convenience. (This problem is very consistently reproducable for me)
Jellyfin-MKV-Playback-Debug-Logs.zip (Size: 92.29 KB / Downloads: 3)
-----------------
I am running server, web, and build version 10.11.3, and it is on a fresh install of debian trixie. I am using the debian repo. I tried setting up hardware acceleration after encountering this problem because I think I read somewhere that it had a small chance to fix random transcoding issues (source lost) but didn't succeed in doing so. But I'll leave that to a different thread if I care enough.10.11.310.11.3
What I expect: When an MKV has it's own title, there are options to select the audio track and subtitle track. But when selecting it as an alternate version, those options don't show up before I press play or in the player like they usually do. I'm not sure if this would change if the MKV were made the default (which if more testing is needed, I can try that). My best guess for it breaking on only most of my MKVs is maybe something to do with subtitles? I really have no idea though, just a wild guess. Should I post this to github? I'm hesitant because I've never done that before. If this is ok too or this problem is due to my ignorance, then great.
Edit: I should add that the same behavior exists on jellyfin for android (although expected because I'm pretty sure that's just a web app). In findroid, it plays, but only the audio, the video is just a black screen. And on a Samsung tv we have, it works just fine in the internet app.
The way I have my library set up, I have MKVs of each film, and these files have the original encoding that the original copy had. I have another version that I have re-encoded to be more likely compatible with the devices I use and use less bandwidth/storage. I have gotten my library set up correctly so that these versions are listed under the same title.
If one of these MKVs is under it's own title (with no other versions sharing it) transcoding works perfectly on all devices.
If the MKV is under the same title as another version I have re-encoded and I try to play the MKV, jellyfin for chrome gets stuck trying to load. But this problem doesn't exist for Firefox. I have updated my browsers. I am on linux, but I tried edge in windows 11, and it has the same problem as chrome (makes sense). Also, it is only the case for most of my MKVs, but not all of them.
I have turned on debug mode and collected logs for Firefox and Chrome when a particular MKV is and isn't sharing the same title with another video file. I deleted logs for before and in-between tests for reading convenience. (This problem is very consistently reproducable for me)
Jellyfin-MKV-Playback-Debug-Logs.zip (Size: 92.29 KB / Downloads: 3)
-----------------
I am running server, web, and build version 10.11.3, and it is on a fresh install of debian trixie. I am using the debian repo. I tried setting up hardware acceleration after encountering this problem because I think I read somewhere that it had a small chance to fix random transcoding issues (source lost) but didn't succeed in doing so. But I'll leave that to a different thread if I care enough.10.11.310.11.3
What I expect: When an MKV has it's own title, there are options to select the audio track and subtitle track. But when selecting it as an alternate version, those options don't show up before I press play or in the player like they usually do. I'm not sure if this would change if the MKV were made the default (which if more testing is needed, I can try that). My best guess for it breaking on only most of my MKVs is maybe something to do with subtitles? I really have no idea though, just a wild guess. Should I post this to github? I'm hesitant because I've never done that before. If this is ok too or this problem is due to my ignorance, then great.
Edit: I should add that the same behavior exists on jellyfin for android (although expected because I'm pretty sure that's just a web app). In findroid, it plays, but only the audio, the video is just a black screen. And on a Samsung tv we have, it works just fine in the internet app.