Does anyone else have experience using the Jellyfin plugin with their Vero?
I have a Vero5. -Jellyfin is installed as a docker on my Synology DS1821+
There is no transcoding turned on (that I can see)
Everything is set up and works rather nicely. However it is a source of annoyance that it now seems to take 3-4 seconds for a video to start, where are prior to using Jellyfin as my library it was near instantaneous over NFS
I have set up a Kodi instance on my main PC mimicking the Jellyfin setup on the Vero…and the video starts in about a second, which is fine. I suppose this could be because my main computer is heaps more powerful, but it could also mean that the issue isn’t with Jellyfin, Kodi, or the JellyfinForKodi plugin.
I’m a little lost where to begin investigating, so I’d love some suggestions from people who may have the similar setup.
To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.
Depending on the used skin you have to set the settings-level to standard or higher, in summary:
enable debug logging at settings->system->logging
reboot the OSMC device twice(!)
reproduce the issue
upload the log set (all configs and logs!) either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A
publish the provided URL from the log set upload, here
Thanks for your understanding. We hope that we can help you get up and running again shortly.
In case someone else is seeing this and is having the same problem.
This is what I did to resolve it.
There are two ways of connecting to the jellyfin database, one is called add-on, the other one is called native. Everyone is telling you to use add-on… no difference in response time apparently.
I found that to be incorrect… but it’s not the whole story
so this worked for me:
Since I have Jellyfin running in a docker, I made sure the NFS permissions for each folder had “allow users to access mounted sub folders” are ticked.
I set up NFS connections in Kodi (I’m sure Samba would work as well, but I don’t use that), that works prior to installing the Jellyfin for kodi plugin.
Next I tested the responsiveness by going into file manager in kodi and just start a video from there.
I then installed the jellyfin for kodi plugin, selected “Native mode”… despite what everyone else on the internet told me to do (again, I’m only writing down what worked for me)
next I was asked about “Path substitutions” … this is basically where you take a bit from the file’s path as the Jellyfin server reports it and substitutes it for something that gives you a different connection.
The part you need to substitute is what the library is called in jellyfin (not the name of the library, but what shows up if you go to “Dashboard - Libraries” … and look at the entry with a dash in front of it… for example /movies … you have to include a dash after it as well so write /movies/
the part you are replacing it with is the NFS address part… for example nfs://192.168.1.100/volume1/movies/ … you should be able to browse to it to make it easier
6) report step 5 for each library
7) after the import is complete… you should be good to go… might take a while thou.
I have this exact same problem. I didn’t find the root-cause, but I did discover that when this is happening the kodi.bin is using 1G of RAM and 100% cpu, when nothing is playing.
WRT your fix:
How did you do this, when Jellyfin has deprecated the native paths method?
I used native for years before upgrading to 10.10 which broke native-paths for all added video content.
It’s rather easy once get your head around it… getting my head around it was hard.
The thing that has changed is that you now have to do path substitutions… which I described in point 5 above… but I’ll try to clarify
Let’s assume you have some tv shows that are physically stored under nfs://192.168.1.101/volume1/tv.
In your Jellyfin library that is visible to the Jellyfin for Kodi plugin, it might be using the following path: /tvshows/
So what you got to do is replace the part that is different between the two paths. The effectively bypasses Jellyfin’s decision to not support native path anymore… the Jellyfin for Kodi plugin tells Kodi to play the file from a different path each time.
so replace /tvshows/ with nfs://192.168.1.101/volume1/tv/ (or whatever your path is)
do this for every library you have. Obviously not every show, just every library
it’s super important that you have a dash before and after on the Jellyfin address you want to subsititute… so /tvshows/ NOT /tvshows
That’s path substitutions… it will ignore the Jellyfin path, and just use the direct path instead when you play a movie.
you probably have to remove your library from Kodi and re-add it, don’t just play around with what’s already there. I suggest you make a tiny library with a couple of files in it in Jellyfin and use that for testing… otherwise you may go mad
edit: your finding of excessive resource use explains why i never had issues with add-on when I tested it on my windows PC… an extra gig of ram wouldn’t matter to my PC, and my Ryzen wouldn’t break a sweat with the extra cpu load.
