I use a mysql database docker on my system for my kodi's to access. In order to make it work though you have to be able to add an xml file to the kodi install that drirects it to use the database. This is probably not an option for firesticks and such.
Yes, you can without any issue do that with Firestick.
Will report back if i manage
An easy to configure and working solution is to use jellyfin on the server and kodi+jellyfin_plugin on the client. You get the benefits of both worlds, synced core database and client with the versatility of kodi.
Regarding the first post of this thread, there is a way to install kodi on docker under OMV. I guess it could be done in a raspberry. https://hub.docker.com/r/erichough/kodi/
Hmmm, that might be right when i think about it. The jellyfin keep syncing the media, does it save the progress and it works correct in kodi also?
Then direct the clients in advanced.xml to a thumbs folder on the omg and keep it all there so it doesnt fill up all the space on the clients! I am planning to move over to jellyfin as it seems. More versatile like this usecase. This seems to be the easiest solution. I will try and see how it is and report back😊
The jellyfin keep syncing the media, does it save the progress and it works correct in kodi also?
I have been using the kodi+jellyfin solution for two years with success.
I am using an i3 6100 so it should handle h264 pretty well, the docker with a proper kodi is quite old by now, 2 years. Might be a newer one, but i have to use 18.9 as my addons does not work on newer versions but this one is the correct version and would be sweet if i can get it running!
With h264 you won't have any problem. To play hevc you have two options.
1. That the client reproduces it directly (raspberry4 does it, raspberry3 doesn't) In this case it will work with any file server.
2. The client can't play hevc and you need to reencode on the server. in this case it will depend on your GPU (intel quicksync, etc)
I have been using the kodi+jellyfin solution for two years with success.
With h264 you won't have any problem. To play hevc you have two options.
1. That the client reproduces it directly (raspberry4 does it, raspberry3 doesn't) In this case it will work with any file server.
2. The client can't play hevc and you need to reencode on the server. in this case it will depend on your GPU (intel quicksync, etc)
Thats 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 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
-----------------------------------------------------------------------------------------------------
PUID=100
- PGID=1000
These are swapped
- /srv/mergerfs/Media/Jellyfin/System/Config:/config
Besides what Soma said, it's not a good idea to put a database in a merge. I recommend you read this.
These are swapped
I saw the swapping somewhere and tried that as well but i didnt make a difference, but i will use the correct order 🙂
Besides what Soma said, it's not a good idea to put a database in a merge. I recommend you read this.
I have had some weirdness with mergerfs and havent been able to use the filesystem as an ordinary drive. Will it work if i use a drive seperately and write to that one that is in the mergerfs?
I will read up in the thread. I did some changes in the advanced settings so that might be the issue as well! Thanks for the heads up, docker is pretty new to me but i am understanding more and more 🙂
I have had some weirdness with mergerfs and havent been able to use the filesystem as an ordinary drive. Will it work if i use a drive seperately and write to that one that is in the mergerfs?
Mergerfs is not suitable for frequently changing databases and files. That is why I advise in that guide to use a dedicated disk.
I will read up in the thread
I'm currently updating that guide, basically including openmediavault-compose instead of Portainer.
Will it work if i use a drive seperately and write to that one that is in the mergerfs?
That is the prefered method for the configs (all containers, NOT JUST jellyfin)
For the MEDIA, you can point it to the merged pool subfolders.
In the below example, you pass as many volumes as you want that are on /srv/mergerfs/Media/<subfolder> replacing <subfolder> with the correct name.
For safety, I pass my volumes to jellyfin with Read-Only flag to prevent anyone from deleting them:
- /srv/mergerfs/Media/tvshows:/data/tvshows:roThis said, your YML would look something like:
version: "2.13"
services:
jellyfin:
image: lscr.io/linuxserver/jellyfin:latest
container_name: jellyfin
environment:
- PUID=1000 # This USER need to have at least, read access to Media folder
- PGID=100 # Standard ID for the "users" group.
- TZ=Europe/Stockholm
- JELLYFIN_PublishedServerUrl=192.168.1.23 # This is the IP of the HOST
volumes:
- /srv/dev-disk-by-uuid-STRING/appdata/jellyfin/config:/config # replace STRING with a valid disk UUID
- /srv/mergerfs/Media/tvshows:/data/tvshows
- /srv/mergerfs/Media/movies:/data/movies
ports:
- 8096:8096
restart: unless-stoppedAfter accessing jellyfin for the first time, configure your Libraries to point to /data/tvshows, /data/movies, etc
For safety, I pass my volumes to jellyfin with Read-Only flag to prevent anyone from deleting them:
Code - /srv/mergerfs/Media/tvshows:/data/tvshows:ro
You might be interested in taking a look at this.
One of the solutions they preach is to make them non-nested mounts. But I don't think this will work if under /tvshows you have /tvshows/dexter/ /tvshows/house/ ...
One of the solutions they preach is to make them non-nested mounts. But I don't think this will work if under /tvshows you have /tvshows/dexter/ /tvshows/house/ ...
That might be valid for BIND Mounts, but not for Volumes.
Just tried to and subfolders are still RO.
Bashed into the container:
root@f59c9682d8a8:/# mount
/dev/sde1 on / type btrfs (rw,relatime,ssd,space_cache,subvolid=3330,subvol=/docker/btrfs/subvolumes/4685572dc11b1a03da69709f6a2b25c00d4c2a580ebf0967e185b988531e43da)
----
/dev/sde1 on /config type btrfs (rw,relatime,ssd,space_cache,subvolid=5,subvol=/)
----
/dev/sdb2 on /data/music type btrfs (ro,relatime,space_cache,subvolid=5,subvol=/)
/dev/sdb2 on /data/tvshows type btrfs (ro,relatime,space_cache,subvolid=5,subvol=/)
/dev/sdb2 on /data/anime type btrfs (ro,relatime,space_cache,subvolid=5,subvol=/)
/dev/sdb2 on /data/documentaries type btrfs (ro,relatime,space_cache,subvolid=5,subvol=/)
/dev/sdb2 on /data/movies type btrfs (ro,relatime,space_cache,subvolid=5,subvol=/)
root@f59c9682d8a8:/# touch /data/tvshows/test.txt
touch: cannot touch '/data/tvshows/test.txt': Read-only file system
root@f59c9682d8a8:/# touch /data/tvshows/A
Alf.S01.1080p.HMAX.WEB-DL.DD2.0.x264-SceneHD/ Andor.S01.1080p.WEB.h264-KOGi/
ALF.S01-S04.Complete.DVDRip/ As.Misteriosas.Cidades.de.Ouro.S01.480p/
Allo.Allo.Complete.Series/ ATLANTIS.2013.720p.BluRay.x264/
Allo.Allo.The.Complete.Collection.and.Extras.AAC.X264-SceneRush/ Away.S01.720p.NF.WEB.DDP5.1.Atmos.x264-NTb/
root@f59c9682d8a8:/# touch /data/tvshows/Alf.S01.1080p.HMAX.WEB-DL.DD2.0.x264-SceneHD/teste.txt
touch: cannot touch '/data/tvshows/Alf.S01.1080p.HMAX.WEB-DL.DD2.0.x264-SceneHD/teste.txt': Read-only file systemThat might be valid for BIND Mounts, but not for Volumes.
You're right. Looking for another topic I stumbled upon it and remembered your comment. But I didn't read the article completely.
After accessing jellyfin for the first time, configure your Libraries to point to /data/tvshows, /data/movies, etc
That's the same process as Emby, that way Jellyfin can locate where the media is stored, so it's like it's own directory structure for the container, I use /mnt/<whatever>
An easy to configure and working solution is to use jellyfin on the server and kodi+jellyfin_plugin on the client. You get the benefits of both worlds, synced core database and client with the versatility of kodi.
Regarding the first post of this thread, there is a way to install kodi on docker under OMV. I guess it could be done in a raspberry. https://hub.docker.com/r/erichough/kodi/
I have to thank you for this, it made me rethink the use of jellyfin on the Pi (CM4 now with the Axzez Interceptor).
Instead of streaming the movies via the jellyfin webpage, I installed Kodi on the Laptop with the Kodi Jellyfin Add-on.
The CPU came down from ~90% (via web) to <~10% using Kodi, 
Will post some proof-of-concept tomorrow and also point this to another thread of a USER that didn't like how much CPU was spent on the Pi with jellyfin:
I have to thank you for this, it made me rethink the use of jellyfin on the Pi (CM4 now with the Axzez Interceptor).
I am glad that it has served you. 
Instead of streaming the movies via the jellyfin webpage, I installed Kodi on the Laptop with the Kodi Jellyfin Add-on.
The CPU came down from ~90% (via web) to <~10% using Kodi,
Jellyfin has a lot going for it, but as a media player, Kodi is still way ahead. It's hard to compete against Kodi's (formerly xbmc) 20 years of experience.
Here it is, watching a h265 file via docker-jellyfin on the CM4 on the Kodi (Windows x64) with the kodi jellyfin addon.
The CPU on jellyfin only spiked a bit up to ~70% at the very beginning of the movie but them, came down to 4%.
Specs of the file are:
Same movie but via the jellyfin webpage which forces the Pi to rely on ffmpeg and pushing the 4 Cores to more than 90%:
Here it is, watching a h265 file via docker-jellyfin on the CM4 on the Kodi (Windows x64) with the kodi jellyfin addon.
The CPU on jellyfin only spiked a bit up to ~70% at the very beginning of the movie but them, came down to 4%.
That's how it is. Kodi makes better use of the resources at its disposal than Jellyfin. Jellyfin's media player still has a ways to go.
That's how it is. Kodi makes better use of the resources at its disposal than Jellyfin. Jellyfin's media player still has a ways to go.
So just to confirm: Kodi + jellyfin app is better than Jellyfin media player?
Don’t have an account yet? Register yourself now and be a part of our community!
