2012-05-01, 12:40
I've set the following in advancedsettings.xml:
<thumbsize>1500</thumbsize>
to force XBMC to cache cover images (thumbnails) at a higher resolution because I wasn't happy with the display quality of the cover images it was importing from my folders.
The setting worked and the quality HAS improved.
But, I've been looking in the cache folders at the actual .tbn files it is creating and I opened them up in GIMP to look at the actual image size of the tbn files it's caching.
I'm a bit puzzled by what I'm seeing.
I have the thumbsize set to 1500 pixels which according to the wiki means that the image can be a maximum size of 1500x1500 pixels.
The source image is 1000x1500 (the standard cover image size on TheMovieDB.org).
And yet, the tbn file produced by XBMC has dimensions of: 836 x 1253
Why?
Why hasn't it kept that image at it's native size as it is on disk when it converted it to a tbn file?
If <thumbsize> is set to 1500 there should be no reason to downsize the image as I understand it.
The thing is, the resultant image IS much bigger than the default image size, so the setting is clearly working, just not quite as I expected.
I'm interested to understand what math / logic is being applied when resizing and caching.
<thumbsize>1500</thumbsize>
to force XBMC to cache cover images (thumbnails) at a higher resolution because I wasn't happy with the display quality of the cover images it was importing from my folders.
The setting worked and the quality HAS improved.
But, I've been looking in the cache folders at the actual .tbn files it is creating and I opened them up in GIMP to look at the actual image size of the tbn files it's caching.
I'm a bit puzzled by what I'm seeing.
I have the thumbsize set to 1500 pixels which according to the wiki means that the image can be a maximum size of 1500x1500 pixels.
The source image is 1000x1500 (the standard cover image size on TheMovieDB.org).
And yet, the tbn file produced by XBMC has dimensions of: 836 x 1253
Why?
Why hasn't it kept that image at it's native size as it is on disk when it converted it to a tbn file?
If <thumbsize> is set to 1500 there should be no reason to downsize the image as I understand it.
The thing is, the resultant image IS much bigger than the default image size, so the setting is clearly working, just not quite as I expected.
I'm interested to understand what math / logic is being applied when resizing and caching.