[RELEASE] Texture Cache Maintenance utility
OK cheers. You are certainly wise and I will need to digest that a little. Maybe i'm not fully understanding what this program is doing.

So if I don't make my artwork 'local' does that mean that my database is fetching information 'remotely', albeit in a cached format that would slow down scrolling through my library (as an example)?

To take it back a step and I apologise for the layman undertones but I just hate not understanding things.. I have my pi running Kodi on 192.168.1.4 that is accessing my NAS via NFS on 192.168.1.7. Via Putty I can run your programs in W10 (or alternatively linux based systems) without issues and can edit files via Filezilla or the like. So, when I run the below script for movies as an example is it fetching the movie data again and linking it between pathways? Or is it providing a link between the cached movie database already on the pi to the NAS for local storage? The latter doesn't seem to be right...

./texturecache.py jd movies | ./mklocal.py --local /freenas/media --prefix nfs://192.168.1.7/share/Videos --artwork fanart poster clearlogo clearart --output fixup.dat

Thanks in advance.
Reply
 
Thread Rating:
  • 17 Vote(s) - 4.76 Average


Messages In This Thread
Crash on Gotham on OS X - by desepticon - 2014-05-29, 17:57
RE: [RELEASE] Texture Cache Maintenance utility - by 80njc80 - 2017-09-05, 07:21
Cleaning - by AleisterHH - 2018-05-28, 22:03
RE: Cleaning - by Milhouse - 2018-05-28, 22:16
qax genre not updated - by Just-Me_A-User - 2018-06-12, 22:06
RE: qax genre not updated - by Milhouse - 2018-06-12, 23:40


Logout Mark Read Team Forum Stats Members Help
[RELEASE] Texture Cache Maintenance utility4.7617