Enabling Kodi Sync Queue in jf4k causes adverse video playback performance about jellyfin-kodi HOT 2 OPEN

Your terminology is confusing, but I can understand what the issue is at least. First off

Note that this is for locally stored media, not indexed by Jellyfin, browsed to via the Files menu.

This is really not a supported use case. The docs explicitly state

However, it also tends to consume the database and not share well, so if you have local media or something else that interacts with the database directly, you will have conflicts and it will not be happy.

Because of how the addon is currently designed, trying to do this is far more likely to encounter issues than other situations. That's (probably) not directly related to what's happening here, but it's worth pointing out you're playing with fire.

Just so everybody is on the same page, the Sync Queue is not a client side thing. It's a plugin that lives in the server and has exactly 0 effect on the Kodi client except when Kodi first starts. The addon installed into Kodi is named jellyfin-kodi, or Jellyfin for Kodi. We sometimes abbreviate this to jf4k if we're feeling lazy. It's not a huge deal, but it greatly helps if everybody is using the same terminology to avoid confusion.

The actual issue, the settings stuff, and this is where things get fun. None of those are actual settings. This is a side effect of previous developers of this addon using the in-memory settings storage of Kodi as a temporary variable store. Kinda gross, but it is what it is right now. I also have significant doubts that this is what's causing your performance issues. imo, it's annoying but harmless, which is why I haven't redesigned that part of it yet. Those log messages aren't even coming from our code directly.

If I had to guess, it's more likely the addon trying to do processing in the background and send playback status to the server, while failing miserably because you're playing files that aren't on jellyfin (again, not really a supported use case currently). Without checking the code, I suspect it's just trying to ship playback progress for everything instead of properly trying to scope itself to only things that's playing from jellyfin. Previous design decisions have led to the assumption that the jellyfin-kodi addon is your only real source of media on this playback device. Disabling the "sync during playback" probably means that it's not retrieving new data from the server during that time period (new episodes/movies, updated watch status, etc), but I doubt it disabled all current status reporting.

from jellyfin-kodi.

Hey @mcarlton00 thanks again for looking at this, and sorry about the confusion.

Just so everybody is on the same page, the Sync Queue is not a client side thing.

The setting in jf4k calls itself "Enable Kodi Sync Queue," which is to what I was referring. Of course, this requires having the plugin installed on the server as well.

This is really not a supported use case

For the record, the problem occurs also when playing the same video, indexed by Jellyfin, with no change in the symptomology. I was simply trying to show that when interacting with a file that is not in the Kodi DB - just by browsing to it with the file browser, the same problem occurs. I guess I should have left it at "it doesn't matter if the video is being served to Kodi by Jellyfin or not."

None of those are actual settings. This is a side effect of previous developers of this addon using the in-memory settings storage of Kodi as a temporary variable store.

Ugh.

If I had to guess, it's more likely the addon trying to do processing in the background and send playback status to the server, while failing miserably because you're playing files that aren't on jellyfin

Sorry for misleading you. This problem occurs even when the file is indexed by Jellyfin, with the exact same symptoms and results. And, again, disabling the jf4k "Enable Kodi Sync Queue" setting restores Kodi performance to normal levels for the system in question.

Let me know what more I can do to help.

from jellyfin-kodi.