Announcing MinimServer 2.1

[entdgc]

Linn have found the problem and the fix will be in the next release...

I didn't experience this during testing of the initial fix, but have been able to recreate it this morning. It relates to the precedence that is given to different metadata values when the app decides what to display on the UI.

Hopefully this will be a final fix!

[KreTR]

Would it be possible to increase the number of items recently added to 1500? Currently, I have a limit of 1000 and there are weeks when it is not enough. I am asking you to consider the possibility of adding a configuration option enabling such display of recently added sets so that the sets last day, last week, last month are disjoint sets? ie did not contain each other elements from the previous time period?

[simoncn]

Because of the way this feature is implemented, increasing the number of recent items degrades browsing performance, especially with a large library. The limit of 1000 has been chosen as a compromise to ensure browsing performance is not degraded too much.

In the early days of MinimServer, a number of options were added in response to user requests. These options are all described in the user guide, together with examples of what they do. The result has been that some people now find MinimServer is too complex to understand and use and the user guide is difficult to read and understand.

Learning from this experience, my approach now when adding new features is to provide options only when there is a very clear need for them and they are simple to explain and understand. In this case, I think the meaning of the selections "Last day", "Last week", etc. is clear and intuitive. Adding an option to make "Last week" actually mean "Last week but not last day" (etc.) would be less intuitive and would add complexity.

[KreTR]

All the arguments put forward are correct. I have a limit of recently added items set to 1000 and I haven't noticed any slowdown of MinimSerwer. By introducing the possibility of increasing the limit to 1500, you can pay attention to the possibility of slowing down the operation of the Minimserver on weaker devices. The names of individual time slots are not expected to be changed. I would like to be able to configure them so that they are disjoint sets and do not contain each other. It would also be a solution instead of increasing the item limit.

[simoncn]

Many people will set the limit to the maximum. They might not notice a slowdown immediately because this depends on other MinimServer settings (for example, index artwork), how many recent files they have and what they are doing while browsing. MinimServer is designed to work with good browsing performance on alll devices with all configuration settings and I don't want to compromise this.

Having disjoint sets would not enable you to view a larger number of recent files because the limit is on the total number of recent files, not the number displayed in each set.

[KreTR]

I understand, that is, the number of recently added items is counted globally and only divided into time slots, each of which contains the previous one. It is a pity, because if it were counted separately for each time interval, more elements would be displayed. In my opinion, it is a bit illogical solution because, in fact, when choosing a monthly range, I have elements added on the last day or the last week at the beginning. If, however, it was possible to change the sorting for subsequent time intervals and the elements appeared in the reverse order of addition, i.e. older ones first, it would make more sense in my opinion. However, I do not know if you can change the sort only in selected time intervals.