Yes right, waveform scratch is using:
COs "scratch_position_enable" and "scratch_position"
while the rest I think is using "scratch" or "scratch2" and "scratch2_enable"
I am not sure which high-resolution timer your mean.
Simply query our new PerformanceTimer does not hurt. What would hurts is an other real-time task apart from the Audio-Engine-Task and the time critical waveform renderer (currently in GUI Thread). This is the issue of Bug #1157579.
Yes right, waveform scratch is using: position_ enable" and "scratch_position"
COs "scratch_
while the rest I think is using "scratch" or "scratch2" and "scratch2_enable"
I am not sure which high-resolution timer your mean.
Simply query our new PerformanceTimer does not hurt. What would hurts is an other real-time task apart from the Audio-Engine-Task and the time critical waveform renderer (currently in GUI Thread). This is the issue of Bug #1157579.