Register a SA Forums Account here!
JOINING THE SA FORUMS WILL REMOVE THIS BIG AD, THE ANNOYING UNDERLINED ADS, AND STUPID INTERSTITIAL ADS!!!

You can: log in, read the tech support FAQ, or request your lost password. This dumb message (and those ads) will appear on every screen until you register! Get rid of this crap by registering your own SA Forums Account and joining roughly 150,000 Goons, for the one-time price of $9.95! We charge money because it costs us money per month for bills, and since we don't believe in showing ads to our users, we try to make the money back through forum registrations.
 
  • Post
  • Reply
Keito
Jul 21, 2005

WHAT DO I CHOOSE ?

Hippie Hedgehog posted:

Have you tried running a Jellyfin server as a source instead of a network mount + database? I've found it to have good performance and it has lasted fine through Kodi upgrades without needing to rescan or migrate a database. Also, no reason to keep client versions in sync with each other.

The nice thing, performance-wise, is that as your server runs the scans in the background, they don't affect the client's performance at all. I'm curious to see if this would help with your problems.

Of course, getting Jellyfin to scan your whole library correctly is a whole different task than doing the same with Kodi over SMB, so a warning is in order that it does not necessarily ID content exactly identically as before.

Thanks for the suggestion! Using Jellyfin was my original plan when setting up the device, but since the Shield TV on newer OS versions apparently has broken HTTP/2 support in Kodi that made all playback from my Jellyfin server fail, and I'd screwed up with not properly closing the <network> tag in advancedsettings.xml when trying to disable it, I went with an NFS share instead when setting this up.

From past experience with running pre-release versions of Kodi, it's pretty common that addons have problems that need to be addressed.

I checked the issues on the Jellyfin for Kodi development repo, and apparently there's an incompatibility with Kodi 21 releases past beta 2 where the movie library ends up empty, so while the fix for that issue is awaiting review, you've got a choice between staying on beta 2 or manually applying these code changes on your device.


So yesterday I rolled back my Kodi application data to a backup from v20 last year, and it stopped crashing (on v21 RC1). Then I logged in to Trakt again and tried to sync my playback history, and it would crash the program every single time when doing TV shows. Removing all unnecessary sync options like my "collection" made it finally manage to get through it, and not crash on subsequent syncs either. This probably was my problem in the first place. Dunno if there's a real issue there or if the Trakt addon just needs more RAM than the Shield can provide when loading all the relevant data into RAM for comparisons.

Adbot
ADBOT LOVES YOU

Keito
Jul 21, 2005

WHAT DO I CHOOSE ?

Le0 posted:

Not sure how the renaming works to be honest. I looked into sonarr and the correct episode is downloaded from nzb like 2024.03.24. But then the issue is at kodi level apparently. I just removed the show from kodi and update data base again. I don't know what is going on but kodi found many more episodes then the only 3 that are on the disk and whenever I play one it's always playing the same file while the info shows different episodes from 2020...

https://wiki.servarr.com/sonarr/settings#episode-naming
https://trash-guides.info/Sonarr/Sonarr-recommended-naming-scheme/

Also just configure Sonarr to create metadata so your Kodi installation doesn't have to guess what it's looking at:
https://wiki.servarr.com/sonarr/settings#metadata
https://wiki.servarr.com/sonarr/supported#metadata

Keito
Jul 21, 2005

WHAT DO I CHOOSE ?
Kodi 21 Omega is out now:

https://kodi.tv/article/kodi-21-0-omega-release/

  • 1
  • 2
  • 3
  • 4
  • 5
  • Post
  • Reply