I probably miss the point.
let me make a brief on how I understand we are: 1. Michael did a great job making LMS able to store sub libraries definition as a list of tracks belonging to a library (or libraries for the track, is the same). 2. The original intent of Michael was to create an infrastructure to be used by developers for plugins, the great advantage is (or it will be soon) that in all the LMS libraries will be considered and used in consistent way, and this is and must be the first Michael commitment on this point, is up to developers make existing plugins comply to this and take advantage. 3. As a plus Michael released the Library demo plugin, that show how to define libraries in plugins. 4. As a plus, Michael enabled Advanced query to be a simple method to define libraries. To me point 4 is 'dangerous' becouse is an easy prediction that in a wile we will see a lot of requests, like the one to enlarge the genre list field, rising up. I for me I'll like the capability to use url structure to define libraries, but I retain myself to ask. 5. My suggestion was here just becouse I think is the more flexible and less costing mods could be done in LMS to enable people use this great functionality without the needs of complex UI or plugins, since every logic will be defined and applied outside LMS. The last is not opposed as any other development in LMS or in plugin, new or existings, who is going to use what is, as usual, a matter of personal preferences, needs and culture. What I could not understand is in what is different using a query defined in LMS and applied in every scan from the same 'query' defined i.e. in Foobar and applied once to add the library to tags. Wy it should take few minutes in LMS and days in Foobar? a. Foobar has much more capability than advanced query (more parameters, regular expresions,...), so using it you did even not have to ask Michael to do nothing on LMS (and accordingly wait for). b. The execution time could maybe be longer, but with a 50K tracks library this has never been a big deal, then, considering you need to do it just once, while scanner will process query in LMS everytime, in long terms could easily result in a benefit. What when your son will start to listen to something he call Rock, but nothing to do with you use to tag as Rock? c. Result is exactly the same, library_track is populated by a value calculated at scan time based on some user logics and then used all over LMS. Difference is LMS in one case in not aware of what this logic is, and this to me is be a good separation of concerns principle implementation. Marco. ____________________________________________________________ SB+, Klimo Merlino + Kent Gold, Monitor Audio Studio 20 Gold SE+, Klimo reference and DIS Interconnect. ------------------------------------------------------------------------ marcoc1712's Profile: http://forums.slimdevices.com/member.php?userid=34842 View this thread: http://forums.slimdevices.com/showthread.php?t=101701 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
