Threaded Mode | Linear Mode

simoncn · 20-12-2021, 16:10

The messages were produced because the logging level was set to Trace. For normal use, it should be set to Info or Verbose.

edj · 05-01-2022, 14:20

Hi Simon, this is a great set of updates, particularly the Recently Added system.

I have an issue with it though, I suspect unavoidable but would guess that a lot of people experience something similar.

Minimserver for me is on a Synology NAS and the music library it reads from is not the "original" - the main library is saved on my OneDrive and is then downloaded onto the NAS. The issue here is that if I update a track (rating on my desktop for example - so creation date remains unchanged but modified date is updated) the NAS will re-download this file and then MS will see it is a new track upon Rescan. Therefore updated tracks will appear in the Recently Added folders.

I can see why this is probably unfixable but wondered if you have any clever ideas!

simoncn · 05-01-2022, 15:42

If I have understood your setup correctly, the problem you describe should not be happening.

After you enable Recently Added support, the first scan buils the "recently added" list using "last modified" times.

On every subsequent rescan, the "recently added" list is updated only for new files that are added (based on the full path and filename of the file). Modifying the contents or "last modified" time of an existing file does not add the file to the "recently added" list.

This means that downloading a new version of the file will not add the file to the "recently added" list if its full path and filename has not changed.

edj · 05-01-2022, 17:31

I've looked into this a bit further and the behaviour is pretty strange.

If I take an album that I added to the library over a year ago and change the rating of a particular track, when I go to Recently Added only the tracks that come after the edited track are included in the list.

EG there is an album of 15 tracks added one year ago. I make a change to track 11 and rescan. Tracks 12-15 are then shown in the recently added node.

Also I have realised that the Synology in fact preserves the created date, and the modified date is as per original. So there's not an issue here / that's not part of the problem.

RSJ · 05-01-2022, 18:06

(05-01-2022 17:31)edj Wrote: I've looked into this a bit further and the behaviour is pretty strange.

If I take an album that I added to the library over a year ago and change the rating of a particular track, when I go to Recently Added only the tracks that come after the edited track are included in the list.

EG there is an album of 15 tracks added one year ago. I make a change to track 11 and rescan. Tracks 12-15 are then shown in the recently added node.

Also I have realised that the Synology in fact preserves the created date, and the modified date is as per original. So there's not an issue here / that's not part of the problem.

I have observed something similar. If I re-tag an album or add new artwork, that album will be added to my 'Recently Added' list. In my setup, I edit album tags, etc., on my laptop which then synchronises with my QNAP (where Minim resides) using Qsync.

simoncn · 05-01-2022, 18:58

As a test, I tried modifying the Title tag of track 6 out of 10 in one of my albums, then rescanning. As expected, no files were added to the recently added list. This was not doing cross-machine synchronization, just modifying a local file directly.

I suspect cross-machine synchronization is causing the order of scanning files and/or folders to change. This could cause files to be incorrectly recognised as being newly added because the order of files on the disk doesn't match the order of files in the MinimServer cache. In previous versions of MinimServer, this would have caused files to be unnecessarily reread from disk with the only visible effect being a slight increase in scanning time.

I will need to think about what can be done to solve this problem without adding too much overhead to the scan.

Peter@57m · 06-01-2022, 08:33

Simon,

I maintain my library on a QNAP and use a sync utility to copy changed files to my Melco. I do fairly regular changes to tags on the QNAP which causes files to be copied to my Melco but have not seen this issue.
I run MinimServer on the QNAP as well which also does show this issue.

Will run some test to see if a recent MinimServer update has changed this behaviour. Will report back later today.

Peter

simoncn · 06-01-2022, 09:43

How are you changing tags on the QNAP?

Peter@57m · (This post was last modified: 06-01-2022 11:42 by Peter@57m.)

(06-01-2022 09:43)simoncn Wrote: How are you changing tags on the QNAP?

I use MediaMonkey to update tags. I set Modify timestamp option on otherwise the sync program doesn't pick up the change.
I then use FreeFileSync to mirror the QNAP to my Melco.

Included below is screen shots of a change to an ABBA Gold album, one track was changed. The sync program picked up just this one track, along with regenerated playlists, and copied it to the Melco. I rescanned MinimServer on the Melco and ABBA did not show in recently added.
I have also included a file list for the PC and for the Melco showing Date modified, created and accessed. The first file list is the PC, second is the Melco

Let me know if I can provide anything else.

simoncn · 06-01-2022, 12:13

Thanks, Peter! For the files on the PC, are they files on the QNAP that you are accessing from the PC using file sharing or are they files physically located on the PC?

I am not quite clear about how tag changes you make on the PC using MediaMonkey are applied to your QNAP library. In your second screenshot, what do T:\FLAC and N: represent? Which program has produced this screenshot?

If you could provide a step-by-step sequence of what you do when you update one file, that would be very helpful.

Also, please confirm whether your change to the Abba Gold file caused the reported issue on the QNAP instance of MinimServer. If so, which files were shown incorrectly as recently added on the QNAP after this file was changed?