Musicmatch wav tag support

[Sunspot42]

OK I have added some MusicMatch, AudioGrabber and BSI InfoEdit Tag Reeding in MediaMonkey Wave Format Tagger, I hope it will make it in next Alpha so that we can test it while it is still in Alpha.

Wow! That's great news Peke! I'm sure users of those other packages will be happy, too.

[Peke]

Try to test it with MM Alpha 3 2.5.1.901 it is possible that it is included in it.

[Sunspot42]

Try to test it with MM Alpha 3 2.5.1.901 it is possible that it is included in it.

Peke -

Sorry it took so long - I'm in the middle of a move.

I'm testing it, and it's sorta working. MM will scan about 400 files out of my library before crapping out with 100% CPU usage. The process just hangs and stays hung. The files it has scanned appear to be correctly tagged, though.

I can't determine why it's hanging. There's nothing at all unusual about the files its hanging on. I looked over their tags in MMJB, and saw nothing that would cause any problems.

Others have reported similar behavior with the existing production release of MM. I tried a deinstall / reinstall, with no luck.

[Peke]

Ok, but it still hangs.
Can you do the folowing:
Move all files when MM locks to 100% CPU one by one to different folder and try to reproduce same thing with that folder you have copy the tracks.
Verify that all remaining (not moved) tracks from source folder are scaned correctly.

This way we will know which file/s couses hungups chose one smaller pack it and send it to MM Support so I can get it and make fix as Soon as possible.
I hope even include it in Alpha 4 (if we are fast).

[rovingcowboy]

Try to test it with MM Alpha 3 2.5.1.901 it is possible that it is included in it.

Peke -

Sorry it took so long - I'm in the middle of a move.

I'm testing it, and it's sorta working. MM will scan about 400 files out of my library before crapping out with 100% CPU usage. The process just hangs and stays hung. The files it has scanned appear to be correctly tagged, though.

I can't determine why it's hanging. There's nothing at all unusual about the files its hanging on. I looked over their tags in MMJB, and saw nothing that would cause any problems.

Others have reported similar behavior with the existing production release of MM. I tried a deinstall / reinstall, with no luck.

check that tweaking program out i said in the other message to you.

but also try setting your page file to a larger limit and make it a fixed limit.

40 gb's of hard drive should be using about 1 gb of pagefile / virt memory.
as it sounds as if your hitting the limit on your page file and it is slowing down or locking up at least that sounds like what you say in this post.

[Sunspot42]

try setting your page file to a larger limit and make it a fixed limit.

My pagefile is fixed at 2GB - I have a gig of RAM. I don't think the problem could be a lack of RAM, unless something is consuming a TON of RAM during the scanning process.

I did remove all of the prefetch info for MM from the Prefetch directory. Most sites on the web no longer recommend flushing the entire Prefetch directory.

I'll also try moving .WAV files out of the directory to be scanned if this doesn't work. Maybe there's a problem file out there.

[Sunspot]

OK, moved the suspect files to another drive, performed a scandisk, terminated any services that might have been accessing that drive . . . and still no dice. Craps out after around 400 - 420 files. This smells like some kind of memory error to me, although I still have plenty of system RAM free and tons of pagefile space. I think maybe a buffer somewhere overloads after 400+ files scanned.

[jiri]

Try to do as Peke suggested, i.e. try to localize the track that causes the freeze (e.g. by removing the tracks that are scanned properly).

Regards,
Jiri

[Peke]

in 99% when this happends last scanned track is visible in Status bar of MM.

[Sunspot42]

in 99% when this happends last scanned track is visible in Status bar of MM.

I was able to identify the directory MM was scanning, and removed it as indicated in my earlier message. No dice. It still craps out after scanning around 400 files, regardless of which files it's scanning.

I'm guessing it's some kind of buffer overflow that isn't being handled properly, based on a message in another thread. Would explain why MM isn't terminating properly - I have to CTRL-ALT-DEL and terminate the process by hand following a crash.

[Peke]

Have you tried to use Mine and Jiris Suggestion to locate exact file that is cousing Error?

It is essencial as I tried to replicate problem with all my Wave Files on HDD ~1000 (some of them regular, some AudioGrabber, MusicMatch,...) and all gone OK without any problems.

[Sunspot42]

Have you tried to use Mine and Jiris Suggestion to locate exact file that is cousing Error?

I don't think it's a particular file. I can point MM to an entirely different directory structure, tell it to scan that structure full of different files, and it still bombs after "X" number of files. I can rescan the same directory and have it bomb out on the same or on a different file. It can bomb on file 27 one time, and skip right past it only to bomb on file 35 the next time.

[jiri]

Btw, does MM 2.4 work correctly on these files?

Jiri

[rovingcowboy]

jiri i have had media monkey hang when scaning files from version 1.0 or so of media monkey.

it has gotten better and the last version you metioned i don't seem to have the trouble anymore.

as weather to the fact you fixed it or i got it out by tweaking my computer i can not answer but it seemed to be a memory error when i did get it.

because like they said around 400 files it locks up.

when i did the alt tab delete thing and brought up the task manager and ended task on media monkey, i waited a minute then ran scandisk then started media monkey again.

and then started scanning the files from the ones it locked up on only to get the same lock up on the same number of files.

i did that several times but always with the same results.
but it is not doing it any more for me since i tweaked my systems.

only thing i can figure is that monkey is holding all the tag info in the open unsaved note pads or acess documents and waiting until it gets all files scanned to write the tags and save.

only when the page file gets filed it stops monkey and the tags are wrote and the document is saved, but stopping monkey makes it lock up.

that is the only thing i can think of that is going on. not that there is a limit because of monkey but that the limit is because of windows only allowing so much infomation to be held before it writes and saves the documents.

one tweak i did was to go in to the works programs such as word, access, and excell and others.

then found their options panels and found out how to set the automatic back up and either turned it off and or made it a couple hours longer then the default one.

if that fixed the lockups in monkey i once again dont know but its worth checking.

[Peke]

Hmmmm... Interesting point.
Dou you have any resource manager that will track how much ram is used when scaning tracks?

We will see it better when Alpha 4 is released as few Mem Leaks is fixed.