6 ms·

Cool software. I used it within/in parallel to Kodi to sync a couple devices but ended up removing this layer. I didn't like that you can't outright disable t

by zeagle 3y ago

Cool software. I used it within/in parallel to Kodi to sync a couple devices but ended up removing this layer. I didn't like that you can't outright disable transcoding for content served via their app or in the browser. I serve mostly local client and my headless NAS has poor integrated graphics and runs Linux so this was very brittle. Kodi's jellyfin addon can play without transcoding by default so this seemed reasonable. However in case others want to go this route for a similar use case I hope I can save you some frustration: both this and the native Android app do not handle Dolby vision or passthrough atmos content properly. I also had odd tearing and av sync issues with some large 4k content that don't happen with maven kodi builds. After a lot of time trying to figure out it, I stripped it out and my shield has no further issues just using kodi despite being the ill famed 2019 tube model. Hdr10, Dolby vision, atmos pass through you name it just works.

WastingMyTime89 3y ago
> 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.
- zeagle 3y ago
  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.
  - WastingMyTime89 3y ago
    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.
    - zeagle 3y ago
      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.
- nijave 3y ago
  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) https://github.com/jellyfin/jellyfin/issues/8743 https://github.com/jellyfin/jellyfin/issues/8743
  - zeagle 3y ago
    Thanks I'll need to take a look next time I start tweaking my tv setup!
DarkCrusader2 3y ago
> However in case others want to go this route for a similar use case I hope I can save you some frustration: both this and the native Android app do not handle Dolby vision or passthrough atmos content properly. I also had odd tearing and av sync issues with some large 4k content that don't happen with maven kodi builds. I also get audio sync issue with some media types. I am frustrated to the point that I now just copy things on a thumb drive to play on my TV. Just to understand you setup better, are you using kodi on TV or your server or both?
- zeagle 3y ago
  I run Kodi on a 2019 Nvidia shield "tube" model. My media and previously jellyfin is on a NAS that serves the content over nfs to the shield. Shield--Receiver--TV. Look into the maven Kodi build if you have something similar. My sync issues went away using when I stopped using jellyfin and also maybe from removing path substitution when I redid it from scratch. I believe I have fixed output with passthrough in Kodi and upmixed turned off on the shield.

by zeagle 3y ago

WastingMyTime89 3y ago

> 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.

zeagle 3y ago
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.
- WastingMyTime89 3y ago
  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.
  - zeagle 3y ago
    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.
nijave 3y ago
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) https://github.com/jellyfin/jellyfin/issues/8743 https://github.com/jellyfin/jellyfin/issues/8743
- zeagle 3y ago
  Thanks I'll need to take a look next time I start tweaking my tv setup!

DarkCrusader2 3y ago

> However in case others want to go this route for a similar use case I hope I can save you some frustration: both this and the native Android app do not handle Dolby vision or passthrough atmos content properly. I also had odd tearing and av sync issues with some large 4k content that don't happen with maven kodi builds. I also get audio sync issue with some media types. I am frustrated to the point that I now just copy things on a thumb drive to play on my TV. Just to understand you setup better, are you using kodi on TV or your server or both?

zeagle 3y ago
I run Kodi on a 2019 Nvidia shield "tube" model. My media and previously jellyfin is on a NAS that serves the content over nfs to the shield. Shield--Receiver--TV. Look into the maven Kodi build if you have something similar. My sync issues went away using when I stopped using jellyfin and also maybe from removing path substitution when I redid it from scratch. I believe I have fixed output with passthrough in Kodi and upmixed turned off on the shield.