[pkscout]

The same behavior is found in the windows versions as well.   So some change was made between 17.6 and 18.1 on how KODI displays images. 

That being said it's definitely not a AS problem, but the problem seriously affects the way the images look when displayed.  

Not sure where to go from here unless you can send it back to the dev's for a resolution.

I think I found the difference between the v17 and v18 skin.  If you go to my v18 mod folder and look for xml/MusicVisualization.xml you can change line 43 from:

Code:

<aspectratio>scale</aspectratio>

to:

Code:

<aspectratio>keep</aspectratio>

I think that will revert back the behavior.  I've been pretty consistent about not wanting to change much of the default Estuary behavior in my mod except for the home screen customization, so I need to decide if I'm going to consider this a bug and fix it or just leave it.  I just hate the idea that any time I update my mod that you'd have to manually make that change.  So maybe there's a new option to add to the mod.  '-)  

 Ok I changed it as suggested.  It does change the behavior back to the original.  

There is however another problem.  The images are displayed on top of the fan art, and the fan art always displays around the edges. 

With it set to scale you just can't see the fan art because each image covers the whole screen.  In previous versions the fan art displayed as the first image and then the slide show started. 

OK, now I feel like I really am going to have to do this as a setting.  But here's something else to try.  Right above the multiimage control you just modified is another one that looks like this:

Code:

            <control type="image">
                <aspectratio>scale</aspectratio>
                <fadetime>400</fadetime>
                <animation effect="fade" start="0" end="100" time="400">WindowOpen</animation>
                <animation effect="fade" start="100" end="0" time="300">WindowClose</animation>
                <texture background="true">$INFO[Player.Art(fanart)]</texture>
            </control>

Try deleting all that.  I'm pretty sure that's what is showing the single fanart in the background of your non-full size images.

[tscholl]

I think I found the difference between the v17 and v18 skin.  If you go to my v18 mod folder and look for xml/MusicVisualization.xml you can change line 43 from:

Code:

<aspectratio>scale</aspectratio>

to:

Code:

<aspectratio>keep</aspectratio>

I think that will revert back the behavior.  I've been pretty consistent about not wanting to change much of the default Estuary behavior in my mod except for the home screen customization, so I need to decide if I'm going to consider this a bug and fix it or just leave it.  I just hate the idea that any time I update my mod that you'd have to manually make that change.  So maybe there's a new option to add to the mod.  '-)   

 Ok I changed it as suggested.  It does change the behavior back to the original.  

There is however another problem.  The images are displayed on top of the fan art, and the fan art always displays around the edges. 

With it set to scale you just can't see the fan art because each image covers the whole screen.  In previous versions the fan art displayed as the first image and then the slide show started.  

OK, now I feel like I really am going to have to do this as a setting.  But here's something else to try.  Right above the multiimage control you just modified is another one that looks like this:

Code:

            <control type="image">
                <aspectratio>scale</aspectratio>
                <fadetime>400</fadetime>
                <animation effect="fade" start="0" end="100" time="400">WindowOpen</animation>
                <animation effect="fade" start="100" end="0" time="300">WindowClose</animation>
                <texture background="true">$INFO[Player.Art(fanart)]</texture>
            </control>

Try deleting all that.  I'm pretty sure that's what is showing the single fanart in the background of your non-full size images. 

I deleted the code as suggested, and that does get rid of the fanart in the background.   However now the fan art never displays as the first image.  Instead the last image of the previous artist is displayed briefly,  and then it goes into the new slide show.

[tscholl]

What I deleted was.

<control type="image">
            <left>0</left>
            <top>0</top>
            <width>100%</width>
            <height>100%</height>
            <aspectratio>scale</aspectratio>
            <fadetime>400</fadetime>
            <animation effect="fade" start="0" end="100" time="400">WindowOpen</animation>
            <animation effect="fade" start="100" end="0" time="300">WindowClose</animation>
            <texture background="true" colordiffuse="$VAR[BackgroundDiffusion]">colors/black.png</texture>
            <visible>Player.ShowInfo | Window.IsActive(musicosd)</visible>
        </control>

