Shunts take up CPU. They don’t count towards estimating what CPU is left like you are because blocks that replace them would negate that usage.
The suggested limit is 80%. That’s the available CPU.
What if it allows 102%?Its a big confusing point especially for new users.
They don't want to know how much processing power the unit needs to spare to work properly
A simple CPU bar how much a user can actually use would be a good thing - from 0 to 100, not from 0 to 100 where the enduser has to try out if the unit mutes around 84, 85 or 86 ;D ... I know its around the forum for many years and I have adapted, but still, I don't understand the reason to show CPU space which nobody can actually use.
"Captain, engineer reports 105 percent on the reactor possible, but not recommended."
Is there a US slang for that? BDU? Brain-dead-user? 
) And of course! No offensive to all new users! I also had troubles to get that in the beginning ...Doesn't the meter turn red just before you hit the danger area?Its a big confusing point especially for new users.
They don't want to know how much processing power the unit needs to spare to work properly
A simple CPU bar how much a user can actually use would be a good thing - from 0 to 100, not from 0 to 100 where the enduser has to try out if the unit mutes around 84, 85 or 86 ;D ... I know its around the forum for many years and I have adapted, but still, I don't understand the reason to show CPU space which nobody can actually use.
If you can calculate and display your current CPU usage, you have to have what 100 percent is.
If 102% CPU usage is fine, or 105%, or 150% or whatever, it still could be recalculate to a range of 0 to 100 - a range every "DAU" can understand (german for "Dümmster anzunehmender User" which basically means .. "most possible dumb user"
Nothing to prioritize but still, I read about this misunderstanding sooooo many times ...
Because it is variable and by allowing you to see the limits this way they are letting you fine tune your presets while also allowing you to break all the rules with what you have available. If they set it with an arbitrary 0-100 they would have to make compromises on what we can do with the available space. On some presets it will run just fine on 80%, but on others it will mute because you have a block or a channel that when engaged will push the processor too much. I have seen presets run with up to 84% but then I switch from one reverb to another and all of a sudden it no longer works just because the new reverb peaks when you run a signal through it. If they picked an arbitrary 0-100% scale they would have to decide on a safe spot to stop you from adding blocks. 0-100 percent with the warning starting at 80% but might work up to 84% would become 0-100% with a hard stop at 70-75% because they would have to use averages in order for that number to mean anything. While it is nice to know that on a Boss gt 1000 I will never run out of CPU, Boss accomplishes that by setting limits on what you can do with the available blocks..Its a big confusing point especially for new users.
They don't want to know how much processing power the unit needs to spare to work properly
A simple CPU bar how much a user can actually use would be a good thing - from 0 to 100, not from 0 to 100 where the enduser has to try out if the unit mutes around 84, 85 or 86 ;D ... I know its around the forum for many years and I have adapted, but still, I don't understand the reason to show CPU space which nobody can actually use.
