...
But, there could be other possible reasons... So, why is the essential question.
…
You're right, i should have told you my reason.
The reason is, i have a really huge library with about 250,000 items.
These are mostly very small sound snippets that i use for sound-collages.
I'm heavily tagging these files and i'm pestered by the delays that occur for every single field change.
This is not the case with moderate sized libraries.
I know the features of MC pretty well, so filtering, smart lists or views are no foreign words for me
.
Another reason to reduce the input for a library: Every auto import has to pass through all titles of the library.
That is very time consuming, especially if you add titles very often, like i do.
Even deleted titles are still contained in a library.
You can test that when you remove all titles from the library and then auto import new titles.
All old titles are tested again in spite they should have gone already.
If you clone a huge library, then delete all items, and afterwards import new titles, it takes forever until the library is ready.
My reasons (in short words) why i want to keep my active library as small as possible: I want to reduce latencies when tagging.