2014-10-20, 12:25
(2014-10-20, 05:31)wrxtasy Wrote: The other thing I found after running Milhouse's Texture Cache Maintenance utility is that with proper media metadata folder structure (after local file scanning) all my media textures were already being pre-cached by XBMC in the Textures13.db.
Very few were missing - likely due to a comprehensive external metadata scraper.
Yes, if you scan using the Pi then the texture cache of the Pi should be populated with the new artwork. However if you are using MySQL then only the scanning client will have its texture cache populated during the scan while all the other clients will need to cache the new artwork as they display it, which can lead to delays and even problems if remote artwork is no longer available by the time one or more of the clients attempts to eventually display it for the first time.
So the benefit of the script depends largely on the environment - it's much more beneficial in a MySQL setup where you can pre-load the texture cache of all the non-scanner clients following a scan, but even in SQLite setups it's useful for interrogating the texture cache to confirm it's in good shape, amongst other things.