Can't remember if I said this before, my bad if I did.
It'd be cool to have a less tedious way to pinpoint which tracks are consuming the most CPU and/Ram, like having a little meter or percentage indicator in the track controls, or a bar that can be hidden like Sends/Returns/X-fade, etc.
CPU/Ram Meter per track
-
friend_kami
- Posts: 2255
- Joined: Mon May 29, 2006 10:10 pm
Re: CPU/Ram Meter per track
would be cool to figure out a way to get that cpu down so we wouldn't need this, but
good idea.
good idea.
-
regretfullySaid
- Posts: 8913
- Joined: Thu Apr 22, 2010 5:50 pm
Re: CPU/Ram Meter per track
I think that's a general and inevitable issue. If you can freeze, do it, half the time I can't because of a sidechain, so I just resample it but keep the old track, turn it off and all the fx, maybe even deactivate the clips (not sure if that plays a part in processing or disk activity if the track is turned off)

