[RELEASE] Texture Cache Maintenance utility
Got a Q. With the mklocal.py script, can you ask that it overwrites existing files? If we've previously done a backup from xbmc and we want to replace those files, it would be difficult otherwise. What do you think?

Also, the change to texturecache.py worked but that only solves half of the problem. The mklocal.py script will read that input and create images correctly now which is GREAT but the resulting fixup.dat file now has decoded URLs in it. I don't think that is safe to re-import back to xbmc as the URLs stored in xbmc were originally encoded.

Its almost like we need a option in mklocal.py to use original URLs with the new base rather than the output URLs but how would mklocal know what the original was as it is just a transformation script and whats getting passed to it is whatever.

EDIT: Or we can just run texturecache.py twice. Once to decode for the images and once to output the correct URLs for making them local in the database. The only caveat is if there was a change (new scan) that occured between those two runs. Sad

Messages In This Thread
RE: [RELEASE] Texture Cache Maintenance utility - by calisro - 2015-08-13, 19:54

Logout Mark Read Team Forum Stats Members Help
[RELEASE] Texture Cache Maintenance utility17
This forum uses Lukasz Tkacz MyBB addons.