[d_v_ant1]

I am currently using Kodi 17 with the metropolis skin, I am have an issue trying to get Artist slideshow to work. When I backspace to the visualization screen it shows the default fanart background image for the artist and won't change. But when i press backspace again to return to main screen i get a flash of another picture. It seems artist slideshow is working behind the default fanart background. Any help would be appreciated.

[msfc]

I suspect the black screen happens when Kodi switches tracks (this is in Party Mode) just as AS has faded out a piece of the previous artist's art while transitioning to another piece of that artist's art.

This guess is wrong. I have just had the problem occur when transitioning between 2 artists for neither of whom AS found any art. While the first artist's track was playing, the standard Estuary background was displayed. During the second the black screen. This might be a problem with the underlying Estuary skin rather than AS. I'll try turning off AS and will report back.

[msfc]

I tried both Kodi 17 & 17.1 standard Estuary skins and did not see the black-screen-when-art-not-found problem. It only happens with the mod'ed skin and AS running. I can't disable AS to try the mod'ed skin alone. Kodi says it can't be disabled because it is in use by the mod'ed skin. It says this even when I'm using a different skin. BTW, I have the "Use transparent image when no art is found" option turned on in AS settings.

The change of the top & bottom text & progress bar disappearing from the OSD when the album art, title, etc. disappear, that I mentioned upstream, is indeed a 17.1 change.

Blending of fanart with the blue background happens in the standard skin. I'm going to file a bug against Estuary. Done. The bug is http://trac.kodi.tv/ticket/17385.

[Dave.B]

@pkscout, I have noticed a strange behavior of AR. sometimes the AR get stuck and show fanart of a certain artist even though the song changed to another. Its very rare but it happened a couple of times each time with a different artist. I have the debug option on. How can I check to see what causes this behavior?

[pkscout]

@pkscout, I have noticed a strange behavior of AR. sometimes the AR get stuck and show fanart of a certain artist even though the song changed to another. Its very rare but it happened a couple of times each time with a different artist. I have the debug option on. How can I check to see what causes this behavior?

If you have debugging on in Kodi and AS, you can look through the log and track what AS does during the song change. If you get a log that shows it, I can look at the log too. Just post a link to it here.

[ajerazzor]

@pkscout can we have something to remove the transparency from the estuary skin when running full screen?

[pkscout]

@pkscout can we have something to remove the transparency from the estuary skin when running full screen?

asked and answered in the Estuary mod thread:

http://forum.kodi.tv/showthread.php?tid=...pid2548325

[msfc]

@pkscout over in the AS wiki you write

There are a number of skins that support Artist Slideshow, but keeping a running list of them has proved too much work.

It is a wiki, editable by anyone registered. Did you try making a page to which skin authors could add their AS supporting skins themselves? If users or you think the support by a particular skin is crap they or you can remove it.

[Dave.B]

@pkscout, I have noticed a strange behavior of AR. sometimes the AR get stuck and show fanart of a certain artist even though the song changed to another. Its very rare but it happened a couple of times each time with a different artist. I have the debug option on. How can I check to see what causes this behavior?

If you have debugging on in Kodi and AS, you can look through the log and track what AS does during the song change. If you get a log that shows it, I can look at the log too. Just post a link to it here.

@pkscout. It happened again.
Don't know why but the last 3 times it happened it got stuck on the pictures of the artist "Dream Theater".
Here is the log file:
https://paste.ubuntu.com/24195218/

Thanx

[pkscout]

@pkscout. It happened again.
Don't know why but the last 3 times it happened it got stuck on the pictures of the artist "Dream Theater".
Here is the log file:
https://paste.ubuntu.com/24195218/

Two things:

1- It looks like while you had AS debug logging on, you didn't have Kodi debug logging on, so there's not much in the logs. If you enable Kodi debug logging from the GUI, you're going to have this horrid overlay on the screen all the time, so you might take a look at this to enable it in the advancedsettings.xml file (which doesn't cause the overlay):

http://kodi.wiki/view/Log_file/Advanced#...ngs.xml.29

2- The version of AS is reporting back as 2.0.7.2. That's odd, because the current version is 2.0.7, and I don't number my addons that way.

[Dave.B]

@pkscout. It happened again.
Don't know why but the last 3 times it happened it got stuck on the pictures of the artist "Dream Theater".
Here is the log file:
https://paste.ubuntu.com/24195218/

Two things:

