cpd73 wrote: > No. The code builds 1 list of all tracks to be analysed - the .notmusic > prevents files within those folders from being added to this list. This > is then split between cores.
Understood. There does seem to be something inconsistent about the CPU allocation though. I've now re-run the analysis 7 times, once on each of the 7 top level folders underneath my LMS music path (by specifying the path to each folder in config.ini), and only the 'Lossy' folder ever achieves the impressive 500% CPU load. The other folders achieve no more than ~150%. And as noted above, if I specify the same path as defined in LMS, even with the other 6 folders excluded via .notmusic, the Lossy folder only occupies a few percent. Having now tried all 7 folders, I've at least identified the one that causes the 'No tags found!' error. But am I right that the terminal output reports the last file successfully analysed, rather than the one that failed? Each time I run the analysis in this folder it fails at a different point. I guess I should wait for your next release to be able to track which files in particular are causing the problem. PS. Do you have the facility to compile for Apple silicon? I noted in Activity Monitor that bliss-analyser is an Intel app, which means it's running under Rosetta on the M1 Macbook. I could imagine it would fly if it ran as a native Apple app. ------------------------------------------------------------------------ chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=116068 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
