prabbit wrote: > There was nothing I snipped from the log that related to highlevel > attributes. I pulled your latest changes (9e0fda) and didn't see a > change in the startup logging.
OK, I'll look into this. The idea is to try to automate as much of the config as possible. So, the analysis side sets highlevel to false unless Linux, and the API side (is supposed to) check the DB to see if Essentia results are there and if high-level results are there. prabbit wrote: > You're correct. After I added an "essentia" stanza to my config.json > file to force high-level recognition (it wasn't enough to do so from the > Music Similarity plugin settings' page), then I did see a difference in > both the startup and in the attributes returned with each song. You can't 'Enable' Essentia from the plugin page, only select if you want things to be used if enabled. I want to have the plugin talk to the server to detect if Essentia is enabled, and if high-level analysis results are there, etc. Then the plugin can control what is shown. Just not sure how to do that at the mo... prabbit wrote: > > I'm not sure exactly what you mean by 'current filtering of these,' but > I have some ideas. Some of us on these forums fondly remember Michael > Herger's deprecated SmartMix plugin. It was a fantastic tool that > allowed us to create mixes based on a variety of attributes — just like > the ones in the music-similarity database. It had slider bars that > allowed us to set a range for various attributes and then build a > playlist from the tracks that met that criteria. Never used SmartMix, before my time :) However, this mixer is meant to be driven by DSTM - therefore mixes are based upon current queue items, not a set of attributes. prabbit wrote: > > Imagine I want to query the music-similarity database for all songs with > these values and produce a playlist—that was SmartMix and that's what I > think the purpose of those values would or could be. And this mixer does not support that, at the moment. The *only* thing this mixer does with the Essentia high-level attributes is to find the 4 highest (above 0.8) or lowest (below 0.2) and then filter tracks on that. i.e. Seed happy=0.95, candidate happy needs to be 0.7 or higher. Likewise if seed happy=0.19 (so, not happy) candidate needs to be 0.3 or lower. But I find that filters out a -lot- of tracks - so I'm not 100% sure about this. Please feel free to look at 'check_attribs' in 'lib/filters.py' and suggest improvements. prabbit wrote: > > > > > - happy: > 0.9 - aggressive: 0.4 - 0.6 - danceable: >0.75 - electronic: >0.8 - dark: >0.5 > > > > You do know that these Essentia attributes are the probability that a song matches a model? i.e. happy=0.9 means that there is a 90% -chance- that it is happy, not that the song is 90% happy. *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
