prabbit wrote: > While it's perhaps to be expected, I've found that using the same seed > song over and over plays the same group of songs (albeit in different > orders), including songs I have rated low and would prefer not to hear > too often, than occurs with Spicefly Sugarcube/MusicIP. This is true > even though the playlist runs for hours. Sugarcube has a setting to > exclude tracks below a certain rating, which "protects" me from hearing > these lowly-rated tracks. My experience with Sugarcube using the same > seed song repeatedly is different, in that it produces a wider range of > playlists. I'm still playing with Similarity's settings, which is the > genesis of my question.
Yeah, I agree the randomness of selected tracks could do with improving - especially if there is only one seed track. I must admit I tend to have DSTM kick in after playing an album. prabbit wrote: > Curiously, Heart thus far seems to be the (Six Degrees of) Kevin Bacon > in my collection. I used Stevie Wonder's -Superstition- as a seed track > and soon enough got to Heart. Used Iron Maiden's -Can I Play with > Madness?- and shortly thereafter heard Heart. And I played some other > seed song from the 2000s and landed on Heart within a dozen tracks. This > is anecdotally interesting because I don't have that many Heart songs in > my collection. Odd, I have Heart songs - but when I choose 'Can I Play With Madness', I don't see Heart being selected. However, different library, etc. Have you tested your analysis results, as stated on the music-similarity github homepage? Musly does have a known issue where it assigns the same similarity to all songs. If everything is OK with that, perhaps set all the filters to 0, so that just Musly is used. Seeing as you have analysed your tracks with Essentia high-level, you could try setting 'Similarity weighting' to 100. This will cause only Essentia to be used. The similarity score is the calculated on how close each track is to the seed track's Essentia high-level attributes. Would be interesting to see if you see an improvement there. Or even try at 50, so that both are used, etc? *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