Which is slightly different that your post.

[pkscout]

 Ok I changed it as suggested.  It does change the behavior back to the original.  

There is however another problem.  The images are displayed on top of the fan art, and the fan art always displays around the edges. 

With it set to scale you just can't see the fan art because each image covers the whole screen.  In previous versions the fan art displayed as the first image and then the slide show started.  

OK, now I feel like I really am going to have to do this as a setting.  But here's something else to try.  Right above the multiimage control you just modified is another one that looks like this:

Code:

            <control type="image">
                <aspectratio>scale</aspectratio>
                <fadetime>400</fadetime>
                <animation effect="fade" start="0" end="100" time="400">WindowOpen</animation>
                <animation effect="fade" start="100" end="0" time="300">WindowClose</animation>
                <texture background="true">$INFO[Player.Art(fanart)]</texture>
            </control>

Try deleting all that.  I'm pretty sure that's what is showing the single fanart in the background of your non-full size images.  

I deleted the code as suggested, and that does get rid of the fanart in the background.   However now the fan art never displays as the first image.  Instead the last image of the previous artist is displayed briefly,  and then it goes into the new slide show. 

That's about as good as it's gonna get until I have some time to look in more detail at it on the skin side.

[pkscout]

 Ok I changed it as suggested.  It does change the behavior back to the original.  

There is however another problem.  The images are displayed on top of the fan art, and the fan art always displays around the edges. 

With it set to scale you just can't see the fan art because each image covers the whole screen.  In previous versions the fan art displayed as the first image and then the slide show started.  

OK, now I feel like I really am going to have to do this as a setting.  But here's something else to try.  Right above the multiimage control you just modified is another one that looks like this:

Code:

            <control type="image">
                <aspectratio>scale</aspectratio>
                <fadetime>400</fadetime>
                <animation effect="fade" start="0" end="100" time="400">WindowOpen</animation>
                <animation effect="fade" start="100" end="0" time="300">WindowClose</animation>
                <texture background="true">$INFO[Player.Art(fanart)]</texture>
            </control>

Try deleting all that.  I'm pretty sure that's what is showing the single fanart in the background of your non-full size images.  

I deleted the code as suggested, and that does get rid of the fanart in the background.   However now the fan art never displays as the first image.  Instead the last image of the previous artist is displayed briefly,  and then it goes into the new slide show. 

I just pushed an update to my Estuary mod that has an option in the settings to not scale artist images in the music visualization.  That should be much cleaner than trying to delete stuff out of that file.

[tscholl]

Sounds like a great idea. I'll keep an eye out for the update and let you know how I make out.  What is the new version number

Thanks for the update

[pkscout]

Sounds like a great idea. I'll keep an eye out for the update and let you know how I make out.  What is the new version number

Thanks for the update

1.2.0

[tscholl]

Sounds like a great idea. I'll keep an eye out for the update and let you know how I make out.  What is the new version number

Thanks for the update

1.2.0 

The Skin updated and I updated the settings.  Having it as a setting was a great idea!!

When you get a chance you'll have to figure out why the previous artist is shown when it changes to the next artist.  I can tell you that it actually overlays the fanart.  The correct fanart can be seen around the edges.  Good luck with that.

Thanks for a quick fix workaround!

[Hallucyn8]

I think I might have found a bug in the Fallback Slideshow feature.

I enabled the fallback slideshow and set a folder with images. In the most part this works as expected and uses those images when there are no images for the currently playing artist but if there is a secondary/featured artist that also has no images available the fallback slideshow does not start and just displays a black screen.

I do have secondary/featured artist images enabled and would like to keep this option.

This should be fixed in 2.14~beta2.  I just released it into my beta repo.  If you want to try it you can install my beta repo and update AS from that.

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

