Full vs incremental scan in MinimServer2.1

[JimmyTheOne]

I have updated from version 2.0.19 to 2.1. Every time I do a Rescan to eg. add a single change, the server now performs a complete scan of my library. This takes several hours, whereas all the versions up to and including 2.0.19 used to just rescan what was changed.

Is it possible to configure this?

Thanks in advance.
Jim

[simoncn]

This is not normal behaviour for MinimServer 2.1. There is a small change to scanning in MinimServer 2.1 but this should not cause the problem you have described.

If you do a rescan without adding or changing any files, is the rescan quick or slow? The answer to this should help me narrow down the possible cause of this problem. Also, do you have the startupScan property set to true, false or full?

[JimmyTheOne]

Hi,
Thanks for the speedy reply..

A rescan without any file changes causes a full scan with the startupScan property set to either true or false.

[simoncn]

Thanks for this. It sounds like there is a problem either with writing the MinimServer cache file on the previous rescan or with reading the MinimServer cache file on the current rescan.

What device are you using to run MinimServer? When I have this information, I will post instructions for further diagnosis.

[JimmyTheOne]

I'm running on a Mac to run the MinimServer

[simoncn]

In Mac Finder, use Go to Folder to open the ~/Library folder. (This isn't the same folder as Library or /Library.) In this folder, you should see a MinimServer subfolder. In this subfolder, you should see a file named either nnnnn-1.mcache or nnnnn-2.mcache where nnnnn is your content directory name (for example, Music). Do you see this file? What is its size and modification time?

Now do a rescan without changing any audio files. After this has completed, look in the ~/Library/MinimServer folder again. The nnnnn-1.mcache file should have changed to nnnnn-2.mcache or vice versa. Do you see this file? What is its size and modification time?

[JimmyTheOne]

Before scan: nnnnnn-1.mcache today at 10:08 19,4 MB
After scan: nnnnnn-2.mcache today at 17:08 19,4 MB

[simoncn]

Thanks for the quick reply. This is as it should be.

Please check whether you have set the MinimServer property writeAllTags. This would cause the problem you are seeing.

If you have not set this property, please create a MinimServer debug log file as described below. It is important to follow all steps exactly.

1) From the MinimServer menu bar minim icon, select Exit
2) Launch MinimServer from the Applications folder
3) From the menu bar minim icon, select Show log
4) In the log window, set the logging level to Debug
5) Close the log window
6) Do a rescan
7) In the ~/Library folder, copy the minimserver.log file to another file named minimdebug.log
8) From the menu bar minim icon, select Show log
9) In the log window, set the logging level to Info
10) Close the log window
11) Control-click the minimdebug.log file, then select Compress
12) This should create a compressed file named minimdebug.log.zip

When you have done this, check the size of the minimdebug.log.zip file and let me know this size. I will then suggest the bext way to get this file to me.

[JimmyTheOne]

Just a quick reply - I'll create the log file tomorrow but the WriteAllTags property is greyed out and not set.

[simoncn]

Thanks for your help with tracking down this problem. I hope the log will provide the solution.