View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0019069 | MMW 5 | Tagging / organizing (properties / auto-tools) | public | 2022-05-10 07:59 | 2022-11-04 20:38 |
| Reporter | michal | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | unable to reproduce |
| Status | closed | Resolution | reopened | ||
| Product Version | 5.0.3 | ||||
| Target Version | 5.1 | Fixed in Version | 5.0.4 | ||
| Summary | 0019069: Continuous monitoring of folders sometimes does not work right away | ||||
| Description | User 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 Information | Ticket 4095, 4830 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2666 | ||||
|
|
Tried to reproduce, but cannot ... artwork correctly updated (in preview window and grid view). |
|
|
I also cannot reproduce already. |
|
|
Verified unable to reproduce 2666 Closing. |
|
|
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)? |
|
|
Yes, I tested nested monitoring. I do not see duplicate scanning in logs. for me only one folder is scanned and child is skipped. |
|
|
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. |
|
|
Verified 2680 Unable to replicate and both tickets are closed. |
