[BUG - OUTSTANDING] Image transition glitch in Showcase

[mindweaver]

I don't know if it can be fixed but..

When you are browsing movies in library mode (i.e. movies) and going from one movie to another you can see a little bit of the main menu backdrop in between the fades.

Scenario: I have the movie Clerks II in focus, I can see poster and fanart. When I press right on my remote to bring the next movie (let's say Twilight) to focus I can see the Clerks II fanart fade out to reveal the main menu backdrop for about half a second and after that the Twilight fanart fades into focus.

I hope this glitch is fixable.

(I have also noticed something else that has nothing to do with this. When you are adding a source and choosing to either edit/delete or create a network source.. the windows pops up behind the "add source" window and making it impossible to navigate. Might be a XBMC issue, not sure)

[Discaciate]

It is fixable.
If I well recall, it's because you are using an old xbmc build.
Try a newer one and see if it works.

[djh_]

Are you sure the first issue isn't to do with an old XBMC build?

I'll look into the one about the dialogs popping under each other.

[mindweaver]

Fast answers :)

I am running XBMCSetup-Rev19102, so not that old :;):

[Bebdown]

Same issue for me, with last XBMC Build

[Halibutt]

I already reported that here (http://xbmc.org/forum/showthread.php?t=47942). Indeed, it's a XBMC issue and not related to Stark by itself. Upgrading to one of the versions suggested by _djh fixes the problem completely.
Cheers

[mindweaver]

I already reported that here (http://xbmc.org/forum/showthread.php?t=47942). Indeed, it's a XBMC issue and not related to Stark by itself. Upgrading to one of the versions suggested by _djh fixes the problem completely.
Cheers

I am running XBMCSetup-Rev19115 and the problem persists. So NO, installing a new version will not fix the problem.

[Halibutt]

I am running XBMCSetup-Rev19115 and the problem persists. So NO, installing a new version will not fix the problem.I installed the version suggested by _djh at aeonproject.com (Build 19052 (http://www.mediafire.com/?ymmzwg1lxgo)) and it works as designed.
Cheers

[mindweaver]

I installed the version suggested by _djh at aeonproject.com (Build 19052 (http://www.mediafire.com/?ymmzwg1lxgo)) and it works as designed.
Cheers

The skin is marginally slower on 1080p screen than a lower res counterpart, that may be why my eyes are able to see it. There is an improvement with the newer build but the problem is still there.

[Bebdown]

Halibutt has right, I install the Build 19052 and backdrop fade work fine.

But it could be good if it could work on Atlantis 8.10

[Halibutt]

Yup, it should work out of the box. I'm a typical end-user, which means that I visit program's homepage and expect the download link to point to the "good, working version". Apparently this is not the case with XBMC. It took me a while to realize that there are different, better versions available.
Cheers

[CF2009]

to fix the bug open up MyVideoNav.xml and find the code below (the 1st 2 multiimage in MyVideoNav.xml)


<control type="multiimage">
<include>Background_SingleImage</include>
<imagepath>backdrops/default_movies</imagepath>
<info>Skin.String(CustomMovies)</info>
<visible>!Skin.String(CustomMoviesFolder)</visible>
<visible>Skin.HasSetting(videomovies)</visible>
</control>

<control type="multiimage">
<include>Background_ImageFolder</include>
<info>Skin.String(CustomMoviesFolder)</info>
<visible>Skin.String(CustomMoviesFolder)</visible>
<visible>Skin.HasSetting(videomovies)</visible>
</control>


Replace With:

<control type="multiimage">
<include>Background_SingleImage</include>
<imagepath>backdrops/default_movies</imagepath>
<info>Skin.String(CustomMovies)</info>
<visible>!Skin.String(CustomMoviesFolder)</visible>
<visible>Skin.HasSetting(videomovies)</visible>
<!-- Fix >>>>>>>-->
<visible>Skin.HasSetting(nomoviefanart)|IsEmpty(listitem.pr operty(fanart_image))</visible>
<visible>[IsEmpty(Fanart.Image)+IsEmpty(listitem.property(fa nart_image))] | Skin.HasSetting(notvfanart)</visible>
<!-- <<<<<<< Fix -->
</control>

<control type="multiimage">
<include>Background_ImageFolder</include>
<info>Skin.String(CustomMoviesFolder)</info>
<visible>Skin.String(CustomMoviesFolder)</visible>
<visible>Skin.HasSetting(videomovies)</visible>
<!-- Fix >>>>>>> -->
<animation effect="fade" start="0" end="100" time="300" condition="Skin.HasSetting(nomoviefanart)|IsEmpty(listitem.pr operty(fanart_image))">Conditional</animation>
<!-- <<<<<<< Fix -->
</control>


Post back if it works for you :;):

[mindweaver]

to fix the bug open up MyVideoNav.xml and find the code below (the 1st 2 multiimage in MyVideoNav.xml)


<control type="multiimage">
<include>Background_SingleImage</include>
<imagepath>backdrops/default_movies</imagepath>
<info>Skin.String(CustomMovies)</info>
<visible>!Skin.String(CustomMoviesFolder)</visible>
<visible>Skin.HasSetting(videomovies)</visible>
</control>

<control type="multiimage">
<include>Background_ImageFolder</include>
<info>Skin.String(CustomMoviesFolder)</info>
<visible>Skin.String(CustomMoviesFolder)</visible>
<visible>Skin.HasSetting(videomovies)</visible>
</control>


Replace With:

<control type="multiimage">
<include>Background_SingleImage</include>
<imagepath>backdrops/default_movies</imagepath>
<info>Skin.String(CustomMovies)</info>
<visible>!Skin.String(CustomMoviesFolder)</visible>
<visible>Skin.HasSetting(videomovies)</visible>
<!-- Fix >>>>>>>-->
<visible>Skin.HasSetting(nomoviefanart)|IsEmpty(listitem.pr operty(fanart_image))</visible>
<visible>[IsEmpty(Fanart.Image)+IsEmpty(listitem.property(fa nart_image))] | Skin.HasSetting(notvfanart)</visible>
<!-- <<<<<<< Fix -->
</control>

<control type="multiimage">
<include>Background_ImageFolder</include>
<info>Skin.String(CustomMoviesFolder)</info>
<visible>Skin.String(CustomMoviesFolder)</visible>
<visible>Skin.HasSetting(videomovies)</visible>
<!-- Fix >>>>>>> -->
<animation effect="fade" start="0" end="100" time="300" condition="Skin.HasSetting(nomoviefanart)|IsEmpty(listitem.pr operty(fanart_image))">Conditional</animation>
<!-- <<<<<<< Fix -->
</control>


Post back if it works for you :;):

yeah it seems to work :) thanks!

[Bebdown]

I tried it on my Atlantis 8.10 installation but there is no change.

I installed Build 19052 on my media center, but thumbs & backdrop don't appear on screen, but on my laptop yes ... I don't understand.

Xbmc is really a curious thing

[Guttasej]

Yup, it should work out of the box. I'm a typical end-user, which means that I visit program's homepage and expect the download link to point to the "good, working version". Apparently this is not the case with XBMC. It took me a while to realize that there are different, better versions available.
Cheers

XBMC is still in heavy development for all PC based systems. Hence the drastic changes.

[jmarshall]

Why is the above fix needed?

The largeimage control holds on to the previous image while the next one loads, so there should be no flashing of things underneath it at all with recent versions of XBMC.

If it is flashing, then hiding what's underneath it doesn't sound like the way to go about attempting to fix it (assuming it's not flashing for a reason).

Cheers,
Jonathan

[CF2009]

Why is the above fix needed?

The largeimage control holds on to the previous image while the next one loads, so there should be no flashing of things underneath it at all with recent versions of XBMC.

If it is flashing, then hiding what's underneath it doesn't sound like the way to go about attempting to fix it (assuming it's not flashing for a reason).

Cheers,
Jonathan

what it look like is largeimage control is fading the 1st image out at the same time as fading the next one in so if you have the smallest lag you will have 1 image @ 50% fade and the next image @ say 40% equalling 90% over all so any think underneath is seen through the fading animation.
i'm just guessing but that is what it looks like...

[jmarshall]

Gotcha - the fade is indeed done so that at the midpoint, both images are approximately at an alpha of 0.7, so it is feasible that you may get leakthrough - particularly on images that are reasonably flat in colour (as busy colour is likely to mask this effect).

It's impossible to avoid leak-through in this circumstance and still achieve a smooth fade - the reason being that the only way to be technically correct is to hold the current image while blending the new one. This doesn't look too flash when the images are different dimensions, however. We thus drop back from technically correct, to one where we assume the images are slightly transparent themselves. This allows a smooth transistion function that ensures the old image is completely faded out at the point where the next one is faded in.

Cheers,
Jonathan