2017-02-20, 10:13
Guys, we don't display any AR in gui.
It is solely used for writing into NFO, to give Kodi a kickstart of the values.
IIRC, Kodi uses that until first play, and then uses it's own calculation for that (which is the same as ours, btw)
Another thing we have to mention, is, that some movies (like http://www.imdb.com/title/tt1104001/technical and many others) have multiple values there.
So we couldn't reliable scrape this. (and no, we won't inflate the searchresults for every AR, multiplied for every possible edition, multiplied for every xxxx)
You could correct the "real" resolution at file level.
Just edit the mediainformation width & height of your video files to your needs... to match a desired AR.
For v3, we _might_ consider a textbox, to override such a value (TBD)
It is solely used for writing into NFO, to give Kodi a kickstart of the values.
IIRC, Kodi uses that until first play, and then uses it's own calculation for that (which is the same as ours, btw)
Another thing we have to mention, is, that some movies (like http://www.imdb.com/title/tt1104001/technical and many others) have multiple values there.
So we couldn't reliable scrape this. (and no, we won't inflate the searchresults for every AR, multiplied for every possible edition, multiplied for every xxxx)
You could correct the "real" resolution at file level.
Just edit the mediainformation width & height of your video files to your needs... to match a desired AR.
For v3, we _might_ consider a textbox, to override such a value (TBD)