Otherwise I'll probably put in the request to update the main repo in the next few days. 

Great, thanks for that

[eljejer]

Hello. I'm struggling to get AS to work as expected. The fanart is just not being shown ever. I'm using the Amber skin that has a setting to use AS or not. Obviously, this is set to Yes.
When I play the same album on Estuary skin, the fanart is being shown.
I have already reset the music library (deleted the music source and re-added it, fully scraped the music library and exported the library to Artist Information folder.
What more can I do to resolve this? Any help is appreciated.
I attach the log file here.

[pkscout]

Hello. I'm struggling to get AS to work as expected. The fanart is just not being shown ever. I'm using the Amber skin that has a setting to use AS or not. Obviously, this is set to Yes.
When I play the same album on Estuary skin, the fanart is being shown.
I have already reset the music library (deleted the music source and re-added it, fully scraped the music library and exported the library to Artist Information folder.
What more can I do to resolve this? Any help is appreciated.
I attach the log file here.

In that log AS is constantly starting and then stopping because it appears no music is playing.  The fact that it works with Estuary points to a skin problem.  I'm not familiar with Amber or how to calls AS, so you might try in the Amber skin thread:

https://forum.kodi.tv/forumdisplay.php?fid=203

If the devs have any thoughts that I can help with, I'm happy to.

[HeresJohnny]

I'm using this add-on as a starting point for my post although the problem that occurs is almost certainly due to underlying functions.
In my log I keep seeing this kind of warning when artwork is pulled to the music OSD:

Code:

2019-05-03 18:07:11.474 T:2826888048 DEBUG: ffmpeg[A87EE370]: [swscaler] No accelerated colorspace conversion found from yuv420p to bgra.
2019-05-03 18:07:11.517 T:2826888048 DEBUG: DoWork - took 101 ms to load special://masterprofile/Thumbnails/d/d21a80f9.jpg


As far as I can tell this means that ffmpeg is either outdated or wrongly configured when scaling images so there's always a small CPU cost involved. Is there anything that can be done to achieve accelerated scaling?

[pkscout]

I'm using this add-on as a starting point for my post although the problem that occurs is almost certainly due to underlying functions.
In my log I keep seeing this kind of warning when artwork is pulled to the music OSD:

Code:

2019-05-03 18:07:11.474 T:2826888048 DEBUG: ffmpeg[A87EE370]: [swscaler] No accelerated colorspace conversion found from yuv420p to bgra.
2019-05-03 18:07:11.517 T:2826888048 DEBUG: DoWork - took 101 ms to load special://masterprofile/Thumbnails/d/d21a80f9.jpg


As far as I can tell this means that ffmpeg is either outdated or wrongly configured when scaling images so there's always a small CPU cost involved. Is there anything that can be done to achieve accelerated scaling?

All AS does is create a window property that points to a folder of images.  The actual rendering is handled by the skin, so this is either a skin or a general Kodi issue.  There isn't anything I can change in AS to fix that.

[scott967]

I'm using this add-on as a starting point for my post although the problem that occurs is almost certainly due to underlying functions.
In my log I keep seeing this kind of warning when artwork is pulled to the music OSD:

Code:

2019-05-03 18:07:11.474 T:2826888048 DEBUG: ffmpeg[A87EE370]: [swscaler] No accelerated colorspace conversion found from yuv420p to bgra.
2019-05-03 18:07:11.517 T:2826888048 DEBUG: DoWork - took 101 ms to load special://masterprofile/Thumbnails/d/d21a80f9.jpg


As far as I can tell this means that ffmpeg is either outdated or wrongly configured when scaling images so there's always a small CPU cost involved. Is there anything that can be done to achieve accelerated scaling?

Looking at the code on ffmpeg for libswscale (yuv2rgb.c) it appears that hardware acceleration is only available for power pc and x86 architectures.  It doesn't look like the code has changed since 2014.  I don't know if there is something Kodi needs to do when building to turn on this function.

scott s.
.

[manfeed]

Hi @pkscout 

Many thanks for your work in this addon, I've been using it for years now without any problem... however, recently I've noticed that similar artists images wasn't showing properly, in fact they all return this:



I looked in the AS addon data folder and saw that lastfmartistsimilar.nfo for each artist was pointing to that online image, as you can see:

xml:


<artist><name>Ashanti</name>

<mbid>b0e304ab-ab52-4e4c-bff5-eb0dff0b3d09</mbid>

<match>0.736042</match>

<url>https://www.last.fm/music/Ashanti</url>

<image size="small">https://lastfm-img2.akamaized.net/i/u/34s/2a96cbd8b46e442fc41c2b86b821562f.png</image>

<image size="medium">https://lastfm-img2.akamaized.net/i/u/64s/2a96cbd8b46e442fc41c2b86b821562f.png</image>

<image size="large">https://lastfm-img2.akamaized.net/i/u/174s/2a96cbd8b46e442fc41c2b86b821562f.png</image>

<image size="extralarge">https://lastfm-img2.akamaized.net/i/u/300x300/2a96cbd8b46e442fc41c2b86b821562f.png</image>

<image size="mega">https://lastfm-img2.akamaized.net/i/u/300x300/2a96cbd8b46e442fc41c2b86b821562f.png</image>

<image size="">https://lastfm-img2.akamaized.net/i/u/300x300/2a96cbd8b46e442fc41c2b86b821562f.png</image>

<streamable>0</streamable>

</artist>

<artist><name>Toni Braxton</name>

<mbid>3c8a8696-e176-4c46-a2d3-48b6b1525c7f</mbid>

<match>0.729155</match>

<url>https://www.last.fm/music/Toni+Braxton</url>

<image size="small">https://lastfm-img2.akamaized.net/i/u/34s/2a96cbd8b46e442fc41c2b86b821562f.png</image>

<image size="medium">https://lastfm-img2.akamaized.net/i/u/64s/2a96cbd8b46e442fc41c2b86b821562f.png</image>

<image size="large">https://lastfm-img2.akamaized.net/i/u/174s/2a96cbd8b46e442fc41c2b86b821562f.png</image>

<image size="extralarge">https://lastfm-img2.akamaized.net/i/u/300x300/2a96cbd8b46e442fc41c2b86b821562f.png</image>

<image size="mega">https://lastfm-img2.akamaized.net/i/u/300x300/2a96cbd8b46e442fc41c2b86b821562f.png</image>

<image size="">https://lastfm-img2.akamaized.net/i/u/300x300/2a96cbd8b46e442fc41c2b86b821562f.png</image>

<streamable>0</streamable>

</artist>

<artist><name>Mariah Carey</name>

<mbid>494e8d09-f85b-4543-892f-a5096aed1cd4</mbid>

<match>0.724704</match>

<url>https://www.last.fm/music/Mariah+Carey</url>

<image size="small">https://lastfm-img2.akamaized.net/i/u/34s/2a96cbd8b46e442fc41c2b86b821562f.png</image>

<image size="medium">https://lastfm-img2.akamaized.net/i/u/64s/2a96cbd8b46e442fc41c2b86b821562f.png</image>

<image size="large">https://lastfm-img2.akamaized.net/i/u/174s/2a96cbd8b46e442fc41c2b86b821562f.png</image>

<image size="extralarge">https://lastfm-img2.akamaized.net/i/u/300x300/2a96cbd8b46e442fc41c2b86b821562f.png</image>

<image size="mega">https://lastfm-img2.akamaized.net/i/u/300x300/2a96cbd8b46e442fc41c2b86b821562f.png</image>

<image size="">https://lastfm-img2.akamaized.net/i/u/300x300/2a96cbd8b46e442fc41c2b86b821562f.png</image>

<streamable>0</streamable>

</artist>

I guess there must be a problem with lastfm, isn't it?

Thanks!