#header.image can cause high CPU (2 Viewers)

[Harley]

mmh, thats realy curious.

does the problem only appears if the image is importat with #...., or also by using not importat files ?

The headerimages have not big sizes of kb´s, so not to understand why they should produce problems.
If the problem also appears with files that are not importat, we should do some test´s with different gfx.
If the problem appears only with importat gfx (#..) we should do a test with set them self in the xml, without importing.

If i remember right, we have had in the past some problems with mp by using real colour black , to solve those problems, we have had to do the black colour some codepoints different. BUt don´t know if the problem is still there.

Harley

 

[Swede]

Hi Harley,

I have no other solution right now, but to crop away the empty space from the images. That fixes my problem, but I don't know why.

It doesn't seem to make any difference if # is used or if the name is used directly. I have a feeling that it has to do with the cache.

I attach a bunch of cropped images. Mainly MP-logos and buttons. Not all of them were nessesery to crop for my system, but I took all similar to those that was troublesome for me to be on the safe side. Only empty space is cropped away so there is no difference in how MP looks.

 

[tourettes]

I have no other solution right now, but to crop away the empty space from the images. That fixes my problem, but I don't know why.

Cropping images reduces the memory amount that GPU needs for textures.

 

[Swede]

Cropping images reduces the memory amount that GPU needs for textures.

Yes but how can cropping away 1kb from such a small file do such difference, when a whole page full of thumbs is no problem?

 

[tourettes]

%programdata%\Team MediaPortal\MediaPortal\Cache\Blue3wide

chech the dimensions of all packedgfx files in that folder (with and without the cropping). Remember to clean the folder before checking those files.

 

[Swede]

I understand where you're going and I will do that, but consider this:
In all screens where Videos_logo is used, List view, icons view, large icons, Filmstrip... CPU was 50% (acting like 100% but it's dual core...) mouse was laggy and everything very slow. Then I crop away 1kb from a 24kb png and everything works fine on those screens!!!

I'll be back with the cache results of the before/after 1kb reduction....

 

[Harley]

i don´t think that 1kb less or more of a gfx will cause such problems.

 

[tourettes]

i don´t think that 1kb less or more of a gfx will cause such problems.

Unless that causes packed texture optimization to increase the texture size a lot. If I remember correctly texture sizes are handled in power of two. Hard to explain, but investigating the packed texture file dimensions should give a clue.

 

[Swede]

The old one including videos_logo were 1256kb and the new one with the cropped videos_logo are 1230kb

 

[tourettes]

The old one including videos_logo were 1256kb and the new one with the cropped videos_logo are 1230kb

How about width and height?