Re: IMDb.com scraper v1.4.4 (FIXES: Score/Rating + Exact Title + Writers)
Eventhough the last line says the scraper assigned the value of 6.4 to the variable movie.score, it certainly inserts 6 if you look at the SQL queries further down in the log file. The database itself also certainly has the value of 6.0 (the column is of type real / float)
The only scrapers that I have enabled are IMDB 1.4.4 and moviemeter.nl (dutch) so I have no clue why moving pictures is still initializing and parsing them, but that doesn't even matter much because the guy before you posted that this is a problem in version 0.7.5 (and possibly before). It's supposed to be fixed in moving pictures 1.0.
So far I see the following obvious already: Your moviemeter.nl scraper v1.1.0 that is still parsed doesn't use FLOAT, so score results are rounded to INT. Same with allocine.fr v1.1.1 and mymovies.it v0.2.3. So from those 3 scrapers you will always get rounded results. And for some reason IMDb scraper v1.1.6 is still getting loaded on your box.
But aside all that, I don't see a problem.
File = "Saw 6.mkv"
Search Match = "Saw VI (2009)"
13-Jan-2010 18:45:09 Debug [ ScraperNode]: Assigned variable: movie.score = 6.4
That last line means the scraper successfully assigned a score of "6.4" into database.
So make me a screenshot of MovingPictures configuration then on the Movie Details overview on Saw IV, because if that doesn't show 6.4, then you got something horribly wrong. But if you are getting rounded results and the scraper used on those movies is the Dutch, French or Italian scraper, then it makes sense, because their scraper code forces round numbers.
Eventhough the last line says the scraper assigned the value of 6.4 to the variable movie.score, it certainly inserts 6 if you look at the SQL queries further down in the log file. The database itself also certainly has the value of 6.0 (the column is of type real / float)
The only scrapers that I have enabled are IMDB 1.4.4 and moviemeter.nl (dutch) so I have no clue why moving pictures is still initializing and parsing them, but that doesn't even matter much because the guy before you posted that this is a problem in version 0.7.5 (and possibly before). It's supposed to be fixed in moving pictures 1.0.