Yes, that was me mixing up the bananas with apples...
I gave you wrongly the "processor time %" value. It was that value that was 1.7. It's the default value that shows up in that graph in the M$ program. Sorry for that.
But would it not be more appropriate to use the drives q value that you use as source for the burning as trigger for the "hard disk activity to reach threshold level"?