|
Ableton Live Tip for Multicore CPU's
|
View this Thread in Original format
| Beatflux |
| The Ableton CPU meter only displays the busiest CPU core at one time. Each channel only uses one core, so if you load up with effects it can only go take as many effects as one core can handle. The solution is process the sound through multiple channels and/or sends. |
|
|
| Storyteller |
| quote: | Originally posted by Beatflux
The Ableton CPU meter only displays the busiest CPU core at one time. Each channel only uses one core, so if you load up with effects it can only go take as many effects as one core can handle. The solution is process the sound through multiple channels and/or sends. |
I'd like to add that this goes for just about any sequencer out there. It's (virtually) impossible to spread the cpu load of a single channel across multiple cores. |
|
|
| kitphillips |
There are some funny glitches when it comes to bussing though, I believe that ableton processes every chain on a single core, so simply sending the signal from one chain to another won't get it onto a different core.
Also, the meter doesn't measure CPU usage, it measures audio buffer usage, which is completely different. Obviously, audio buffer is constrained by the heaviest loaded core, but its not just simply CPU usage. |
|
|
| EliPsE |
| I do that in Logic and works out well |
|
|
|
|
