Announcing MinimServer 2.1

[Peter@57m]

(06-01-2022 12:13)simoncn Wrote:  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?

This is the setup

   

So the master copy of my music is held on the QNAP mapped as drive T on my Windows PC.
I use MediaMonkey to make any tag changes directly on this mapped drive. I also use MediaMonkey to create playlists.
I then run FreeFileSync running on the PC to compare the files on the QNAP, mapped as drive T, to the files on the Melco, mapped as drive N. The second screen shot was of FreeFileSync.
I then rescan MinimServer on the QNAP and the Melco.

The change to the ABBA file did not cause it to appear in either the QNAP or Melco instance of MinimServer as Recently Added

[simoncn]

Thanks, Peter. Because you are doing all this from Windows, files in a folder are always sorted and scanned in alphabetical order. It seems this order is preserved when Windows is modifying or syncing between mapped network drives.

I think the issue arises when a sync program is copying directly from one Linux system to another without going via Windows. On Linux, the sorting/scanning order is not necessarily alphabetical and can change because of copying/syncing activity.

[edj]

If it helps isolate or understand the problem, this is my setup:

My music collection is on a Windows 11 desktop, managed with MediaMonkey 5 and stored/synced with OneDrive.
The music is pulled from OneDrive onto a Synology NAS (DSM 7) using the Cloud Sync package.

I've just done some more testing. This applies to "old" tracks being edited.

- If it is the _only_ track in the album, it does not appear in the Recently Added list
- If it is the _last_ track in the album, it does not (nor do other tracks from the album) appear in the Recently Added list
- If if it _not the last_ track in the album, all subsequent tracks from the album appear in the Recently Added list

[simoncn]

Many thanks, this helps me understand what is causing the problem and how to test a fix.

[simoncn]

A fix for this problem is available in MinimServer update 211. After you have installed this update, files updated by a sync operation should no longer be shown incorrectly as recently added.

At present, this update is available for manual installation from the Packages tab of the Properties dialog. Please try it and let me know if it fixes the problem.

[RSJ]

That seems to have sorted things for me. Updating tags or artwork on my PC and synchronising with a QNAP via Qsync no longer results in an album being added to the 'Recently Added' list.

Many thanks

[simoncn]

Thanks for trying this so quickly and letting me know.

[Peter@57m]

Simon I seem to have a problem with release 211 on the Melco. All is OK on my QNAP.

I was going to update the Melco to 211 from 210 but thought I'd run a check first.

1. Before making any changes to MinimServer, I updated another track on the ABBA album on the QNAP source files
2. I updated playlists and copied all changes from the QNAP to the Melco
3. I did a rescan on the Melco
4. Looking at Recently Added there was no entry for Last Day but there was an entry for ABBA for Last Week. This was the track that I had changed on 6 Jan for the previous test. I guess I didn't notice this error as it hadn't appear in Last Day
5. So I updated the Melco to 211, hoping this would resolve the problem
6. With 211 Last Day now shows the track I updated today
7. Last week now shows both tracks on the ABBA album that were updated, the one updated today and the one from 6 Jan
   

As I said above the QNAP instance is behaving as expected, but here the changes are applied in situ. For the Melco the files are copied.
I know that earlier versions of 2.1 did not have this problem. I will see if I can narrow down which version introduced the error.

Screen grabs:

   

[Peter@57m]

(08-01-2022 14:05)Peter@57m Wrote:  I know that earlier versions of 2.1 did not have this problem. I will see if I can narrow down which version introduced the error.

So I went back to version 208 of MinimServer on the Melco
I then changed another track on the source album for ABBA. Copied changed files to the Melco (playlists + the one new changed track)
Recanned on the Melco and the new track did not appear (the previously changed ones still appear. I know how to get rid of these and will do so later)
So 208 on the Melco is OK.

Updated the Melco to 209 and its now picked up the newly changed track in Last Day and Last Week. So something changed between 208 and 209 that causes tag changes when copied over to the Melco to be picked up as new items

Not sure why I didn't pick this up at the time. This time I was making sure I exited Kazoo on the PC before making checks as I thought I noticed it seemed to be using cached data at one point.

[Peter@57m]

(08-01-2022 15:51)Peter@57m Wrote:  Not sure why I didn't pick this up at the time.

OK I think I didn't pick it up as I do a rescan after a copy to check the version, however this does not seem to update Recently Added.

With 209, I tried updating another source track and copying it over. Did a rescan of the Melco MinimServer and nothing had changed in the Recently Added items from before the rescan.

I then did a restart and the newly changed track appeared. So I assume I have been upgrading to a new version which does do a relaunch, then changing a track and copying it over, then doing a rescan and not seeing a change.

So in future after doing a change I will do a restart