prabbit wrote: > Essentia analysis and running my API server on Windows. It'll be my > weekened/next week project.
If you use windows, then you can download the alpha3 release from the initial post but then get the latest python code from the github repo - as I made some changes that are not in a release. prabbit wrote: > > 1. Will 'mood' (or similar) be one of the attributes that can be used? > > 2. Are all attributes (BPM, key, danceability, aggressiveness, etc.) > combined by Essentia into a single score and is that what used for > matching? If so, is there a way to add weight individual attributes > (i.e., I want danceability to get +10 but aggressiveness to not change)? What this mixer does is, foreach seed track: - Query Musly for similar tracks - Filter these tracks by metadata - title, artist, album - Filter by Essentia key - Filter by Essentia BPM - Filter by Essentia 'loundness' - If tracks have been analysed with Essentia highlevel models then; find the 4 Essentia attributes (danceable, aggressive, etc) of the seed track with which Essentia has very high (80%) or very low (20%) confidence, and check the similar tracks against these. I take Essentia very low value to mean high probability that its not - e.g. danceable 0.8 => is danceable, danceable 0.2 => is not danceable. (There is no 'mood' attribute) The filtering against high-level Essentia attributes seems to filter out way too many tracks for me, so I'm not sure how useful it is. Also, if you have analysed your tracks with Essentia high level (so, on Linux) then you can opt to use these attributes for similarity. However, pleas bear in mind that I'm in no way an expert in this - I would never have heard of Essentia or Musly if not for Roland0 - and I'm just experimenting with trying to create a useful, for me, DSTM mixer that is not MusicIP. And, again for me, so far it seems to work well and is what I currently use. *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
