[RELEASE] Texture Cache Maintenance utility - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: Supplementary Tools for Kodi (https://forum.kodi.tv/forumdisplay.php?fid=116) +--- Thread: [RELEASE] Texture Cache Maintenance utility (/showthread.php?tid=158373) Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
|
RE: [RELEASE] Texture Cache Maintenance utility - Forage - 2014-10-18 (2014-10-17, 21:39)Milhouse Wrote: Update: I can add a fix, but it's only going to work if texturecache.py has direct file system access to the Thumbnails folder as the JSON Textures API "lies" about thumbnail file existence - it responds with details from Textures13.db even though the underlying cached file is missing, so the fix is not going to be ideal. Those that are maintaining remote systems won't see any change, but those running the script on a local system (or that have mounted the remote Thumbnails folder locally) will have the benefit of automatic "fixing" of any missing thumbnails. Thanks again Milhouse. I understand you simply can't cater for every possible failure. It's good that at least one has been added that will help others who used the backup feature unsuccessfully. I'll see if I can reproduce the issue to get the actual backup feature fixed as well. I've skipped adding a log file created by the script because the cause was already determined and fixable and the file was too big to begin with, but let me know if you would still like to have it. RE: [RELEASE] Texture Cache Maintenance utility - Milhouse - 2014-10-18 No need for the log file now. RE: [RELEASE] Texture Cache Maintenance utility - Maetrik - 2014-10-21 Does this work on the Fire TV? If yes, which is the correct path? I'm starting this from my MacBook, no issues with doing that on an AppleTV and an HTPC. I tried: userdata = /sdcard/Android/data/org.xbmc.xbmc/files/.xbmc/userdata/ and userdata = /storage/emulated/0/data/org.xbmc.xbmc/files/.xbmc/userdata/ but no luck RE: [RELEASE] Texture Cache Maintenance utility - Milhouse - 2014-10-21 (2014-10-21, 18:27)Maetrik Wrote: Does this work on the Fire TV? Should do. (2014-10-21, 18:27)Maetrik Wrote: I tried: The script should be using the default Android userdata path (wiki entry) unless configured to use something else (it will also check the /sdcard version of the default path). If the FireTV is using some other path then you'll need to set that by specifying the correct path for the userdata property. The userdata path should be referenced in your xbmc.log, look for "special://masterprofile/ is mapped to". If not obvious, upload the log to pastebin. RE: [RELEASE] Texture Cache Maintenance utility - Maetrik - 2014-10-21 The log says: special://masterprofile/ is mapped to: /storage/emulated/0/Android/data/org.xbmc.xbmc/files/.xbmc/userdata which i tried already. This is my cfg: sep = | userdata = /storage/emulated/0/Android/data/org.xbmc.xbmc/files/.xbmc/userdata/ dbfile = Database/Textures13.db thumbnails = Thumbnails/ xbmc.host = 192.168.100.39 webserver.port = 8083 rpc.port = 9090 download.threads = 2 extrajson.albums = extrajson.artists = extrajson.songs = extrajson.movies = extrajson.sets = extrajson.tvshows.tvshow = extrajson.tvshows.season = extrajson.tvshows.episode= qaperiod = 30 qa.file = no cache.castthumb = no logfile = logfile.verbose = no network.mac = Ports are doublechecked, XBMC is set to allow programs to on other systems to control XBMC, and allowance to control of XBMC via HTTP is also set. This is what Texture Cache's log says: http://pastebin.com/YYPTtfnD I guess it's a read/write error and my FireTV is not rootable to change file permissions RE: [RELEASE] Texture Cache Maintenance utility - Milhouse - 2014-10-21 1. That's a really old version of texturecache.py (v0.8.9) that you have - the current version is v1.7.9. Try running "texturecache.py update" 2. Change you texturecache.cfg file to be *just* the following - everything else you have is already the default and not required: Code: userdata = /storage/emulated/0/Android/data/org.xbmc.xbmc/files/.xbmc/userdata/ According to the log, your current client platform is "Darwin", which would suggest you're running this script on a Mac, so presumably 192.168.100.39 is your FireTV client but your Mac isn't going to be able to access the Android userdata folder. Not that you need access to the userdata folder to perform the "c" option using recent versions of the script as it will be done entirely using JSON. Trying "c" with the above configuration and v0.8.9 of the script probably explains why it is failing. So upgrade to v1.7.9, then either run the script on the FireTV (and remove xbmc.host from your config so that it defaults to localhost) or run it on your Mac connecting to the FireTV (but remove the userdata entry from your config). 3. If v1.7.9 is still not working, submit a new log (add @logfile=/tmp/tc.log to temporarily enable logging), and also copy/paste whatever you see in the console so that I know the error you are experiencing RE: [RELEASE] Texture Cache Maintenance utility - Maetrik - 2014-10-21 I love you so much right now :-* After updating, everything works like charm - thank you so much. Didnt notice this was an old version as the other ones i use keeps updating themselves RE: [RELEASE] Texture Cache Maintenance utility - Milhouse - 2014-10-22 Version 1.8.0
RE: [RELEASE] Texture Cache Maintenance utility - Milhouse - 2014-10-25 Version 1.8.1
RE: [RELEASE] Texture Cache Maintenance utility - QuattroGam3r - 2014-10-28 Thank you for this script Milhouse, i've been getting used to it for a while now and it's great. I Use it on my Pi and it works flawless, but I have a Pi in another room with multiple profiles on it. Is there a way to direct it at a certain profile's artwork, not sure how to set that up over here. RE: [RELEASE] Texture Cache Maintenance utility - Milhouse - 2014-10-28 (2014-10-28, 02:39)gardnerd4me Wrote: Thank you for this script Milhouse, i've been getting used to it for a while now and it's great. I Use it on my Pi and it works flawless, but I have a Pi in another room with multiple profiles on it. Is there a way to direct it at a certain profile's artwork, not sure how to set that up over here. There is a JSON method to load a profile on demand - I could add see about adding support for that and then the JSON methods would act against the currently loaded profile, although this might cause mayhem if someone is using the device at the time you run the script. Or you can just load the profile to be updated and run the script. Right now the script isn't particularly profile aware, for instance the X/Xd/r/R/p/P commands will default to the userdata folder of the master profile, and you would need to specify the location of each profiles userdata folder (eg. /storage/.kodi/userdata/profiles/myprofile) so that the default master profile location isn't used. You could create a [section] in your config file for each profile and configure the userdata folder within each section which would go part of the way to making the script more tolerant of profiles, then run the script specifying @section=<section-name> to work with the relevant profile. The final step would be to automatically load the profile as part of an update or query action (c/C/jd etc.), assuming the required profile isn't already loaded. The profile name would be another property to be specified in the section. RE: [RELEASE] Texture Cache Maintenance utility - QuattroGam3r - 2014-10-28 (2014-10-28, 03:12)Milhouse Wrote: There is a JSON method to load a profile on demand - I could add see about adding support for that and then the JSON methods would act against the currently loaded profile, although this might cause mayhem if someone is using the device at the time you run the script. I'm not too comfortable running the JSON commands, still learning things. Are you saying that it currently runs on .xbmc-current? If so then no problem here. I just didn't know how it handled profiles. I'll give it a shot and post back if I have any problems. Thanks for the advice. RE: [RELEASE] Texture Cache Maintenance utility - Milhouse - 2014-10-28 The options that use JSON will query or update the currently loaded profile - JSON options are those such as jd, s, x, c, C, p, P, purge, qa, qax, query etc. The options that require direct file system access will by default use only the master profile unless you configure the userdata property with the path for a specific profile. Options that require direct file system access are f, F, r, R, S, X and Xd. As of right now, the script can be made to work with profiles provided you configure the correct userdata path (for use by the direct file system options) and remember to load the correct profile before running the script when using the JSON options. The missing functionality is for the script to automatically load the required profile (and possibly automatically adjust the default userdata path when a non-master profile is used) so that you don't have to remember to do so. RE: [RELEASE] Texture Cache Maintenance utility - QuattroGam3r - 2014-10-28 Ok, thanks for the clarification. I haven't used the JSON query yet (iirc, I thought you said it was much faster). I'll have to play around with that and get used to it. Thanks again for your help Milhouse. RE: [RELEASE] Texture Cache Maintenance utility - Milhouse - 2014-10-29 Version v1.8.2
|