I've carry out some rebuilding tests on my 7700 mp3s:
- Empty database = 184K
- First building -> database size = 36180K
- Rebuilding on the same mp3s with the option "Don't restore old album covers" UNchecked -> database size = 71992K!
- Rebuilding again with the option "Don't restore old album covers" checked -> always 71992K!!

So if you don't check the option "Don't restore old album covers" the database size abnormally grow up because ID3 images are added again and again each time you rebuild, until excessively slow down eJukebox operation! And if you check that option, ID3 images are not duplicated any more but you lose the looked up images...
Look at another post concerning this problem HERE.

I suggest a solution to prevent the database grow up too much because of ID3 images:

I think during the rebuilding when a ID3 image is loaded from a mp3 , the previous one corresponding to the same mp3 file MUST be first erased from the database.

What you think?

This is already done. All previous ID3 images are erased from the database and are reinserted when rebuilding the database.

Yes, but I need to chose the option "Don't restore old album covers" in order that works correctly, and then I will lose the looked up images, no? Too bad!

So until now I never check off the option "Don't restore old album covers" but I have noticed my database grows up abnormaly (because of a wrong ID3 images updating, I suppose): the size is almost double JUST AFTER THE FIRST REBUILDING, even if I have added NONE new mp3 or any ID3 image edited externally! And that, you can't tell me that is normal !?

Thanks.

Actually it erases all the old ID3 image images from eJukebox and reinserts them on rebuilding no matter if you check "Don't restore old album covers" or not. "Don't restore old album covers" ONLY effects eJukebox lookedup images. ID3 images are Always treated the same: deleted and reinserted (just in case the image has been changed). The "Don't restore old album covers" option should really be removed as it no longer really serves any good purpose.

The reason the database is huge after rebuilding is because the database itself is not compressed down until you exit eJukebox. If you shutdown and restart eJukebox and you should see the size of the ejuke.asn file drop.

Drat!
So the explanation is in the compression which occur only when I exit eJukebox... Now I understand my appreciation error!
Maybe I am too curious...
Sorry to have been annoying with that.

Otherwise I think the option "Don't restore old album covers" could be used to delete the database file and restart with a clean one, providing a kind of "soft reset".

The "new database" function is currently missing in ejukebox. That could be useful in case of problems with the database. That may always occur after many manipulations one an old database. Look junk's post HERE.


Thank you for your explanation.