What is going on behind the scenes when ejukebox shuts down? It is stated that it's compacting the database, however my database (ejuke.asn) is at the same size all the time (ej running vs not running). Are you sure this pause is nececcary? I've killed ejukebox several times from the taskbar, and don't have any troubles with my database. At least none I am aware of

I think it saves in the id3 tags the play count of each mp3 you have played, and the new ratings you've maybe added! It certainly saves all that in the database too... And I forgot the "last played" date for each song.
Unless all that is already saved while eJ is playing songs? So you are right, what eJukebox do during the shut down? An useless compression?!

If so I hope it is removed. This pause and the pause after albumlist loading is quite frustrating with large collections. Because it takes ages to do large operations on the database (mine is around 150 mb and growing)

I agree, the pause just after albumlist loading is damned annoying. I don't know what it occurs exactly during this long time, but what I'm sure is that eJukebox is completly frozen!! So this time seems even more long...

Here is the timing in my case, with 2783 albums:

0min 0s -> I start to rebuild the albumlist
... During this time I can use eJukebox normally, even the albumlist itself while it is loading! Perfect, nothing to change here!

0min 45s -> The albumlist is completed on the screen. But unfortunately that is not finished, the real problem starts here:
... During 40s eJukebox remains FROZEN, entirely!

1min 25s -> eJukebox unfreeze, finally!


Audiosoft,

What is eJukebox doing during these 40 long seconds ??
Couldn't you avoid this eJukebox freezing time?

If not, maybe during the albumlist building you could split eJukebox in 2 different process, allowing more CPU time to the albumlist building process while keeping the eJukebox main process (end the user) alive!

So during the albumlist "freezing time" the CPU usage would be:
- Process #1, eJukebox main program: 25% max (eJukebox is not frozen)
- Process #2, Albumlist "critical" building: 50% max (The albumlist building time doesn't grow longer more than currently...)
- Free CPU time: 25% min (The PC is not frozen)

And during the normal use of eJukebox:
- eJukebox: 50% max
- Free CPU time: 50% min

I hope this make sense...

Thanks.

Well, the reply to my question is here: http://www.audiosoft.net/forums/viewthread.php?tid=737#pid5130

After loading, eJukebox save the albumlist on the hard drive...

So Audiosoft, you could create a separated process to save the albumlist on the hard drive, using the CPU time limitations I proposed on my previous post.

Plus, if you add the "rocket" solution I suggest here:
http://www.audiosoft.net/forums/viewthread.php?tid=737#pid5130