mruddo wrote: > musly_track_analyze_audiofile failed for M:\TestLibrary\Gorillaz\Humanz > (Deluxe)\09-Interlude- Elevator Going Up.flac
Odd. Can you run ffprobe against this file? ffbrobe.exe should be in the 'windows' folder - and it should print info such as the track's duration. Also, if you edit musly.py (in the lib folder) and uncomment (remove the '#') lines 71 and 72 (these lines have ....musly_debug....) and re-run, then you should have more debug (comming from libmusly). This -might- provide more info. mruddo wrote: > The "-" after Interlude is actually a ":" that's been substituted in the > filename already, but given there are a number of other similarly named > tracks on that album it does not look obviously different in any way. Yeah, the contents of the tags shouldn't matter - and I have a few with a colon (mind you I'm on Linux, so my filesystem accepts a colon in a filename). mruddo wrote: > Anyway, 680 out of 681 trackes analysed this time in 2 hours 5 mins.... > so that's not too bad. Not bad? To me that's -slow-! On my 6 (or 7?) year old laptop I get 1140 tracks/hour. Perhaps its because my libmusly uses the ffmpeg libraries, so does not need to start the executables for each track. Still, that's quite a difference! *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
