So just to confirm: Kodi + jellyfin app is better than Jellyfin media player?
Yes, don't hesitate. Kodi on the client is much better than Jellyfin. If you also have Jellyfin on the server and serve the media to Kodi via the addon, you have the best of both worlds.
Yes, don't hesitate. Kodi on the client is much better than Jellyfin. If you also have Jellyfin on the server and serve the media to Kodi via the addon, you have the best of both worlds.
Thanks for letting me know. This is very interesting. I am using jellyfin server via docker and as a client I use the browser or jellyfin media player for 2 years now and CPU usage can really get high. will check this out definitely and see if CPU usage improves!
Display MoreI read above a recommendation to mount the mergerfs pool root directory (/srv/mergerfs) as the Jellyfin media directory. Ok, while this may work, it is not the preferred method because of the performance: mounting the mergerfs pool root directory can lead to performance issues, especially for large libraries. This is because Jellyfin will need to scan the entire pool for media files, even if they are located on different physical disks. And safety is the second moment, 'cause mounting the mergerfs pool root directory gives Jellyfin full write access to all of the files in the pool. This is a safety risk, as it could allow Jellyfin to accidentally delete or corrupt important files.
Instead, I recommend mounting specific subdirectories of the mergerfs pool as the Jellyfin media directory. For example, you could mount the following subdirectories:
/srv/mergerfs/Media/tvshows/srv/mergerfs/Media/movies
This will give Jellyfin access to the media files it needs, without giving it full write access to the entire mergerfs pool. You need just to update your Docker Compose file to mount the specific subdirectories instead of the mergerfs pool root directory and update the Jellyfin library configuration to point to the mounted subdirectories (for example, I mean you would need to create a new library for TV shows and point it to the /data/tvshows directory).
It seems simple, but not.
If you don't want a container to be able to write to a volume you just have to mount it as read-only (:ro). For example in the previous case you would do this:
- /srv/mergerfs/Media/movies:/movies:ro
This way Jellyfin will be able to read the volume but will not be able to write to it.
Display MoreThats good that it all work good with jellyfin! Hevc will be ok as most things at home run them fine, if i am away somewhere i can do without those movies until one day i upgrade the computer.
I managed to move the folder with all the fanart in kodi (thumbfolder) so that is one good thing in the right direction.
What i have stumbled and got stuck doing is to get jellyfin running in a container. I can install it fine and all but i cannot access the webui. I have these settings when i pull the image and it seems to work correctly:
-----------------------------------------------------------------------------------------------------
version: "2.13"
services:
jellyfin:
image: lscr.io/linuxserver/jellyfin:latest
container_name: jellyfin
environment:
- PUID=100
- PGID=1000
- TZ=Europe/Stockholm
- JELLYFIN_PublishedServerUrl=192.168.1.23 #optional and i used my internal port to get it running until i can figure out nginx on my Homeassistant https://edubirdie.com/examples/cyber-bullying/ has examples to help me keep informed about cyber bullying and cyber security of my data. to play nice with my domains and i can direct them properly
volumes:
- /srv/mergerfs/Media/Jellyfin/System/Config:/config
- /srv/mergerfs/Media/Jellyfin/System/Cache:/cache
- /srv/mergerfs/Media:/media
ports:
- 8888:8096
restart: unless-stopped
-----------------------------------------------------------------------------------------------------
Hi, can I give you a few questions in PM about the code? (Probably you have private profile, because I can't DM you). I read above a recommendation to mount the mergerfs pool root directory (/srv/mergerfs) as the Jellyfin media directory. Ok, while this may work, it is not the preferred method because of the performance: mounting the mergerfs pool root directory can lead to performance issues, especially for large libraries.
Don’t have an account yet? Register yourself now and be a part of our community!
