2023-07-11, 10:39 AM
(This post was last modified: 2023-07-11, 01:17 PM by macbean. Edited 3 times in total.)
EDIT: editing to reflect that Kodi Sync queue is separate from Jellyfin for Kodi
Kodi Sync Queue just quick working for me (i think i know why, i just need to troubleshoot more) and since I don't want to manually refresh the db, it lead me to try Jellycon.
I'm looking to see why people use one over the other.
my understanding is:
Jellyfin for Kodi populates the kodi db which means it is treated as the local library for all Kodi purposes. Aside from your own preferences, you can immediately start using kodi as is. However you rely on the sync mechanism (specifically via Kodi Sync Queue) to keep the kodi db up to date.
Jellycon, you can use the app to browse, but if you want to use the main menu to browse, you'll have to config the interface to use app links instead. Since you accessing the libraries themselves, any change is made immediately.
Is there any other real difference between the two?
Kodi Sync Queue just quick working for me (i think i know why, i just need to troubleshoot more) and since I don't want to manually refresh the db, it lead me to try Jellycon.
I'm looking to see why people use one over the other.
my understanding is:
Jellyfin for Kodi populates the kodi db which means it is treated as the local library for all Kodi purposes. Aside from your own preferences, you can immediately start using kodi as is. However you rely on the sync mechanism (specifically via Kodi Sync Queue) to keep the kodi db up to date.
Jellycon, you can use the app to browse, but if you want to use the main menu to browse, you'll have to config the interface to use app links instead. Since you accessing the libraries themselves, any change is made immediately.
Is there any other real difference between the two?