I finally located the resource monitor 
I deleted a few more tracks and then disabled about thirty and it is definitely helping.
1 Like
Looking at your CPU monitor, it appears the workload is pretty evenly distributed across the cores.
Is this after you started disabling tracks, or is this with the original workload?
This was with the original workload.
Interesting. The CPU doesn’t look overloaded but your system does appear to be I/O bound.
160 audio tracks and 3 Kontakt instances is quite a lot for a machine of that vintage.
Now that you’re reducing the number of tracks, is the disk cache meter getting back to something reasonable?
Yes it is! Most tracks are/were muted anyway, but that doesn’t seem to make a difference. Neither does the fact that for the most part they were short 8 bar recordings. Disabling tracks is definitely working. I have definitely worked with high track count projects in the past, with long parts, and never encountered this issue. I guess the chances are I hadn’t hit 160 tracks before.
Sounds like you’ve got it under control anyway, so good luck!
Thanks!
Thank you everyone for all your helpful advice!
1 Like