What can we expect for the future?

[simoncn]

(13-08-2012 08:09)winxi Wrote:  

(12-08-2012 20:59)Hans Wrote:  There are two aspects that I am not quite happy about:
1 If I add music to the my database which happens every few days Minim will not automatically update (not real-time or not very nowand then).

I'm used to this feature from twonky, but i don't miss it with MinimServer at all as the rescan works incredibly fast (in fact, i wonder how this can be achieved). BTW, twonky forces a database rescan at every server restart which takes ages. thus, twonky needs about 20 min. for my ~25000 audio files to be fully available, Minimserver will need just half a minute.

IMHO, the thing that could be optimized about MinimServer rescan is that MinimServer should continue being advertised to the LAN during the rescan process either showing no contents or even better: showing the contents that were available before the rescan. In some control points, if the server disappears, the control point will automatically select another server available, and one will have to switch back manually to MinimServer when the rescan has finished. But that's just complaining on a high level i guess

That's a good suggestion. This would be a new Rescan operation in addition to the current Restart (which is equivalent to a database rebuild in Twonky, but much faster). Ideally, the Rescan operation would incrementally update the current contents list with any new music found and remove music that's no longer available, without disrupting any control point browsing or music playing currently in progress. It would be as fast as or faster than the current Restart, and the changes needed to implement it wouldn't significantly impact browsing performance for large collections (> 100000 items).

It would be extremely challenging to achieve all of the above. If it can be done, it would require major changes to the internals of MinimServer. This means that it's something for the MinimServer 2.0 wish list rather than a 1.0 work item.