bakker_be wrote: > I've had some trouble getting this to work correctly, but with some > debugging I've now at least come to a point where it's analysing all > tracks. What I don't get is why I need to use the" --force" switch to > get get it analysing. Attached the logs with & without ..
Not looked at the logs, yet, but you don't need to re-analyse. The DB should contain all the required info. This config just allows you to specify that for the initial similarity that you want to combine Musly & Essentia. It was jsut to replace the prebious UI setting that you had used. The data required is the same as before. "--force" is used to force the analysis code to re-run. This is used, for instance, to re-read the Essentia JSON files if I were to ever use a new value from there. *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
