erland wrote: > I believe you can do exactly this with the API Michael has created, he > created two ways to register a library: > > The above is based on an SQL statement, which is the solution you don't > like. >
Hi erland, how are you? I never sayd I don't like using SQL, indeed this is the wayI actualy use, starting from the library demo plugin, currently looking for a better way. I only speculated about the opportunity of using advanced search as 'main' source to create those SQL, I think this could drive to a lot of modifications and lead to a very complicated UI, but never mind, if for people using just genre or simple parameters already in ADV Search its OK, don't see why not to use it. erland wrote: > > If third party developers (such as you or me)... Please dont confuse masters with absolute beginners, I'm not a plugin developer at all, just willing to try. erland wrote: > > Finally I just want to give Michael credit again for the way he did this > implementation, starting with the API and thus offer possibility to > third party developers to extend it is the way forward in the future > since we don't know how long Logitech will let Michael continue to work > on LMS core software. This way we always have the option to extend the > functionality through third party plugins even if LMS core development > stops completely. +1. erland wrote: > > In this second variant you can get the information from what ever place > you want, your callback will be called by the scanner and it's your > responsibility to fill library_track with suitable tracks for your > library. If you want pick them from foobar that's just an implementation > choice of your plugin. Not sure it was clear enougth what I suggested: 1. Make the scanner look for a specific TAG named i.e. "Library" in the audio files. 2. Use values in this tag to populate libraries and library_track table. No needs to look at foobar or other, Foobar was named just as an example of application able to mass tag files in a 'query alike' way, but the benefit is that you could use whatever You want to just fill the library TAG. I suggested to do this in LMS standard scanner, just replicating the way it does for genre - is exactly the same - in order to have a clean implementation with a little effort. Michael suggested to do this in a Plugin, then I'm looking forward to retrieve info on how to do it, but I'm a beginner just starting to undestand how plugin works. In my understanding, I think this could already be done by your custom scan plugin or something very similar, since it does not need to store Library in custom tags, but directly in library_tag, not sure, but I think it lack the capability to read metadata from .cue files' is this correct? Please let me know your mind about the opportunity to write a new plugin for this. Many tanks, 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
