2024-07-24, 01:00 PM
(This post was last modified: 2024-07-24, 01:02 PM by TheDreadPirate. Edited 1 time in total.)
Huzzah! You read documentation and found my bug report. You're my new favorite user.
One of the quirks I found with the 6.8.0-38 issue was that transcodes that scaled the resolution were the affected (4K to 1080P or 1080P to 720P). But transcodes that did not scale resolution were not always affected. I didn't test it that much before rolling back.
One of the two patches to fix this issue was already scheduled to be incorporated into -40. But the second patch that fully fixes the issue won't make it until the next kernel release.
One of the quirks I found with the 6.8.0-38 issue was that transcodes that scaled the resolution were the affected (4K to 1080P or 1080P to 720P). But transcodes that did not scale resolution were not always affected. I didn't test it that much before rolling back.
One of the two patches to fix this issue was already scheduled to be incorporated into -40. But the second patch that fully fixes the issue won't make it until the next kernel release.
Jellyfin 10.10.3 (Docker)
Ubuntu 24.04 LTS
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)
![[Image: GitHub%20Sponsors-grey?logo=github]](https://img.shields.io/badge/GitHub%20Sponsors-grey?logo=github)
Ubuntu 24.04 LTS
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)