prabbit wrote: > Meta:NONE There is Musicbrainz and other metadata present in the files.
Perhaps this is an issue with the mutagen library that is used to read tags. prabbit wrote: > Thread exception? - name 'resp' is not defined My files are on a mounted > network drive, but the only thing the computer is actively doing is > analysis. Ah, that's a coding error on my end - used wrong variable name! Hopefully fixed now. However, this should only occur for analysis errors or filtered out tracks (due to duration or genre). prabbit wrote: > gzip: /mnt/g/music-similarity/cache/Abba Gold - Greatest Hits/1997 - 1-8 > - The Winner Takes It All.flac.json.gz: Operation not permitted /mnt/g > is a local drive that is read/write and the file does get written; it's > present. That's not an error string that I have written, must be the 'gzip' command that is showing that error. prabbit wrote: > This statement hints that after a track has been analyzed it is skipped > in future analysis runs but isn't explicit. Is that what actually > happens? Of course. The script iterates your filesystem for music files, and checks whether they are in the DB or not. Any files not in the DB will be analysed. Any files listed in the DB but not found on the filesystem will be removed from the DB. (You can force the script to re-analyse files, or just to re-read metadata (in case tags were changed)) prabbit wrote: > > When I start the analysis, nothing actively happens for hours after the > Temp folder phase. I assume a process is querying my music folder for > files, but I wouldn't think that would take hours each and every time. Me neither. Even over a shared network drive hours seems a *very* long time. Needless to say I have not experienced this myself - but then I have local copies of all my files, and on SSD. For me it takes a meter or seconds before analysis starts - and this is with ~25k tracks. *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
