> I didn't like that you can't outright disable transcoding for content served via their app or in the browser.
You can outright disable transcoding. That’s a checkbox in the server option.
> both this and the native Android app do not handle Dolby vision or passthrough atmos content properly
They do out of the box. Never had an issue with either transcoding disabled. If you have properly configured the source content, Jellyfin is just a passthrough for Kodi and content is directly accessed using the network share.
I ran into this with HDR. I have a fork/branch that strips that logic block out and it works great (tldr; video gets transcoded breaking HDR for any transcode reason i.e. audio/subtitle)
I'm not sure what to say. Unless this is a recent change in my experience it does not work as intended. I spent a lot of time playing with the various transcoding settings and per user settings and direct path access or the regular way of accessing files.
I'm happy it worked for you. I have specific content jellyfin doesn't work with where Kodi is fine and I am just sharing my experience with this software package.
For the transcoding setting, they are indeed in the user profile and work since day-1 as inherited from the Emby fork. It does 100% disable all transcoding for this user.
> I have specific content jellyfin doesn't work with where Kodi is fine
Very surprising as Jellyfin is just a passthrough to Kodi. Did you open a bug report?
> I am just sharing my experience with this software package.
Every post here about an open source project be it Firefox or Jellyfin always see plenty of people sharing their experience with it from a decade ago and panning things that actually work. I usually just read them and move on but sometimes I like to give a counterpoint when it’s about a piece of software I consider quite good.
I appreciate it and the civilized discussion! I might need to take another look at the next major version release. The passthrough stuff if objectively easy to check : tv shows hdr/dv logo, receiver tells me the encoding. I wonder if it just slightly overtaxed the tube shield for the latency.
You can outright disable transcoding. That’s a checkbox in the server option.
> both this and the native Android app do not handle Dolby vision or passthrough atmos content properly
They do out of the box. Never had an issue with either transcoding disabled. If you have properly configured the source content, Jellyfin is just a passthrough for Kodi and content is directly accessed using the network share.