2016-04-08, 01:26
I know this topic has been mentioned a few times in the past but have found no useful fix yet.
When using high-res pictures (2K or 4K high quality images) as backgrounds in Amber, they get down-sized badly.
I tried setting <imageres> and <fanartres> to 2048 and 4096 in advancesettings (then deleting the textures DB and the entire thumbnail cache), however analyzing the resulting texture database and thumbnail cache I still see for example:
000009|6/68871366.jpg|1080|1626|0001|2016-04-07 22:59:38|2016-04-07 18:59:38|/media/sdb1/HDR/DSC_6304-Villandry.jpg
i.e. it gets downsized to 1080. This image has approx. 6000 x 4000 pixels.
The imageres/fanartres settings produce no log errors in the log so I assume they were taken (I can see in the log Kodi read & parsed advancesettings with no problems)
Is amber using a different "parameter" other than imageres/fanartres to determine the background image resize target?
Better: can Amber offer a different mechanism to manage Background assets and bypass the downsizing altogether? Something like its own image cache (with an option to empty it)
The only way I found to work around this problem is using "texturecache.py" to find out the cached image name and replace it with the original. Not clean.
When using high-res pictures (2K or 4K high quality images) as backgrounds in Amber, they get down-sized badly.
I tried setting <imageres> and <fanartres> to 2048 and 4096 in advancesettings (then deleting the textures DB and the entire thumbnail cache), however analyzing the resulting texture database and thumbnail cache I still see for example:
000009|6/68871366.jpg|1080|1626|0001|2016-04-07 22:59:38|2016-04-07 18:59:38|/media/sdb1/HDR/DSC_6304-Villandry.jpg
i.e. it gets downsized to 1080. This image has approx. 6000 x 4000 pixels.
The imageres/fanartres settings produce no log errors in the log so I assume they were taken (I can see in the log Kodi read & parsed advancesettings with no problems)
Is amber using a different "parameter" other than imageres/fanartres to determine the background image resize target?
Better: can Amber offer a different mechanism to manage Background assets and bypass the downsizing altogether? Something like its own image cache (with an option to empty it)
The only way I found to work around this problem is using "texturecache.py" to find out the cached image name and replace it with the original. Not clean.