133
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Jun 2024
133 points (98.5% liked)
Jellyfin: The Free Software Media System
5714 readers
3 users here now
Current stable release: 10.10.0
Matrix (General Information & Help)
Matrix (Off-Topic) - Come get to know the team and blow off steam!
Matrix Space - List of all the available rooms on Matrix.
Discord - Bridged to our Matrix rooms
founded 4 years ago
MODERATORS
Hey, I've worked in the recommendations/similarity calculations. Could you post a screenshot of the detail page for Inside Out? I suspect your media doesn't have associated metadata (e.g. tmdb tags) that are used to power similarity calculations.
I'm not 100% sure what the detail page is but here is the page I see when selected.
I think I have Jellyfin mostly at the default setings, with one exception. I did change the name of the key for the rating variable in the metadata to be 'MPAA rating' instead of the default which I think was 'rating' before since I found it confusing. So if the current recommendation calculation is using that variable then I guess it would be null for all my media.
Also, here is the metadata jellyfin shows.
PS: I scrape my metadata from themoviedb.org in Kodi and then export that to an xml file of the same name, Jellyfin seems to find and use that.
https://github.com/jellyfin/jellyfin/blob/31aa44d23d12b5dbb5f9a131242cc82c9ef98f24/Emby.Server.Implementations/Data/SqliteItemRepository.cs#L2279 is what's discovering similar content. If the
InheritedParentalRatingValue
is considered zero, it's only going to match other content with the same value. Can you elaborate on "I did change the name of the key for the rating variable in the metadata to be ‘MPAA rating’ instead of the default which I think was ‘rating’ before since I found it confusing."? I suspect we're zeroing (ha ha) in on the problem.Digging in a bit. It looks a bit different than I thought it did on my end.
I periodically use Kodi to backup my metadata to an NFO file. But I guess I forgot to script that and haven't actually done that in a while. When Kodi scrapes the metadata it preprends the
mpaa
value with the stringMPAA Rated
. I did this to make it more obvious if the rating was scraped correctly since I've seen kodi attempt to scrape before but then just record the value as null.Inside Out didn't have an NFO that Jellyfin was reading from. But Jellyfin is set to scrape its own metadata from all avaliable sources. I just didn't enable it to write its own NFO file since I want the files that Kodi makes to take precidence and not be overwritten be Jellyfin. So for the case of insde out, it's pulling the correct rating without any changes. As seen in this desktop screenshot.
A Boy and His Dog, on the other hand does have a nfo from Kodi and it does have that MPAA rating on jellyfin with the prepended string as seen in this screenshot and in this bit from the nfo file.
So I guess I have 2 questions.
Yes, modifying the value is going to break the mappings (see https://github.com/jellyfin/jellyfin/blob/master/Emby.Server.Implementations/Localization/Ratings/us.csv). Anywho, I think we've discovered the root of your problem. How you choose to rectify it I leave to you! Personally, I'd recommend suffixing your filenames with
[tmdbid-123456]
as per https://jellyfin.org/docs/general/server/media/movies/ and letting themoviedb.org handle it all for you.