Problem with mp3Tag + MediaMonkey

Support
1

Hi everybody, I'm going mad while trying to use MP3Tag in combination with Media Monkey.

I have been updating my music database and the tags. I would like to use ID3v1 + ID3v2.

My problem: I do not see the changes I made with MP3Tag in Media Monkey, i.e. for the ablum artist.

My settings are as follows:

MP3Tag:
READ: ID3v1 + ID3v2 checked, APE not checked
WRITE: ID3v1 + ID3v2 checked, APE not checked, plus "ID3v2.3 UTF16" checked
DELETE: APE checked

MediaMonkey:
Save song information: ID3v1 + ID3v2-Tags
ID3v2 Code: ASCII + UTF16 if necessary
"Update Tags after changing properties" checked

Does anybody has an idea what's wrong with that?

Thanx for any answer.

Andreas

2

Did you re-read your changed tracks in MM after you made any changes in Mp3tag?
MM only detects changes, if you
a) manually re-read this tracks
or
b) set "folder(s) to monitor" for tracks that you change inside such a directory

3

Mediamonkey normally shows you the content of it's database and not what's inside the tags.
So you habe to rescan your files so that Mediamonky updates it's database.

Have you set the option "Preserve file modification time when saving tags" in Mp3tag?
Disable that and rescan your files in Mediamonkey.

4

Thanks for your help.

My "music"-folder is set to "scan continously" (because it takes some time to have it scanned completely at each startup), and I have manually "added / re-scanned the library". I even startet Media Monkey new - the changes made with MP3Tag are not shown.

It works perfectly the other way round: If I change tags in MM and refresh MP3Tag, the changes are shown in MP3Tag.

5

In my version, it is called: "Modify timestamp when updating tags", and it is not checked...

6

Maybe I should change to ID2v3 completely? Would mean no problem with any of my devices. Should I delete the ID3v1-Tags in that case?

7

That's because MM works with a database (a collection of previously scanned id3 tags). You could even delete all your songs and still see this tags in MM. Don't do it anyway. :yum:

Mp3tag read the tags directly from the tracks every time you load them. So you see every change instantly.

You should update your Mp3tag to the newest version and turn off "Preserve file modification time when saving tags" in Mp3tag. This way Mp3tag changes the last modified date for your changed tracks. This should show MM to re-scan such files.

Preserve file modification time
Preserve file modification time625×555 14.1 KB

Please read this thread in the MM forum too.

Update 26.05.2025 for future readers:
You can find the option "Preserve file modification time when saving tags" in newer Versions of Mp3tag in the section:
File -> Options -> General

8

That's the option in Mediamonkey. I was talking about the option in MP3Tag:
File->Options->Tags
To my opinion it should me unchecked so that other programs know for certain that something in the files has changed.

9

I had a look at your first post again and you are mentioning "Album Artist".
The ID3v2-tag is called ALBUMARTIST in Mp3Tag. It is possible that you mix them in the 2 programs.
Have a look at all your tags in Mp3Tag with the extended tag-view (ALT-6) and tell us what you see. I suspect that you see 2 or more different tag-fields.

10

Okay, I mixed up the preferences of the 2 programmes, that's true.

When I changethe "Album Artist" in MP3Tag, it fills the same field as it does when I fill it in MM; I checked that with the extended Tags in MP3Tag.

On the other Hand, I tried to change the "genre" in MP3Tag, and I could not see the change in MM after

  1. simply refreshing the view
  2. Add/Rescan the library + refreshing the view
  3. restarting MM after No. 2)

I updated MP3Tag to version 3.3, and I use MM Gold version 4.1.29.1910

Here are my settings:
image
image
image

Settings for MM in a separate post due to tretrictions for new users... :wink:

Thank you both so much for your support!

Andreas

11

image
image721×544 107 KB

image
image866×603 111 KB

If you need any more information, please let me know.

12

Please try it again with this changed MediaMonkey settings:

2e82b234644cccc12f155acf8be49926b958265b
2e82b234644cccc12f155acf8be49926b958265b721×544 108 KB

It seems that you don't rescan the tags into MM at all with your current settings.

13

That's it! Now it works perfectly! Thankyou so much!