Anyone ever have this? I load a set and going into my first patch, opening song the CPU is at about 65%. On the 2nd song there would be spots where it hits 100. But- if I stop the engine and restart it drops by almost half; that first song would start at maybe 35% and the 2nd won’t go over 50. Any ideas why this might be?
BTW I keep forgetting to check this specifically but I’m fairly sure this only happens when preloading the whole set, not on any of the individual songs. Not entirely sure though.
I experience the same phenomena, so I configured a shortkey in order to be able to quickly restart audio engine and get the audio load drop to normal level.
I use restart engine with a binding in background rack. Bound to a button on my midi controller.
I do it to feel safe in case of stuck notes.
But I never checked if this helps on audio engine load…
It would be nice if this restart audio engine could be configured to happen automatically after loading a set (being human I could forget to hit a hot key!) - assuming that is not already an option?
But I guess the question would be what causes this behaviour and can it be eliminated?