View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0018274||MediaMonkey 5||Tagging / organizing (properties / auto-tools)||public||2021-09-10 23:16||2021-09-17 16:19|
|Target Version||5.0.2||Fixed in Version||5.0.2|
|Summary||0018274: Cancelling Tagging can introduce discrepancies|
|Description||When tagging a large amount of files MediaMonkey will first do the database updates for the files, then do the actual tagging of the files.|
When MediaMonkey is doing the database updates the user can cancel. This will cancel the database updates, however MediaMonkey then continues tagging the files requiring a second cancelling of tagging (in MediaMonkey 4 it would be one cancellation that was needed).
|Steps To Reproduce||1 Tag 1000 files|
2 Cancel the update database stage from the progress bar
--> Expected tagging to stop (MediaMonkey 4 behavior)
--> MediaMonkey starts tagging files (all originally updated files).
3 Cancel file tagging
The problem is that the database will have received different updates than the files in this scenario introducing data discrepancies between database and file tags.
Maybe where MediaMonkey updates database for 1 file, then tags the file, then updates database for next file and then tags the file would be preferred. Any cancellation would then be a single cancel and would happen before the next file is updated in the database (so database and file data are in sync).
|Tags||No tags attached.|
|Fixed in build||2503|
Fixed in 2503.
i.e. the tagging thread tags only the files that have been already updated to DB (and were not canceled) -- i.e. only the not canceled DB updates are queued for tagging (though the tagging thread can still be canceled).
Note that in MM4 canceling the DB update thread also did not cancel the tag updating thread.
||Verified on 2503.|