1- It looks like while you had AS debug logging on, you didn't have Kodi debug logging on, so there's not much in the logs. If you enable Kodi debug logging from the GUI, you're going to have this horrid overlay on the screen all the time, so you might take a look at this to enable it in the advancedsettings.xml file (which doesn't cause the overlay):

http://kodi.wiki/view/Log_file/Advanced#...ngs.xml.29

2- The version of AS is reporting back as 2.0.7.2. That's odd, because the current version is 2.0.7, and I don't number my addons that way.

@pkscout

Thanks for the quick reply.

1- As for the AS version I installed Kodi Brazil repo and installed mq7 skin from there. I see now that the upgrade to the 2.0.7.2 Ver. came automatically from that repo.

2- I enabled logging through advancedsettings.xml, now I have to wait for the next bug.

[Dave.B]

@pkscout. It happened again.
Don't know why but the last 3 times it happened it got stuck on the pictures of the artist "Dream Theater".
Here is the log file:
https://paste.ubuntu.com/24195218/

Two things:

1- It looks like while you had AS debug logging on, you didn't have Kodi debug logging on, so there's not much in the logs. If you enable Kodi debug logging from the GUI, you're going to have this horrid overlay on the screen all the time, so you might take a look at this to enable it in the advancedsettings.xml file (which doesn't cause the overlay):

http://kodi.wiki/view/Log_file/Advanced#...ngs.xml.29

2- The version of AS is reporting back as 2.0.7.2. That's odd, because the current version is 2.0.7, and I don't number my addons that way.

@pkscout

Thanks for the quick reply.

1- As for the AS version I installed Kodi Brazil repo and installed mq7 skin from there. I see now that the upgrade to the 2.0.7.2 Ver. came automatically from that repo.

2- I enabled logging through advancedsettings.xml, now I have to wait for the next bug.

@pkscout
It happened again. log file is:
https://paste.ubuntu.com/24212806
Again it was stuck on the same artist "Dream Theater".
Thanks for all your help

[pkscout]

@pkscout
It happened again. log file is:
https://paste.ubuntu.com/24212806
Again it was stuck on the same artist "Dream Theater".
Thanks for all your help

Well, I have good news and I have bad news. The good news is that this time your log file had an actual crash logged for AS, so I was able to make some changes to keep that from happening. I've pushed a beta to my beta repo channel for testing. If all goes well I should be able to release an update later this week to the main repo. I have no idea what that will mean for you though, since you have that oddly numbered version from the Brazilian repo.

The bad news is that your log still isn't showing any debug information (it seems to be set to give error, warning, and notice, but not debug), so I'm not sure if I actually fixed your problem or not. The log file before didn't have any crash that I remember, so it's possible there's still something else going on.

[Dave.B]

@pkscout
It happened again. log file is:
https://paste.ubuntu.com/24212806
Again it was stuck on the same artist "Dream Theater".
Thanks for all your help

Well, I have good news and I have bad news. The good news is that this time your log file had an actual crash logged for AS, so I was able to make some changes to keep that from happening. I've pushed a beta to my beta repo channel for testing. If all goes well I should be able to release an update later this week to the main repo. I have no idea what that will mean for you though, since you have that oddly numbered version from the Brazilian repo.

The bad news is that your log still isn't showing any debug information (it seems to be set to give error, warning, and notice, but not debug), so I'm not sure if I actually fixed your problem or not. The log file before didn't have any crash that I remember, so it's possible there's still something else going on.

@pkscout Thanks for all your effort.
As for the good news I will install your beta update and see if it solves the problem. should I delete the Brazilian ver. first or I can just install your Ver. upon that Ver. ?
As for the bad news, is there something I can do to make the log showing debug information ?

[pkscout]

@pkscout Thanks for all your effort.
As for the good news I will install your beta update and see if it solves the problem. should I delete the Brazilian ver. first or I can just install your Ver. upon that Ver. ?
As for the bad news, is there something I can do to make the log showing debug information ?

I think if you install my beta repo and then have Kodi do a addon update it will pull from there because the 2.0.8~beta1 is newer than the 2.0.7.2 in the Brazilian repo. You can get my beta repo (which is good for Kodi Helix and later) from here:

https://github.com/pkscout/repository.be...-1.1.0.zip

As for the logging, you need to make sure this is in your advancedsettings.xml and restart Kodi:

Code:

<loglevel hide="false">1</loglevel>

(technically the hide attribute can be true or false)

That's from this wiki page:

http://kodi.wiki/view/advancedsettings.xml