Errors in the Library Area

[JohanZ]

Hi Peter,
During scrolling in the Library Area i've got a frozen screen in the The Library Area with a Warning Message "Onvoldoende geheugen. -0" (See Scrolling1). After accepting this error, the Warning came back several times. Scrolling again gives the same warnings. After accepting the last warning it shows the other images in the library area. The next scrolling gives the messages scrolling1, scrolling 2 and 3! After an restart it works again. I have seen this warnings now for the second time in two days.

I have the impression that scrolling in the Library is much slower then the version before.

The Library Area now is provided with a black background.

   
I prefer the white background. Please make it selectable.

Regards

[SeVeReD]

For my little laptop the scrolng became slower.  I dunno which background I like... the black has grown on me... but it does seem slower.  Just thought that would get better with a faster machine?  No errors as of yet.

[PeterSt]

Johan,

Do you now have more coverart showing up opposed to before ?
or
Do you have the feeling that many are different now ?

and

Most of your coverart for the cover will be named folder.jpg. But for the remainder, what name would you use for the one and only cover ?

[SeVeReD]

I always thought...
cover.jpg
would be a good one
to name


the cover
jpg

[JohanZ]

Do you now have more coverart showing up opposed to before?

I do not understand your question. In this version there are nine new coverarts/cd's. Directly after copying to the Galary the errors where generated during scrolling.

Do you have the feeling that many are different now?

Beside the new background and red lining in the image i don't see a differences with the previous version 09v-1

what name would you use for the one and only cover ?

I only rename the name to 'folder'. I'll keep the extension as it is.

[PeterSt]

What I indirectly meant is :

When you have named all your coverart as folder.jpg and you have put that in the directory as intended (by me, which is or in the directory where the music data is, or for a multi volume album in the directory that holds the album itself (with underneath the volumes) ...

a. you would see as much coverart as before (XX didn't dig up more);
b. it shouldn't produce those errors since they can only come from files which are not called folder.jpg while a folder.jpg is not in the directory(s) as mentioned;
c. yes it will be a bit slower in any case.

Ad c.
Which is most profound with a single core processor I now realize.
Btw this is related to the better rendering of the pictures (they are more beautiful) for which I can make a parameter to shut it off.

Ad a.
When you have the folder.jpg somewhere else (e.g. in a directory named "folder") or you often don't have a folder.jpg but e.g. a cover.jpg, it will be more slow because of that which may be *much* slower when you have a couple of other jpg's (like inlet1.jpg, back.jpg etc.) because they all have to be examined. Also, when these additional files are large (which could be the case with a high resolution scan for the booklet (to keep it readable)) it will be significantly more slow. Keep in mind though that this is caused then by no folder.jpg being present at the appointed place(s) (see above).

The errors, of course, should be solved. So I will look into that anyway.

[JohanZ]

......as folder.jpg and you have put that in the directory as intended.....

Always in the directory where the music data is. ......Sometimes i'll put more coverarts in that directory. Future backup's i'll put in de artis directory. So there are more coverarts in artist - and album directories.

errors since they can only come from files which are not called folder.jpg while a folder.jpg is not in the directory

Sometimes i'll keep the origional names. All in the same album directory or apart in the artist directory.

Background colour selectable?

[PeterSt]

Background colour selectable?

Nah, not.

Yet.

[SeVeReD]

I have all .jpg in the same folder area as the wav & cue & txt files. 

[PeterSt]

A small update :

This problem is solved, but currently I can't upload a new version because of (rather major) other difficulties which must be solved first (I started something which is half-way now).

Btw, the problem occurs only when the Library Area is loaded with data from Galeries.
It is unrelated to being out of memory, and is merely a flaw of the OS just saying it is, while it is really about loading a picture from a file which doesn't hold a picture at all (and this by itself is a flaw of me ).