2015-03-05, 05:00
Then your systems are broken, and you should fix them.
Use "texturecache.py jd sets" to view the Movie Sets artwork urls on each of your clients, and - if your clients are all using the same videodb schema - you'll see the urls are all the same on each client. If the urls are different on some or all clients then those clients are not using the same MySQL server or schema you think they are, and you need to fix that.
Assuming the urls are correct on your clients, if any client is not displaying the correct images in the GUI then that is most likely a caching issue rather than a media library issue (try "texturecache.py C sets" on such clients).
Use "texturecache.py jd sets" to view the Movie Sets artwork urls on each of your clients, and - if your clients are all using the same videodb schema - you'll see the urls are all the same on each client. If the urls are different on some or all clients then those clients are not using the same MySQL server or schema you think they are, and you need to fix that.
Assuming the urls are correct on your clients, if any client is not displaying the correct images in the GUI then that is most likely a caching issue rather than a media library issue (try "texturecache.py C sets" on such clients).
