Updating Tags
Wiki Home > MediaMonkey 5 Help > Editing Files > Updating Tags
Introduction
By default tags are saved both the MediaMonkey Library and the media files tags when editing media files in MediaMonkey the tags are saved both the MediaMonkey Library and the media files tags. However there are times when the MediaMonkey Library tag values can mis-match the tag values in the media files.
DB / Tag Mismatches
In some circumstances, the file properties that appear in the MediaMonkey Library will not match those that are in in the files tags. Such files are displayed in the Collections > Files to Edit > DB / Tag Mismatches node with the non-matching tag highlighted.
Occasionally some files will not have any tags highlighted; this is usually the case when tags that do not appear in the Filelisting (e.g. comments) are non-matching. Files can appear in this node if:
- When adding files to the Library and missing tags are inferred from filenames. Inferred tags are not automatically saved to the files tags are not saved to the files.
- When files are read-only or MediaMonkey lacks rights to update the media files (in this scenario you first need to give MediaMonkey the rights to update the media files).
- One version of a tag matches the library (e.g. ID3v2) but another version doesn't (e.g. ID3v1). Note that for MP3 files, the list shown will depend on the configuration under Tools > Options > Library > Tags & Playlists from the Main Menu:
- If MediaMonkey is set to write ID3v1 Tags: Only files whose ID3v1 properties don't match the Library are shown.
Note: ID3v1 has a number of constraints including: Track#s< 256, field lengths are often limited to 28 characters, and UNICODE is not supported. Differences between the tag and the library that are caused by these constraints are ignored. - If MediaMonkey is set to write ID3v2 Tags: Only files whose ID3v2 properties don't match the Library are shown.
- If MediaMonkey is set to write ID3v1 and v2 Tags: Files whose ID3v2 or ID3v1 properties don't match the Library are shown.
Note: ID3v1 has a number of constraints including: Track#s< 256, field lengths are often limited to 28 characters, and unicode is not supported. Differences between the tag and the library that are caused by these constraints are ignored.
- If MediaMonkey is set to write ID3v1 Tags: Only files whose ID3v1 properties don't match the Library are shown.
- A change is made to a file property, but a malformed tag prevents the tag from being saved correctly.
- The option to Update tags when editing properties is disabled under Tools > Options > Library > Tags & Playlists from the Main Menu.
Note: With ID3 this functionality is active only for the Title, Artist, Album, Date and Comment fields. For other tagging standards this is Artist, Album Artist, Album, Title, Genre, Date, Origal Date, Track#, Episode#, Disc#, Season#, BPM, Rating, Comment, Lyrics, Author, Publisher, Lyricist, Conductor, Grouping, Involved People, Original Artist, Original Title, Parental Rating, Producer, Track Volume and Album Volume.
Update Tags
When MediaMonkey Library values don't match the tag values in the files you can manually update the file tags. To do so:
- Select the files listed in the Collections > Files to Edit > DB / Tag Mismatches node that you want to save the MediaMonkey Library values to
- Use Tools > Edit Tags > Update Tags. The MediaMonkey Library values will be saved to the files.
- For some MP3 Tracks, attempts to synchronize tags may fail due to malformed tags. In these cases, use the Clean Tags function to remove the tags and then use Update Tags afterwards.
Note, this saves the MediaMonkey Library values to the files tags. If instead you want to update the MediaMonkey Library values with the files tags you'll need to scan the files.
Related
| English |
Additional Help: Knowledge Base | Forum | MediaMonkey Support | MediaMonkey for Android Help | MediaMonkey 5 Help | MediaMonkey 4 Help
