mruddo wrote: > Just an update on mixes though - as a trend I've noticed seems to > indicate a bias towards artists at the tail end of the alphabet.
As stated on the 'music-similarity github page' (https://github.com/CDrummond/music-similarity), Musly has a 'bug' (https://github.com/dominikschnitzer/musly/issues/43) where all songs can get the same score. Hence why I added a *--test* commandline switch to music-similairty to test the Musly analysis. If this fails it usually just means recreating the jukebox. Passing *--repeat* will cause the test code to delete the jukebox on failure, recreate, and re-test until OK. This -might- not be your issue, but is worth checking. The order that the tracks are processed depends on the similarity order from Musly - my code simply iterates the list of tracks returned by Musly and applies some filtering. *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
