prabbit wrote: > Understood, completely. It's your tool for your use case that you've > chosen to freely share. I was commenting on what I saw after I took a > peek behind the curtains and started to understand how things were > connected. I don't currently have the skills to fork what you've done > thus far to extend Similarity into SmartMix 2.0. But maybe someone else > does or maybe you do, if the idea of creating playlists or influencing > playlists based off of specific Musly/Essentia metadata is interesting > or exciting. And if not, no complaints here. This is > freeware/donation-ware, and I accept everything that comes with such a > plugin.
I'm more than happy to add such functionality, or have others submit pull requests, etc, to implement this. Just that its not the current focus. I love the DSTM feature, its how I mainly listen to my music now - lpay 1 track, or album, and let LMS continue to add more tracks based on that. prabbit wrote: > I'm not a math(s) major Me neither! I really am just making this up as I go along! prabbit wrote: > > I've also only had an intro to statistics course at university. If 1000 > tracks are selected to build the model music style database and then the > 4 highest or lowest are used to filter based on a comparison to the seed > track, I wonder if we're running into a sampling bias (or some other > statistical bias). The 1000 tracks get further split into genres/genre > groups based on relative percentage to the existing catalog and that > affects the model. I do understand Similarity is pulling from the entire > music collection when selecting a song to play and not just the 1000 > model tracks. Like you, I only use local files; I do not use any > streaming services. I know nothing about statistics, or indeed how Musly does its similarity or how Essentia matches against models, etc. I'm just trying to put bits together! My initial thinking was that Musly is pretty good at getting similar tracks, so then adding filtering by BPM, Key, etc. would help improve even more. prabbit wrote: > Right now Similarity is a bit of a black box to me and it's not clear > how much of an effect any one lever/setting has on a mix, so I've chosen > to disable most settings and start fairly wide open. Next, I may go to > the opposite extreme and use a very narrow range of setting values. As I > get a sense for what's happening, I'll know where to go to make > adjustments. I agree, hence the initial post asking for best default settings, etc. prabbit wrote: > I do fully understand that and appreciate the distinction. The closer to > 0 a value, the less likely it is that type; the closer to 1 the more > likely it is. The intro to statistics course taught me that much. I do > admit that I don't recall everything from the class though. :) Sorry, I didn't mean to sound condescending. You probably know more about the theory of this than I :) *Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here. ------------------------------------------------------------------------ cpd73's Profile: http://forums.slimdevices.com/member.php?userid=66686 View this thread: http://forums.slimdevices.com/showthread.php?t=115609 _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
