Have for two weeks now tracked what cause a silly little system event to make Cubase think there are dropouts and restart audio engine.
Not seen in Sonar or Reaper - not a glitch ever - but Cubase seems to struggle with something internally and get disturbed by something in system hourly that does not even show cpu anywhere.
So did as test - just turn off multi processing in audio settings - and voila.
I can at least record over that system event, whatever it is - not getting the clipping.
I still get a little crackle - but it does not stop recording.
But it’s cruising on 5-6% instead of 8-12% cpu. Three cores activated and seems much more happy.
A project just 15 tracks, and a superiordrummer running and some plugins.
I think there is something really wrong internally in audio engine as it is now.
So many threads - what are they doing?
All 8 cores with an even load of 6% each???
No transport running even???
I did the same thread listing in process explorer with Sonar and Reaper - it does not even fill half the screen with threads.
Cubase is one and a half screen listed with threads???
For you that as I been at wits end with the audio in Cubase - try it…