MediaMonkey forum

MM has become totally unstable.
Yes, it might run for a rip or 2, but then it does something weird.
I tried to document the weirdities ... here are just a few:

I enter a different <Year> ... like 1997 - it doesn't take.
It won't find Freedb data... it just hangs - I have to restart MM.
It "stutters" when it starts playing a new CD.
It doesn't rip all the tracks. Yes, I have them all checked.

There is more. I just gave up logging them.
In almost all cases, if I restart MM, it works ... for a while.

Thanks.

Hi,
If it is consistent issue and you can replicate it always. It would be great if you can please open support ticket and supply us a debug log as described at https://www.mediamonkey.com/forum/viewt ... p?f=7&t=69 ?

Then we can analyze and see what exactly is going on.

"stutter" on begin of playback usually indicate on a Device problem rather than media problem, due teh fact that Laser can't get steady calibration on the disk in order to read it.

Nothing is consistent in causing the problems, but many of the results are consistent.
The most common is ... it just stops ripping.

Stuttering... There is nothing wrong with my CD/DVD reader.
It's one big stutter, not a bunch of little ones.
The song will play for 3-4 seconds... then restart. Then it will play 5-6 seconds and jump back 3 seconds.

It never fails with any other program.

Hi,
Hmm, as I said this behavior is very uncommon and by your description it is first time something like this is reported for Audio CDs. Symptoms for behavior you describe are different and Debug log would be crucial in order to see what commands MMW see and sends to CD-Rom.

In reading the bug reports... it seems that a lot of people are experiencing instability.
I stopped treating MM as a threaded program. In other words, I only do one thing at a time.
Previously, I would rip one CD and edit tags for other CDs at the same time.
Suddenly, most (not all) of my problems disappeared.
This points to bad threading practices or passing variables between classes in a sloppy fashion.
Sorry, I don't mean to cast aspersions on your program... I like it. But, it's driving me crazy.
This new method of operation will cost me a lot of time.

And now, the "I'm not a robot" has made me verify 4 times.
I've been a gold member for years. I'm vested in MM... and I'm worried.

Robot test is for non-registered posting.

Have you maintained (complete optimization) the database recently?

No - How do I "completely optimize" the database?
... and why would an unoptimized DB affect code execution?
(other than slowing it down)

The biggest bottle neck is the database as most operations involve it. So when 1 operation locks the database and other operations are added things can become unresponsive. Optimizing (File > Maintain Library) can improve the speed of the database and thus MediaMonkey.