According to the html page, the total load at 48kHz (which is what the csv file is based on) for 64 block size is between 237% and 250% for the tests that aren’t “Isolated” (The “Isolated” test is when no jacks are patched, which is not the case here obviously). If you divide those by /2 (because there are two cores) then you’ll get 118.5% - 125%.
That’s over 100% so that tells us it won’t run at 48kHz. Let’s see if it can run at 32kHz… 125% * 32/48 = 83%. So it should be about 83% at 32kHz.
And indeed if I run Ambient Gen at 32kHz with block size 64, the load on the MM is about 87-88%. So it seems like the html file’s calculations are pretty close, you just need to divide by two (since there are two cores) and probably report the value scaled for 32kHz and 24kHz.
What do you mean by “memory is all blown out”?
Do you mean the “Construction Time(ms)” and “FirstRunTime(ms)” columns? Those are in milliseconds (ms), and they refer to how much time it took to create the module and run it the first time. Some modules do special allocations and setup when they process their first sample, so this column will detect that. In general though I think it can be ignored, it’s rare and not relevant to CPU usage.
The included .html has the new calculations in it. But Ambient Gen.yml for me still calculates to over 100%. I think it’s because it doesn’t have different sample rate metrics. The .csv looks to be one run at a certain rate?
A few questions. In the plugins .yml there are regularly 5 entries in the CPU list. Are these the sample rate metrics? Are they in high to low or visa-versa? If this file is kept up to date and available, I wouldn’t even need the .csv file.
The five entries are the CPU load (min-max) for each of the various block size settings (32, 64, 128, 256, 512).
The CPU load measurements on module finder are all based on a sample rate of 48KHz. So if you want to guesstimate the load for 24KHz just multiply the current value you are calculating by .5.
Likewise for 32KHz you’ll need to multiply by 32 / 48 or .666
This file is regularly re-generated every time the website is updated, so you can rely on it being up to date. Be warned though, sometimes when we add features to the website, the schema of that file changes, which can cause your app the break.