MediaMonkey forum

My system:
Windows 7 Pro 64bit, 4GB of ram.
MM4.1351 is installed on the C: drive (an SSD) and the library is on D: drive.

When adding album art to a file by pasting the image, MM4 hangs for about 20-30 seconds. The image can be from a website or a file on the local machine. The system will say non-responsive. The option will then pop under MM4 to select what the image file is (cover, etc). This problem has existed for me on the last few betas, not just the latest 1351.

I have uninstalled, deleted settings files and tried creating a new library with just a few tracks. No plugins or skins installed.

Is anyone else experiencing this hang? The program performs pretty well otherwise.

~Chris

PS- is debug log compatible with Win7 64 bit?

I assume it's this: http://www.mediamonkey.com/forum/viewto ... =6&t=56020

Where are you pasting? Here opening the Album Art tab in the Properties window took maybe 20-30 seconds. Doing the past has MediaMonkey already hung for more than a minute and it's still hung.

The size of my MM db is about 40MB, but I do have about 20GB worth of mp3's.

Yes, pasting in the album art tab is causing the hang although I think it's reproducible when adding art in other ways.

I had to force MediaMonkey close as it never came back. I'd still assume it's the above links issue.

Thanks lowlander for confirming that you and others are having the same issue.

This continues to be an issue in the latest beta, [1355].

I can't reproduce any problem. Does the art file have to be particularly large, or..?

I can't reproduce either, I've just tried with a 1.5MB file and it was quick.

Just copying any old album art image of the net.

I'm not so sure this is related to MediaMonkey anymore (although I didn't have this issue with MM3), because when I first opened MM after updating to 1357 and attempted to paste art into a track it happened instantly. Five minutes later I try again with the same image and I get the long hang. In that time, I can hear the hard disk spinning but no hard drive activity via the disk activity LED, so I don't think it's because the drive went to sleep or anything. The mp3 drive is a fast harddisk, 7200 RPMs and my OS drive is a c300 ssd. Disk performance in general seems fine, eg. copying a file between both drives is very quick.

I will look into this more and report back anything I find.

Edit 1- During the paste hang time, taskmgr reports that MM jumps to 50% of the CPU usage clock up until the context menu pops up, vs only 4-7% when actually playing a track. That is curious. I tried disabling Microsoft Security Protection (my AV) but that did not fix it. I also tried running in various compatibility modes, such as xp sp3 to no avail.

~
Chris

I'm getting this error code when clicking ok after I add or remove art (also submitted via the error reporter). I have no extensions or plugins. I normally never hit the ok when I was testing this function:

Error: Starting a transaction while some query is open. Running queries are:
SELECT IDFilter FROM Playlists WHERE IDPlaylist = 9

SELECT IDFilter FROM Playlists WHERE IDPlaylist = 9

SELECT IDFilter FROM Playlists WHERE IDPlaylist = 9

(M:\Sources\MediaMonkey\MP3Datab\SQLiteDB.pas, line 209).

Already reported: http://www.mediamonkey.com/forum/viewto ... =6&t=56651

I guess I should have titled this thread 'adding album art in any way causes MM4 to become unresponsive for about 20 seconds', as auto-tag from web causes the same type of system hang. If I'm tagging a file I'm playing it doesn't go to the next track, it loops the last 4 seconds.

A debug log is helpful in these cases: http://www.mediamonkey.com/forum/viewto ... ?f=6&t=341

HeistMonkey wrote:I guess I should have titled this thread 'adding album art in any way causes MM4 to become unresponsive for about 20 seconds', as auto-tag from web causes the same type of system hang. If I'm tagging a file I'm playing it doesn't go to the next track, it loops the last 4 seconds.

I can reproduce some issues if you try to tag a track while it's playing (with 9 seconds or so from the end of the track). but that has been around forever. Any track tagging of other tracks produces no issue here.

Lowlander wrote:A debug log is helpful in these cases: http://www.mediamonkey.com/forum/viewto ... ?f=6&t=341

I ran the debugger and basically what happens when I go to tag a track I see "[8052] MP3.ReadHeader " for every single track in my library, which explains the 20 second lag while this happens. This also happens to make my log file like 5MB. Does this provide enough info or do you want the entire log?

If I auto tag a track that is part of a smaller play list, it happens much quicker, as MM4 will scan through just those tracks in the playlist, even though it isn't tagging any of them.

I mentioned in an earlier post that I created a new library as a test and still had this issue so is it some other setting?