Stop button / keycommand - could it be sacred ?

[sebas777]

When the Reaper engine is overloaded, there's no way you can stop it with a keycommand.

Clicking the button is a little faster, but still it's such a pain to see the sequencer choke and die.

What's even more frustrating, the "tail processing" is not overridden when there is CPU overload, so even after you perform the stop command, Reaper is hanging for another few seconds.

The point:

I mean the stop button / keycommand is an "overload panic button", so maybe it could have higher priority ?

And when resuming playback, is there any hope for a "preload time" slider in the Arrange (or a self-calibrated mechanism) to guarantee the stuttering will not happen again ?

Or another idea: using lower bit resolution for previewing mix, and 64bit for rendering, to save CPU [a switch in the Arrange]?

I mean, even on a fastest machine sooner or later you are going to reach 100% CPU, so it's not only important for little guys like me with my PIII 800Mhz