Xorp 48 Posted March 23, 2016 Posted March 23, 2016 If a movie gets added to my collection, by way of the scheduled library scan, when I look at it's details information like the community rating, it's out of date or incorrect. If I hit refresh, then the information gets updated to correct current info. For example, today I added the movie Brave to my collection. It has never been in my collection before. It was added by me triggering the library scan, and when looking at the information page the community rating was at 6.5. After I hit refresh, it was updated to the correct 7.2. I just looked all 20 of my most recently added movies. All of them have an incorrect community rating, that is only corrected after manually hitting refresh for each one. Why is Emby pulling incorrect information every time when it's grabbing the metadata for the first time?
ebr 16185 Posted March 23, 2016 Posted March 23, 2016 Are you sure the items you added didn't already have metadata with them? How were they added?
Xorp 48 Posted March 23, 2016 Author Posted March 23, 2016 These items never existed in Emby before. Like I said, the normal "Scan media library" task added them.
Luke 42080 Posted March 23, 2016 Posted March 23, 2016 That's not what he asked Did another program create an nfo, or was there already one attached to the file you downloaded? If yes then this is where the metadata came from.
ebr 16185 Posted March 23, 2016 Posted March 23, 2016 Yes, by "how were they added" I mean the actual movies in the file system. Did you rip them yourself from a disc or did some other program download them from [ahem] somewhere and potentially also bring an nfo file with it...
Xorp 48 Posted March 23, 2016 Author Posted March 23, 2016 (edited) There isn't any foreign information/nfo. I remux all my movies by hand with eac3to/mkvmerge. Anytime I add a movie, I create a new folder in the movies folder (movies library pointing to this folder) with the title and release year, then copy the .mkv and nothing else into it. Edited March 23, 2016 by Xorp
Xorp 48 Posted March 24, 2016 Author Posted March 24, 2016 It's definitely happening for every new movie added. I created a folder called "Ip Man 3 (2015)" and put "Ip Man 3 (2015).mkv" and nothing else in it. nfo upon being detected for the first time by the library scan (5.5 rating): http://pastebin.com/59eb7afw nfo after refresh on info page (7.6 rating and more info): http://pastebin.com/W7kejuLz
Luke 42080 Posted March 24, 2016 Posted March 24, 2016 it's not a question of new vs. old. 5.5 is the rating on tmdb, 7.6 is the rating on omdb. so that means for some reason the initial omdb lookup didn't produce anything, but then the second time it did.
Xorp 48 Posted March 25, 2016 Author Posted March 25, 2016 (edited) it's not a question of new vs. old. 5.5 is the rating on tmdb, 7.6 is the rating on omdb. so that means for some reason the initial omdb lookup didn't produce anything, but then the second time it did. Ok it's starting to make sense now. It also said the movie was GB-12 before the refresh, and PG-13 after the refresh. Thing is I have OMDB with higher priority in the Metadata services. I wish it would use all the OMDB's info the first time. Edited March 25, 2016 by Xorp
Luke 42080 Posted March 25, 2016 Posted March 25, 2016 It does, there must just been some kind of failure the first time around.
Xorp 48 Posted March 31, 2016 Author Posted March 31, 2016 It does, there must just been some kind of failure the first time around. If it consistently fails the first time, everytime, then I'd consider it a bug. The last 50 movies I added had to be manually refreshed.
Xorp 48 Posted February 4, 2017 Author Posted February 4, 2017 Is there some new issue with getting the OMDb rating? Since updating to Emby 3.1.5 the film rating has been stuck at the TMDB rating and not taking the OMDB rating after a metadata refresh. As mentioned in post #10, I STILL have to do a manual refresh to every new movie because it STILL prefers the TMDB info during the first-time detection, even though OMDB STILL has higher preference in my metadata settings. I even tried disabling TMDB metadata, and doing a refresh with OMDB as my only provider, but recently added stuff is still stuck at the TMDB rating. There are no OMDB Api errors in the logs.
Luke 42080 Posted February 4, 2017 Posted February 4, 2017 @@Xorp, there is no known issue. In order for us to best help you, please provide the information requested in how to report a problem. thanks !
Happy2Play 9782 Posted February 4, 2017 Posted February 4, 2017 Is there some new issue with getting the OMDb rating? Since updating to Emby 3.1.5 the film rating has been stuck at the TMDB rating and not taking the OMDB rating after a metadata refresh. As mentioned in post #10, I STILL have to do a manual refresh to every new movie because it STILL prefers the TMDB info during the first-time detection, even though OMDB STILL has higher preference in my metadata settings. I even tried disabling TMDB metadata, and doing a refresh with OMDB as my only provider, but recently added stuff is still stuck at the TMDB rating. There are no OMDB Api errors in the logs. How about a specific example.
Xorp 48 Posted February 5, 2017 Author Posted February 5, 2017 How about a specific example. I added the magnificent film "The Room (2003)" to my movies folder directory. Had both metadata downloaders OMDB and TMDB enabled. A media library scan added the film to my movies library with a rating of 4.5, the TMDB rating. Prior to 3.1.5 doing a refresh (both ways), would change the rating to the OMDB rating of 3.5. Since 3.1.5, the rating stays at 4.5 after a refresh.
Luke 42080 Posted February 5, 2017 Posted February 5, 2017 @@Xorp can you please provide the emby server log (as requested in the link i provided, how to report a problem). thanks !
Luke 42080 Posted February 5, 2017 Posted February 5, 2017 Additionally, see the notice on the omdb front page: http://www.omdbapi.com/ 1
Happy2Play 9782 Posted February 5, 2017 Posted February 5, 2017 Was just go to say what Luke already posted, and your log would have said the same. The remote server returned an error: (503) Server Unavailable.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now