i actually don't have the issues with playing concurrently (maybe because I have 2gigs of ram?). The CPU issues seem identical no matter what priority is being used, and happen even when MM is doing -nothing- else.

Hi mistresso,

I can confirm your problem: When analyzing the volume of a list of tracks, the player first starts to stutter and then finally stops playing the song it is playing.

Setting the analyzer priority to 'idle' does help a bit, but doesn't stop the player from stuttering at all.

Not only that, but after the volume leveler has analyzed a certain amount of tracks, I get an error message that the actual track cannot be decoded...

To crown it all, the player also stutters or stops playing when I am ripping a CD to mp3 in the background.

Everything was fine on the same machine when I was using MM2

Hope the development crew will find a solution soon.

Cheers,

Dread

Has anyone else confirmed/experienced this, or am I alone moaning in the dark?

I can live with the high CPU utilization if I do nothing else important with the machine, but the inability of MM to properly shut-down & close once it gets "stuck" on 99% is worrying.

I've shut off the background levelling and now just do it manually on batches of files, but the memory issues are still there; it's just less likely to hit the 99% mark and die.

It also gets stuck anytime a protected file is hit (I have a few, maybe 1% of collection). Instead of realizing the file is protected (mp4 for example), MM will hang indefinitely (the background thread, that is; the app still works). Again, exiting/shutting down MM normally does not work then; I have to kill the process directly via the task manager.

Long-time user here, have experienced -very- few bugs.

But right now, volume level analyzing functionality seems a bit "funky" with my large database (~80k mp3 files, most averaging 128-192 bit).

What happens is if I turn on the background volume level analyzation, the CPU usage immediately goes to 90-100% and stays there. it's almost evenly divided between Decoder.exe and MediaMonkey.exe, but after a while, MediaMonkey.exe takes over and uses up all the CPU utilization. At that point the level process more or less grinds to a halt, as well.

Changing the priority of the task by right-clicking on the status bar within MediaMonkey has no affect- it's always near 100% CPU. As you can imagine, this has an adverse affect on my other applications.

Furthermore, if I exit MediaMonkey while this process is going, I either get an "application error" debug box, OR MediaMonkey.exe stays running as a process (still at 100%) - I have to manually kill it via the task manager. Every time I try to re-start MM without doing this, I get another clone created that won't fully boot up.

I've also confirmed this behavior on 2 different machines, one an Athlon and one a spankin' new Intel VERY FAST dual-core. Both are 64 bit processors but running in WindowsXP 32 mode. Both have 2 gigs of ram and are virus/malware free.

Let me know if there is anything I can do to help reproduce the problem - and I am curious if anyone else out there sees the same behavior or not (it may be weirdness caused by the size of my music collection).

BTW - I am using MediaMonkey 3.0.3.1140, but problem also exists on current non-beta version.