Something I've been wondering for a while: how come Sonar doesn't max out processor usage during fast bounce?
 
I use Izotope RX 3 quite a lot, and for non-realtime operations, it goes full whack on all cores to get them done as quickly as possible.
 
Not a criticism particularly, just curious as to what's going on in Sonar that makes this a bad idea / hard to do / something else.
 

I am not quite sure either, but the coding itself can throttle usage, and this can be for very good reasons. Video editing is the only time I have seen programs run "full bore" (encryption is another case) and the CPU temperature ramps up quickly on my machine even with good cooling. With heat increase in the CPU, page fault/thread errors rise as well (have noticed this with benchmarking software), so I assume this is very intentional behavior. The worst offender I have seen (temp wise) is Windows Movie Maker... if rendering a full-length movie, CPU temp will exceed limits and the BIOS front end (ASUS AI Suite II) intercepts these processes and throttles them (was sort of painful to watch the CPU reach max recommended temp and stay there for 20+ minutes)... if it were not for the BIOS, it would have burned up in one run. Adobe Premiere Pro actually throttles itself prior to the CPU temp being reached. The coding for bouncing in SONAR is probably chosen for the most conservative case (again, I am assuming).

Bounce involves writing a new file to disk. The processing time may be more limited by disk write speed than CPU.

Hmm... possibly yeah. I've not noticed any difference between bouncing to an SDD or an HDD though.