Offline Scantool (for X2 models)

[Unreal]

Taking your data there are two non integer values 23.0 and 68.0 which lead to 5 in the mede8er.db...

The XML file should not contain anything like "68.0".  In the XML file it should either be stored as "68" or "6.8".  If Y2M was used to create the XML file, the value would be stored as "68".  The only way I can think of that you would get a "68.0" stored in the XML file is if the rating came from somewhere other than IMDB.  The algorithm I provided in my previous update should handle either scenario.

[Skylinc]

The XML file should not contain anything like "68.0".  In the XML file it should either be stored as "68" or "6.8".  If Y2M was used to create the XML file, the value would be stored as "68".  The only way I can think of that you would get a "68.0" stored in the XML file is if the rating came from somewhere other than IMDB.  The algorithm I provided in my previous update should handle either scenario.

Actually, the value comes from IMDB through Tvixie, and then through a program I wrote to convert the Tvixie files to XML. I will have to correct this...

[Lupissimo]

@unreal: thank you for your algorithm, we are using something very similar.
@skylink:

You have not commented on this yet:
10 Things I Hate About You    xml Rating=  69 mede8er.db = 5    "Maasbommel"=34.5 => 3.45=> 4 (which is "our" value) but NOT 5. 
And
28 Weeks Later xml rating= 71 mede8er.db = 4  which does not agree with the 10 Things I Hate About You calculation.

I wonder how these numbers were calculated?

[Unreal]

@Lupissimo

It occurs to me that you really don't need any algorithm to determine the proper star rating conversion.  This can be done with a simple 'case' statement (or set of 'if' clauses if you prefer).  Here is the IMDB rating range for each Mede8er (1-5) star rating...

5 stars = 9.0 (90) to 10 (100)
4 stars = 7.0 (70) to 8.9 (89)
3 stars = 5.0 (50) to 6.9 (69)
2 stars = 3.0 (30) to 4.9 (49)
1 star  = 1.0 (10) to 2.9 (29)

I mention this because I found your scan tool (v1.03) generating many 5 star ratings when the rating in the XML was in the 80s (anything in the 80s should convert to "4", not "5"), so this still needs to be fixed.  Hopefully you find this chart makes the conversion code simpler and more accurate.

[Skylinc]

@Lupissimo
I did not think I had to comment on that. Sorry. But, I think Unreal's last comment is a good suggestion

[Lupissimo]

@Unreal: That seems to be the easiest solution! We will built that in!
@skylink: I still wonder how your inconsistant data came about. Just curious

[Unreal]

@Lupissimo

As I'm not familiar with Delphi, I'm not sure of the exact syntax, but I believe this code will work...

case xmlrating of
   70..89 : mstar = 4 ;
   50..69 : mstar = 3 ;
   30..49 : mstar = 2 ;
   90..100 : mstar = 5 ;
else
   mstar = 1 ;
end

...where "xmlrating" is the rating value from the xml file, and "mstar" is the star rating to write to the Mede8er.db file.  This should give your code execution a speed increase too, even though it only takes a few seconds to do several hundred movies as it is.  I tried to put the most commonly occurring star value as the first check, and the least common star rating as the last check, but I'm not certain statistically which values occur the most/least, though I'm pretty certain the mstar rating for most movies will be 4 or 3.

I believe the rating value in the xml file should not contain a decimal, but if it does, you may have to account for that.

If the value is exactly "10", it could be either the worst possible score as written by Y2M, or the best possible score as written by something other than Y2M that uses decimals, unless a perfect score by the non-Y2M program writes it as "10.0".  I don't know any movies in IMDB that carry the worst or perfect scores, but if you could find some examples, we could run them through Y2M and TG to see how they store the values in the xml file.

[Lupissimo]

@: Unreal: This is the latest version including your "Star" Rating algo, though not your exact latest coding proposal. Thank you for testing and helping to improve the scantool.

[Skylinc]

@Lupissimo

There is a password on the RAR file...

[Unreal]

@Lupissimo

Thanks, version 1.04 is working great.  I just ripped an entire TV Series and 1.04 seems to have created all of the entries in the Mede8er.db file correctly.  Thanks again for creating this tool, and for sharing it.

[jer1956]

We all think this is very good work.  But we do have to make it clear to those wanting to try this that it isn't Mede8er software, and is used without Mede8er having any responsibilty.  So we would prever to move this thread again, to Modding.

[Lupissimo]

I do not see this as a modding tool, as it does nothing to the mede8er firm- or software. It is merely a tool which elimínates lenghty scans done by the player.

[jer1956]

Data is software...you are replacing the database normally created by the code. Sanji cannot be held responsible for any unforseen consequnces of creating it this way.

No one is saying this software is a bad thing...but the practice is if you downlaod anything from the Modding Section..the adverse consequnces won't be be solved by Mods (or Sanji) by posting in the main forum. Sanji won't debug issues resulting from using this software...so here is the obvious place to host it.

[shizzl]

Lupos_SQLV1.04.rar is pass protedcted!

please post pass.


Shizzl

[Unreal]

I'm not sure why there is a password on the download, but I suggest you PM Lupissimo if you want to try the offline scanner.