View Issue Details

IDProjectCategoryView StatusLast Update
0017693MMW 5Tagging / organizing (properties / auto-tools)public2026-09-15 07:08
Reporterrusty Assigned To 
PriorityimmediateSeverityfeatureReproducibilityalways
Status resolvedResolutionreopened 
Product Version5.0.1 
Target Version2027Fixed in Version2027 
Summary0017693: Mass edits: improved handling of situations in which metadata within a field doesn't match
DescriptionWhen performing a mass-edits and each track has different values for a given field, it would be better if:
1) The user was notified that attributes don't match by highlighting the fields in some manner. This could be achieved in the same manner as in the auto-tag dialog. There are 3 cases that would need to be handled:
a) the field is empty for some of the tracks
b) the attributes are identical except for case
c) there are conflicting attributes (Currently there's an implicit notification by virtue of an empty field)

The solution in all 3 cases, would be to Display the most common attribute for the field other than "" (in Orange to signify that a change will result) followed by an orange exclamation point (signifying the conflict).

2) The user was able to preferentially choose from among the values that have been entered. So when clicking a combio-box, rather than displaying the full alphabetic list, MM should display the attributes associated with the field (from most to least common), followed by a separator, and then the rest of the list.
Additional InformationRaised at https://www.mediamonkey.com/forum/viewtopic.php?f=30&t=98686
Case discrepancy issue raised at 0017691 issue 1
TagsNo tags attached.
Fixed in build3522

Relationships

parent of 0022317 resolvedrusty CUE tracks: Editing Properties of All CUE tracks incorrectly suggest changes (regression) 
related to 0021615 closedLudek BPM not showing in Properties when 2 files selected 
related to 0022185 closedmichal Opening Properties on multiple files causes high memory usage/slow to use 

Activities

michal

2026-05-16 16:29

developer   ~0081157

Fixed in build 3402.

lowlander

2026-06-30 17:40

developer   ~0081545

This seems to work on 3514.

1) I think the drop down indicator should be orange as well (eg. see Title, it's grey like the standard drop-down indicator like Album).

2) The Exclamation mark should show a tooltip indicating that multiple values are associated with the selected files for this field.

3) Genre, Track# and Disc# don't have exclamation mark on multiple values.

4) It would be nice to have values used in selected files in orange too in the drop-down, to better clarify to user that these are values found in the selected files (see Genre screenshot).
image.png (50,035 bytes)   
image.png (50,035 bytes)   
image-2.png (10,516 bytes)   
image-2.png (10,516 bytes)   

michal

2026-07-01 09:12

developer   ~0081554

Fixed in build 3515.

lowlander

2026-07-30 18:09

developer   ~0081756

Last edited: 2026-07-30 18:15

Verified all 4 items on 3516.

5. The new Subtitle and Language fields don't show multi-value.

6. Rating has no multi-value indication.
a. If there is a file with Rating value and and a file without, the Rating of the file with value is shown, no indication the other file is lacking Rating
b. If 2 files with different Rating are selected, no Rating is shown, no indication of a multi-value

7. There is no indication that there are multiple values in Comment, it's shown blank.

8. No indication of multi-value for Start time, Stop time, Play counter, Skip counter, Track volume and Album volume. Note that users may select 2 copies of the same file so there is a use to being able to see multi-value.

michal

2026-08-07 06:30

developer   ~0081803

Fixed in build 3517. Because it would be risky and more computationally and memory demanding, the comment field displays the first value, not the most common one. It also does not display a dropdown with a selection of all possible values, as comments can be very long.

lowlander

2026-08-17 21:04

developer   ~0081894

Verified on 3517

peke

2026-09-13 23:23

developer   ~0082152

image-3.png (55,406 bytes)   
image-3.png (55,406 bytes)   

rusty

2026-09-14 21:04

administrator   ~0082165

To summarize, the problem is related to the fact that MM now highlights fields that have differing values using color and an '!', and preselects values that are most common resulting in:
- some users interpret this as a warning/recommendation by MM to fix things using the suggested values (rather than a warning that the values across multiple files are inconsistent and should only be changed if the inconsistency needs to be corrected). Consequently they check the field with the suggestion, causing metadata to be lost.
- some users interpret this as a warning about the suggested metadata, and solve it by deleting it. In so doing, the red text and '!' warning go away and the field to become checked, and they might think they've solved the problem even though results in the metadata being deleted from all tracks.

This probably isn't a severe issue since MM still warns the user when a large number of files are to be edited, however, it should still be improved, since in the above cases users realize that they're editing many tracks--they just make incorrect edits if they're not thinking about what they're doing because the UI steers them towards those edits.

This can be solved with a few tweaks discussed offline:
1. When a given field has multiple different values, continue to show the '!', but without displaying the 'recommended values'. Instead force the user (as in the past) to either choose from one of the recommended values in the combobox (instead of pre-filling the field) or manually edit the field
 - as always, automatically check the checkbox after the user has manually edited/deleted the field or only after selecting a value from the combobox
The tweaks are minor, but force the user to actually go through editing steps as in the past (while still providing feedback regarding inconsistent field values).
  
2. Tweak the tooltip: Selected files contain multiple values for this field
--> Selected files contain different values for this field

michal

2026-09-15 07:08

developer   ~0082171

Fixed in build 3522. Now we not do not prefill most frequent value, as before changes in this issue.