View Issue Details

IDProjectCategoryView StatusLast Update
0019069MMW 5Tagging / organizing (properties / auto-tools)public2022-11-04 20:38
Reportermichal Assigned To 
PriorityurgentSeveritymajorReproducibilityunable to reproduce
Status closedResolutionreopened 
Product Version5.0.3 
Target Version5.1Fixed in Version5.0.4 
Summary0019069: Continuous monitoring of folders sometimes does not work right away
DescriptionUser experiences problem, that after editing tags of FLAC/MP3 file in 3rd party tagging SW (TagScanner), the newly added artwork is not seen in MM5 till second tagging of the same file or MM5 restart. It seems to be caused by multiple modify event handlers called for the same file in our auto-scan monitor in only about 500ms. This can happen e.g. when monitoring nested folders (like H:\MP3, H:\MP3\classic and H:\MP3\classic\new -> change in "new" folder generates at least 3 modify events), but for the user, it happens even for only one monitored folder, probably related so something in his system.
We should wait a little bit in auto-scan monitor and handle only last modify/add/delete event for the same file during circa 1s.
Debug logs in the ticket.
Additional InformationTicket 4095, 4830
TagsNo tags attached.
Fixed in build2666

Activities

petr

2022-09-28 14:20

developer   ~0069539

Tried to reproduce, but cannot ... artwork correctly updated (in preview window and grid view).

michal

2022-09-28 15:19

developer   ~0069540

Last edited: 2022-09-28 15:19

I also cannot reproduce already.

peke

2022-09-28 20:57

developer   ~0069558

Verified unable to reproduce 2666

Closing.

rusty

2022-09-28 21:33

administrator   ~0069559

According to ticket 4095, this issue occurs when there are nested scans (i.e. scanning is configured for both a parent and child folder). Peke can you confirm that this is the scenario you tested?

If not (i.e. if the issue does occur with nested folders), shouldn't MM have logic to automatically prevent duplicate scanning of a child (or at least prevent duplicate configuration of a child)?

peke

2022-09-28 22:23

developer   ~0069560

Last edited: 2022-09-29 07:43

Yes, I tested nested monitoring.

I do not see duplicate scanning in logs. for me only one folder is scanned and child is skipped.

michal

2022-09-29 06:43

developer   ~0069563

No, I was not able to reproduce the problem. And the problem with nested folders (multiple modify events) was already fixed. So resolving and we will see, whether some user will reproduce it again, I cannot too.

peke

2022-11-04 20:38

developer   ~0070157

Verified 2680

Unable to replicate and both tickets are closed.