[Milhouse]

Ok, so I have it installed as stated in post #1199, and it seems to be working. Any ideas on a test to run first?

Code:

texturecache.py c

is probably what most people run first.

I understand that this script is not changing anything in MySQL, just the textures13.db file for the installation on that local machine I run this on. Correct?

When caching, only Texture13.db is updated, although it is possible to update the media library (whether it be MySQL or SQLite) using the "set" option, for example:

Code:

texturecache.py imdb movies | texturecache.py set

would update your movies with the latest votes, ratings, and top250 from imdb - additional imdb fields can be configured - and these changes would then be applied against your media library, which as it's central means you'd only need to run this update on one client (potentially your Pi) for them all to see the benefit.

Once this DB is cleaned up and fixed on this PC, I have a personal .bat file that updates all boxes with the new textures13.db file, and a restart of XBMC locally.

So you're copying the textures13.db file to each PC? Just be aware that this could cause problems if you're not also copying/syncing the Thumbnails folder as well.

You can also run this script centrally, against remote clients by varying the @xbmc.host setting. Potentially you could run the script on the Pi against each of your Windows clients, waking them up ("wake") and putting them to sleep ("power suspend") as required. You'll need to configure the MAC address of each client to wake them up, assuming they support Wake-On-LAN. Best way to do this would be to add "sections" to your cfg for each client, ie.

Code:

allow.recacheall = yes
download.threads = 6
qaperiod = 9999
checkupdate = yes
orphan.limit.check = yes

[pc1]
xbmc.host = 192.168.0.123
network.mac = dd:27:eb:12:9e:7b

[pc2]
xbmc.host = 192.168.0.124
network.mac = dd:27:eb:12:9e:7d

[pc3]
xbmc.host = 192.168.0.125
network.mac = dd:27:eb:12:9e:8b

then simply add "@section=pc1" when running texturecache.py to run options against the pc1 client, add @section=pc2 to run against pc2 etc., cycling through all of your clients. Any setting in a section overrides the "global" settings you see at the top of the cfg file.

The only options that require direct access to the userdata/Thumbnails folder (ie. that need to be run locally, or against a mounted filesystem) are "f", "F", "r", "R", "S", "X" and "Xd". Everything else can be run centrally against remote clients using JSON for control and updates.

My last question (promise) - with a new setup, what would be a good place to start to run this script? The posts I see here have a lot of passing variables that seem unique to their setup.

Not sure I understand the question, are you asking what to run, where to run? I've fully automated my library management (scanning [vscan], caching [c], quality checking [qax], local artwork creation/loading [mklocal.py]) using this script, and run it centrally on a Pi with a MySQL library, pre-loading the caches ("lc movies"/"lc tvshows") of my non-Pi clients whenever new stuff has been added centrally.

This is a copy of the texturecache.cfg I wrote following the first few pages of posts:

Code:

userdata = C:\Users\Mychale\AppData\Roaming\XBMC\userdata
dbfile = Database/Textures13.db
thumbnails = Thumbnails/
xbmc.host = localhost
webserver.port = 8080
allow.recacheall = yes
rpc.port = 9090
download.threads = 6
qaperiod = 9999
checkupdate = yes
orphan.limit.check = yes

The first five settings you have are just the system defaults (rpc.port=9090 is also the default), so you can probably drop those. You really only need to specify the userdata/dbfile/thumbnails settings if they're in an unusual or non-standard location (for example, if you're mounting the userdata folder of a remote client on the local PC). The rest look fine.

I am amazed at how this started out as a simple tool for yourself and it grew into this.

You're amazed, I'm horrified.