Pace service consuming 10%-12% cpu

That percentage of CPU activity corresponds to my experience here.
I submitted a ticket to Slate a few days back but nothing back so far.

I’m actually on VMR 1.x (latest version of version 1)
But I had the same experience with version 2 which is why I went back to 1

Also for the record, Version 2 does not recall groups properly on VCC because of ‘dreamstrip’ limitations, which is why I went back to V1 also. Its a known issue but a big one when your recalling mixes!