jellyfin-kodi
jellyfin-kodi copied to clipboard
Dynamic libraries slower than Jellycon
Describe the bug I have a few libraries that I don’t want included in TV Shows or Movies and I was going to just use the dynamic libraries and add a link to it from Favorites. But I’ve noticed the loading of the dynamic library in this addon is much much slower than the same library via Jellycon. Leading me to believe that Jellycon might be retrieving the dynamic library in some more efficient way or doing caching.
Is there anyway to have the dynamic libraries use the same fast loading as Jellycon does? As I’d rather not have to have both anddons installed.
To Reproduce
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior
Logs
Screenshots
System (please complete the following information):
- OS: [e.g. Android, Debian, Windows]
- Jellyfin Version: [e.g. 10.0.1]
- Kodi Version: [e.g. 18.3]
- Addon Version: [e.g. 0.2.1]
- Playback Mode: [e.g. Add-On or Native]
Additional context
This is more or less expected at this point. Jellycon has seen a bunch of optimizations around dynamic library loading since that's the only way it has to display server contents. This addon hasn't seen those same improvements since it's primarily designed to be used with the metadata/database sync method. It's been on the todo list forever, but just a lack of time/interest from somebody willing to dig into it. And since they both behave very differently behind the scenes, it's unfortunately not as easy as just copying that code over to this client.
That makes a lot of sense. Is there any concerns for running both addons? Use this one for writing to the tv and movies database and then use Jellycon on the same Kodi installation for some dynamic libraries that don’t conform to the tv and movie libraries?
EDIT: as a side question, is one of the plugins considered more stable than the other?
@mcarlton00 just curious if there any concerns for running both addons at the same time? And is one of the plugins considered more stable than the other?
Nope, both are separate codebases and namespaces and don't conflict in any way. I'm not sure either of them can be considered better/more stable. I personally primarily use jellycon just because I don't want to deal with the database sync. It largely comes down to personal preference.