Posts: 3,444
Joined: Jan 2011
Reputation:
362
pkscout
Team-Kodi Member
Posts: 3,444
1.6.2 Pushed to Main Repo
I have put in a request to the XBMC team to update Artist Slideshow to 1.6.2. This should resolve the crash issue folks saw with 1.6.0 and 1.6.1. Hopefully this will start being available later today. If you aren't seeing the update by tomorrow, I'd try forcing a refresh of the main XMBC repo.
My apologies that I so thoroughly messed up these last couple updates. My test systems ended up with a strange version of a python module, so things that looked like their were working really weren't. I think I have everything resolved now, so next time I can have a different problem. '-)
Posts: 3,444
Joined: Jan 2011
Reputation:
362
pkscout
Team-Kodi Member
Posts: 3,444
2014-02-21, 08:41
(This post was last modified: 2014-02-21, 08:42 by pkscout.)
1.6.0 and 1.6.1 are broken. That's totally my fault. 1.6.2 will fix everything, and I'm hoping it will make it into the repo soon. The XBMC devs ask developers not to do updates more than once a month, and because I did a bad job testing I've had to do three updates this week. So I won't be surprised if it takes a little longer for them to get to the last update.
If you're really desperate, you can download the beta listed a few posts up. Otherwise this should all resolve itself in the next day or so. Again,my apologies.
Posts: 12
Joined: Jan 2014
Reputation:
0
I just got home, turned on XBMC and got the "Artist Slideshow Updated" message on my screen. Checked the info, and it's pulled in 1.6.2 already! Slideshow appears to be working just fine (XBMC Gotham Alpha 11, Aeon Nox 4)
Posts: 548
Joined: Feb 2009
Reputation:
4
Before updating to 1.6.2 the vizualiazation fanart was truly stuck on an artist from a few days ago, even after a reboot. Deleting the add-on folder (not the data folder) and replacing with 1.6.2 fixed it (at least for now). I recall this happeneing some weeks ago, where a manual update reset things back to normal. Obviously I'll post any future issues. Thanks for the update.
Win10x64 Pro. Intel Core2Duo E8500 3.26GHz on Gigabyte GA-EP43-UD3L. 4GB DDR2 1066MHz RAM. Nvidia GT240 512MB PCIx16. Multiple displays, including Sony VPL-XW5000ES 4k projector + 100" Da-Lite Cinema screen.
Posts: 4
Joined: Feb 2014
Reputation:
0
Hi,
I was working on a fresh install of my htpc when you pushed the "broken" versions, so i reinstall my system quite a few times these last days, and found this thread.
Here is my feedback if it can help :
Everything works fine with 1.6.2 on an XBMCbuntu fresh install.
But still getting the 'error script failed' on a fresh install of OpenELEC (Frodo 12.2).
Is there still something to be fixed on a future 1.6.3 to work with OpenELEC ? If not i'll try to get a previous working version of artist slideshow.
Thanks.
Posts: 346
Joined: Dec 2011
Reputation:
0
I love this add on, but having some small problems. From version 1.6.0 onwards, they work but are for me, slow and it's hit or miss if it finds the artist. So I've reverted back back to version 1.5.9 and it works absolutely great. One question, everytime you check the information of an artist, does it go back to Last.FM or does it recover the information locally, because it has downloaded that information before. If it's the latter, where is this stored. The reason I ask is, I have an artist it didn't fine originally and now it seems stuck that it won't look for that artist. I know that the artist is there, because my other PC found them.
Any help would be appreciated.
Posts: 12
Joined: Jan 2014
Reputation:
0
Apparently I spoke too soon as well... The script will display artwork for a few artists, then randomly stop updating and just keep looping artwork for the last artist it found. Last night it hung on Paul Simon, tonight I don't know exactly when it stopped working, but it's been showing a black screen for the last two artists (on Party Mode - Garth Brooks, and Matchbox 20.) Both of whom I not only have seen artwork for, but definitely have artwork in the local cache (both Artist Slideshow cache and XBMC cache - don't get me started on that!) Guess I should enable debug logging so I can help with the solution instead of just being obnoxious.