[MAJOR] - Incorrect Artist/Album Artist Classifications

[nohitter151]

Please, somebody, this really sucks.

May I suggest someone with this particular problem send their MediaMonkey database to the developers or contact MM support: http://www.mediamonkey.com/support/inde ... &_a=submit

[Moogs]

Okay, I sent in my .db file, so I hope they're able to figure something out!

[jiri]

I studied the problem quite thoroughly and my conclusion is, that it seems to be caused by a script, that it shouldn't be caused by the core code in MM.

In more technical details: There is only one place in MM sources where ArtistsSongs table is modified and there doesn't seem to be any possibility how would it cause such a kind of corruption. Also, the code there always deletes all ArtistsSongs records related to a track and creates them again, i.e. 'ID' field there should be consecutive for a track, while in the samples I saw, it wasn't (e.g. numbers like 53 followed by 25159 - 'ID' values for the one track).

To me, it looks like some script adds incorrect records to the table, can you think of some scripts you occasionally use?

Jiri

[jplank]

I've been having the same issue with my copy of Media Monkey Gold. I also use Windows 7. The only plugins/extensions that I use are:

Case Checker
Auto Album DJ
Auto Increment Track #'s
Batch Art Finder
Genre Finder
Last.Fm Scrobbler
Musicbrainz Tagger

[Bex]

I haven't looked into the issue myself but to my knowledge there are no scripts which alter the ArtistsSongs table. There are a few which updates the Artists table (e.g. Case Checker) but I don't see how that can give the described behaviour.

The OP says that it happens on initial scans, which pretty much excludes a script to be the cause. To me it seems that there are some incompatibilities between some new components in Windows 7 Pro and MM's internal code that handles this. But what do I know!

[jiri]

In case someone is able to reproduce the problem (e.g. on the initial scan), it might be useful to see the debug log of the process.

Jiri

[Moogs]

In case someone is able to reproduce the problem (e.g. on the initial scan), it might be useful to see the debug log of the process.

Jiri

It just happened to me, how do I grab the debug log? I've been emailing with the develops for a while now, so I hope they're onto something.

[Ludek]

- Download the latest debug build from here: http://www.mediamonkey.com/sw/MediaMonkey_Debug.exe and install it.
- Download the DbgView application from: http://www.microsoft.com/technet/sysint ... gview.mspx
- Execute DbgView.
- Run MediaMonkey debug build and you will see the log being generated to the DbgView app window.
- Repro the problem
- Save the content in DbgView app to a file and send us the log

Thank you for helping to sort this issue.

[Dussault]

Well, I've found a solution. Since the problem did not exist when I copied part of my library to another hard drive, I had tried re-tagging the information for some artists and it seemed to have cleared up the problem. I asked in this thread for a way to do this with all my music and a poster promptly gave a solution that works. Here its:

Select all your music, right+click, properties and then find a tag that you don't care for, such as "Composer" and just write anything in it, like "x". Then press enter and it will tag all your music with "x" as the composer, as well as re-applying all the other tags with the same information. Simply re-applying the same information seems to correct the issue, so this serves as an effective solution (I did this on a small scale and it worked and am currently doing it with all my library).

This thread should still be pursued, though, so as to understand what caused the files to be corrupted, but there's an easy way to fix the problem. I just hope that whatever caused this problem was just a freak accident, so that I don't have to do this again.

[srlake]

Just an update - I've been using iTunes lately as with this issue MM has been un-useable.

However, I tried the following and am still having the same issue:
1) Clean HD, New Windows 7 x64 install.
2) All Windows Updates
3) New MM 3.2.0.1294 install
4) Added half my library to MM

Same problem - database is all messed up. No scripts or extensions. Arrg.

Edit: I had sent in my MM.db to the MM team back in January, but never heard anything back.

[Ludek]

Just an update - I've been using iTunes lately as with this issue MM has been un-useable.

However, I tried the following and am still having the same issue:
1) Clean HD, New Windows 7 x64 install.
2) All Windows Updates
3) New MM 3.2.0.1294 install
4) Added half my library to MM

Same problem - database is all messed up. No scripts or extensions. Arrg.

Edit: I had sent in my MM.db to the MM team back in January, but never heard anything back.

Srlake, we analyzed your DB and conclusion is several posts above (from Jiri), we haven't found a problem in MM code and we haven't been able to reproduce the issue so far. We think that it must be a script issue, but if you think it is not a script, but a problem in MM or SQLite then try to generate debug log (see posts above) and it might show us something. Do you say that your DB is messed up immediatelly after initial scan? If yes, try to repro by re-scanning the DB and send us debug log from the scanning process. Thx.

[jplank]

I've been playing around with Media Monkey and it seems that the I was running Media Monkey as an administrator. As soon as I turned that off and ran it as a regular user (after I deleted and rebuilt my database), I didn't have anymore problems.