View Issue Details

IDProjectCategoryView StatusLast Update
0017692MediaMonkey 5Tagging / organizing (properties / auto-tools)public2021-03-25 15:17
Reporterpeke Assigned To 
Status newResolutionopen 
Target Version5.0.1 
Summary0017692: Tagging read only files lead to loosing changes and slowdowns
Description1. Select number of tracks whose permissions are read and execute only (image attached). It is easier to setup whole folder -> Add Album art to tracks and initiate tagging

2. Tagging 100 of such tracks can take up to 4 minutes on local drive and 10 minutes on Network path. (example can be seen in video for bug 0017691)

3. There is no information that Tags are not saved (especially AA) and MM5 shows in properties that it is saved to tag, but after MM5 reload album art is missing and in case tracks are not in library all changes are lost.
TagsNo tags attached.
Fixed in build



2021-03-24 19:17


bug17692.png (21,522 bytes)   
bug17692.png (21,522 bytes)   


2021-03-24 20:46

developer   ~0062594

MM4 behaves differently, but you can trigger same thing with these steps:
1. Select number of tracks whose permissions are read and execute only (image attached). It is easier to setup whole folder.
2. Add Another album art (will be added to the end)
3. Press OK to Tag all files
4. No tagging info shown (track properties show new AA was not added)
5. Repeat steps 1-2, but move Newly added track to be first in list
6. Clicking OK to Tag files will trigger same action as in MM5 of long tagging of files

This is long standing functionality and most likely will happen for users that access files on NAS and moved HDDs from one PC to another where permissions will be changes (Unknown user permission) or in cases where users use external HDDs on multiple machines, but scan them into library (teher was few cases in the past).

My suggestion it needs to be fixed but not for 5.0 Pushed to 5.0.1


2021-03-25 15:17

developer   ~0062610

Editing tags works ok for read-only files (files with read-only attribute set) - in this case it displays info, that file is read only and value is set only to DB.
The problem is related to the situation, where writing to folder and files is forbidden by user access rights, where read-only attribute is not set for files.