View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0021916 | MMW 5 | Tagging framework / input plugins | public | 2026-01-07 09:48 | 2026-02-12 16:13 |
| Reporter | michal | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | feedback | Resolution | reopened | ||
| Product Version | 2024.2 | ||||
| Target Version | 2024.2.1 | Fixed in Version | 2024.2.1 | ||
| Summary | 0021916: Some files are reported as updated on every rescan - regression | ||||
| Description | Some files, like AAC or MPC, are reported as updated on every rescan. It seems to be regression caused by fix of 0021709. | ||||
| Additional Information | https://www.mediamonkey.com/forum/viewtopic.php?p=531243#p531243 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 3206 | ||||
|
|
Fixed in build 3201. It was combination of two regressions, one for AAC and MPC files, one could affect also other files. |
|
|
Verified 3201 |
|
|
Works for me on 3201 with MP4/FLAC files. |
|
|
Fixed in build 3204. Now rescans should be far faster in case of many external images are used. |
|
|
On 3204 newly ripped files are updated on the next scan. |
|
|
"Analyze files for duplicates" somehow causes this and it is not regression. Decreased priority, does not seem to be so serious. |
|
|
Fixed in build 3206. It was there many years, caused by the fact, that signatures needed for "Analyze files for duplicates" function were not added after ripping, but only during the subsequent rescan. Now they are added, if needed, just before saving ripped track do DB. |
|
|
It's still updating files just ripped on scan. Added new logs, Analyze for Duplicates doesn't seem to be the issue as with it disabled the same happens. |
|
|
I already cannot reproduce, do you reproduce it always? Is it related only to NAS or is it the same also locally? It looks like your files were changed after saving last modified time to the database (after ripping and tagging), but I cannot reproduce and find out how this could happen. |
|
|
Yes, this seems to always happen for ripped files. New log from 3209 for Snoop Album. Local vs NAS makes no difference. |
|
|
To sum up situation. It does not happen for local files, it was probably test error. It seems some NAS setting/setup is causing change (tag?) of just saved file. First rescan then sees changed file and updates it in DB. I think we can do nothing with this, as from MM side it is correct behavior. But leaving on lowlander and his testing. |
|
|
Test note/clarification: - the issue of some files being reported as updated on every rescan was a regression and was fixed at 0021954 - the issue of files being reported as updated after a rip, occurs once (after each rip) and is apparently caused by an issue specific to certain NAS software/settings (for LL to verify) |
