So after MUCH trial and error, I think I may have tracked down where part of the problem is, although I haven't figured out the best way to fix it. I've moved all the Kontakt instances into VE Pro, leaving DP empty except for one instance of Omnisphere (which I've left disabled for the time being). The CPU meter in DP was still around 40% at idle, so that wasn't it. And everything's running in real time, no pre-gen enabling.
For the last while I've tried to do lots of routing within DP to make it easy to quickly print stems. To do this, I've run things through a couple of layers of Aux channels. For example, my LASS strings in one group, EW in another, Symphobia in a third, so as to be able to reverb/EQ them individually before sending them into through another Aux into a Strings Bus audio track (which is Input Monitored while working, then record enabled to print stems). The stems are then sent out a Master bus into one more audio track for printing the mix, for a total right around 25 busses.
I decided to try deleting some of the busses to see if that helped. I deleted about half of the busses, with a negligible difference in the CPU meter, then kept deleting one by one. With one bussed track still enabled, no real change, but when I deleted that one, the CPU meter dropped down to next to nothing. After rejoicing mightily (and prematurely), I reassigned everything out my main output, and sadly watched it spike back up to around 35% at idle. This is a little better though, so it's starting to border on usable.
Now the odd part is that with nothing loaded into DP itself except the MIDI tracks, a few busses without any processing, and everything sitting at idle, no MIDI recorded into the tracks, no audio files, DP's still hogging 53% of my computer's CPU, according to the monitor in MiniUsage. When I disable the VE tracks, theoretically freeing up the resources, DP is still using 28%. Quitting VE altogether and leaving DP open the meter is around the same.
The only other application open is Safari (so I can type this), and that's it. With the DP session project closed and nothing loaded in VE, DP uses 2.2%, and in an empty session it's around 4%. It seems strange that a bunch of empty MIDI tracks and a couple of Aux busses take that much computing power, so I'm not really sure what to make of it.
And that's where it's at. I'm at a bit of a loss of what to try next, I've got an old slave PC that I can try to bring into service, but it's probably only good to offload a small amount of the load to it.
Thanks again folks, I appreciate the ideas.
Jeff
|
|