fanart.tv forums

I have three Android TV Boxes.

1. Nvidia Shield Tablet - Kodi (16.1 PLAY STORE Version)
2. MINIX NEO U1 - XMBC (XMBC for MINIX 16.3 Dedicated Hardware Version)
3. BEELINK S82 PLUS - Kodi (16.1 PLAY STORE Version)

All are using the same Skin (AEON MQ6 Isegaard v3.3.0.10 dated 9th February 2016) and Artwork Downloader AD-ON (v13.1.0), but the Fanart updates aren't coming down to all the machines. That is to say, my MINIX will receive new artwork but the other two don't and a combination of all three. It simply doesn't make sense, it either is available or it's not and all machines should be able to download the appropriate images when they become available.

Also, it takes over at least a week and 3 or 4 days in which to receive new images that I've created and uploaded myself. Why is there such a huge delay? TVDB takes no longer than 1Hr to have the images cached in their system to be available, yet Fanart takes well over a week? Is this a bug? Is it related to the fact my 3 systems don't receive updates at the same time?

Any help would be very much appreciated.

Cheers

Ad

Probably to do with this: https://fanart.tv/2015/01/personal-api-keys/ certainly the delay in time is, not sure I understand the other questions, but most plugins implement their own caching system on top of what fanart.tv implements.

Hope that helps.

Kode wrote:Probably to do with this: https://fanart.tv/2015/01/personal-api-keys/ certainly the delay in time is, not sure I understand the other questions, but most plugins implement their own caching system on top of what fanart.tv implements.

Thank you KODE for your reply,

OK, now I understand the time element. However, where is this posted in terms of the ADD-ON? For example, I had no idea this API key issue affected the download time. If someone doesn't contribute to the site, how does the Kodi end user find out this information and become a member and receive VIP API status? As a suggestion, it would be a better option to place this information on the ADD-ON page within KODI which explains this time element. That way you will get more exposure. I'm a contributor and I had no idea! So this information hasn't been overly publicised.

Also, as a Contributor myself, I would suggest that they receive the option: "Software using v3 AND sending a users valid personal API key will see that image on the 3rd of January." as standard. Again, as a suggestion, a Contributor receives it after X amount of points, that way it weeds out people making one image and getting new privileges without giving back to the site.

HOWEVER, it still doesn't make any sense that say my MINIX box downstairs and my NVIDIA SHIELD upstairs don't receive the updates on the same day/hour etc. This makes no sense. OK they are being received by the same IP Address etc, but after said X delay ie 2 weeks say, the Clear ART images for eg "JOE BLOGS" isn't available to both machines on the same day. This appears to be an API checking error. It sees my machines as two devices but one receives the images the other doesn't. Obviously days maybe a week later it turns up, but that makes it 3 weeks almost. This appears to me as a bug. My kids BEELINK also has received Kids images faster than both my main machines too, which again suggests there is an API checking bug.

Cheers

We have no control over 3rd party plugins, so if they don't communicate this information to their users there isn't a lot we can do (there are hundreds, if not thousands of apps/plugins using our API). As a user of the 3rd party plugin I'd suggest you contacting the plugin author and making the suggestion, it would likely have more impact from users than us.

That's a good suggestion, I will look into implementing it for the new site.

As for you last issue, I'm not 100% sure, but iirc artwork downloader implements it's own caching of a week or so, and this caching is specific to the box, so if you check for an image on box 1 at 3pm, then on box 2 at 6pm or even the next day, that would account for the discrepencies, and again, completely out of our control. I believe the only way you could route round that is to run something like kodi headless to do the lookups and grab the data from that, but I have no experience with that.