Hi
It used to best practise to turn off Asio-Guard on tracks that were routed to a VEPro instance. Today I tried to turn in on and all the CPU spiking disappeared!
But what is the experience with Asio-Guard and VEPro?
Hi
It used to best practise to turn off Asio-Guard on tracks that were routed to a VEPro instance. Today I tried to turn in on and all the CPU spiking disappeared!
But what is the experience with Asio-Guard and VEPro?