prabbit wrote:
> 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
The "4" that I referred to was not tracks, but attributes. As in I find
the 4 strongest Essentia attributes a track has (so attributes >=0.8 or
<=0.2) and then filter tracks against those. What my script does is:
Code:
--------------------
for each seed track (the LMS plugin sends a maximum of 5)
get 5000 most similar tracks for Musly
for each of these similar tracks
filter out based on meta-data - to stop repeated titles, artists, etc.
check BPM of candidate track against seed track
check key of candidate track against seed track
check loundness of candidate track against seed track
for each of the 4 strongest Essentia attributes of seed track
check candidate track's attribute aginst seed track
stop when we have enough matching tracks for this seed
randomise selected tracks
return required amount of tracks
--------------------
...there's more to it than that, but that is the basic idea of the
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
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins
