Yesterday, 03:25 PM
(2025-11-01, 09:19 PM)Necromind Wrote:(2025-11-01, 03:36 PM)B C Wrote: It's more about not wanting to transcode, due to it not working great all the time, and storage is so cheap, I'd rather just have 1080p/4k versions since I watch things all over the place (work, travel, etc)
Well, wasted storage is the most expansive one for sure
What you like to do is simply not (yet) supported by Jellyfin.
They put a lot of efford in the transcoding feature. Even by changing ffmpeg's code for better integration.
I constantly use it, even on ridiculous low bit rates while on travel. The results are excellent.
Sure, there are possible problems with HDR/Dolby Vision and such encodings. But Jellyfin supports a proper tone mapping, which must be activated.
I just try to explain why such a "file mapping" function is not part of Jellyfin. Because of it's excellent transcoding features it's not needed in my opinion.
Well, an encoding/decoding hardware is required. Many people let run Jellyfin on low-end hardware or a very old one, with no such capabilities.
I use a current Intel iGPU and it works crazy fast with excellent results. But this may vary depending on the type of files in the library. An Intel Arc card will do the job fine aswell.
Beside that the main info here is: Such a function is not (yet) existent in Jellyfin. And I don't believe it ever will be...
You may file a feature request about it, tho
Weird how it works "out of the box" fine on Emby and Plex, strange how this wasn't kept as a basic feature from the Emby code fork years ago. Ah well, I'll revisit Jellyfin again in a year or two and see if it works lol.