afriend wrote: > BTW does it fill the metadata at the end because a first look at the > musly.db (in progress) shows the relative path (files) and the values > (vals) but the other metadata columns are still empty.
Yeah, meta-data is saved at the end. afriend wrote: > Good to know. So if I don't have any cue files this path is never > called/checked and I don't even have to set it in config.json, right? Correct. afriend wrote: > Could you add os detection to *lib/musly.py* so manual editing of line > 31 won't be necessary? Create a pull request on github, or send me your modified file. afriend wrote: > > And how do you feel about adding/moving these settings from app.py to > config.json: DEFAULT_TRACKS_TO_RETURN, MIN_TRACKS_TO_RETURN, > MAX_TRACKS_TO_RETURN, NUM_PREV_TRACKS_FILTER_ARTIST, > NUM_PREV_TRACKS_FILTER_ALBUM, NUM_SIMILAR_TRACKS_FACTOR, SHUFFLE_FACTOR > ? Might be nice to have all user configurable settings in one place. Can do, but do they need to be configurable? Not sure I really see the point. NUM_PREV_TRACKS_FILTER_ARTIST and NUM_PREV_TRACKS_FILTER_ALBUM perhaps - but then if that was the case the I'd add them to the API, and allow setting of these in lms-musicsimilarity. I'm wary of having things over-configurable as that then creates extra scenarios for things to go wrong! But, let me know how the mixer works for you - as there is no point adding extra features if no one is actively using it! afriend wrote: > > About *create similarity mix*: when I call that from a track's context > menu/song details page it's using only this one track as a seed, right? > In other words, I could just take a look at which tracks musly-server > thinks are similar to this track. Yeah, for a track it just sends that one. I've started the analysis. Since you commit after 500 tracks maybe you could a small info message stating the total number of tracks processed so far. Would make it easier to track progress. afriend wrote: > > Anyway, I just wanted to thank you for taking the time to explain things > to me and for musly-server. And a thank you to Roland0 too. Quite > curious if this is going to work out on macOS and if it's going to make > listening to my music more interesting. As far as Essentia is concerned, > I think one of you mentioned that the analysis part was *a lot* slower > than musly so I guess I'll never get to use that one because my hardware > is quite old and slow. As a rough estimate, Essentia is about 14 times slower. Musly took around 1hr to analyse ~20k tracks, and Essentia took about 14hrs. Both still faster than MusicIP. *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=112713 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
