When the soundcard passes us a buffer, Mixbus has to be alerted by your OS, process the audio buffer, and return it to the soundcard before the soundcard needs to play it out. This is a useful number to know if we are trying to finish a hard math problem, or if we are measuring battery usage.īut in digital audio, the timing is much more sensitive. This gives a general indication of how busy your CPU is. HOWEVER: even the most powerful cpu can have very poor realtime audio performance if it is not adequately "woken up" at regular intervals to service the incoming audio buffers from the soundcard.įirstly, you need to understand that the CPU meter on your computer averages the cpu usage over a very long period (perhaps one second). This means that if Mixbus is running smoothly, you won't accidentally overload your system if you enable all the channelstrip features while you are mixing.Ī modern i7-class processor has the capability to run 100s of tracks and lots of plugins in Mixbus. Note that, because of the way Mixbus works, it does not increase the cpu to enable all the EQs and compressors the DSP load for that processing is already pre-allocated when you run Mixbus. Nevertheless, an older 2GHz CPU should be able to handle dozens of tracks and several plugins, with reasonable settings. By default, Mixbus requires significantly more CPU resources than a typical DAW, because it is emulating the operation of an analog console.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |