[FIGURED OUT]Updated to latest MM firmware, single modules are maxing out CPU

[danngreen]

I just posted a huge spreadsheet of CPU load measurements:

CPU load number database

I wrote some code to measure CPU load for every module under various conditions. I have the raw results here. Goals The goal is to create some new features on the MM hardware and in VCV that leverage pre-recorded CPU load data to make a reasonable estimate of CPU usage of a patch. For example, the MM firmware could tell you in real-time how much the CPU usage would change if you added a certain module. Or to be able to browse modules and choose the lowest CPU utilizer that does the function you…

There’s a ton of data in there, but the line relevant to this thread is that the SpringReverb had over 100% CPU usage at all block sizes, even when unpatched, except for block size of 512. Also, if you just scan the spreadsheet you can see most modules don’t change much under different block sizes. SpringReverb might be the only one?? (I have yet to parse and analyze it all)