The DAW needs the data in time so it only cares about the latency. So if your DAW is set to a buffer equating 1ms, a processor that can do 100 calculations in 1ms is more valuable than a processor that can do only 10 in 1ms, but 500 in 2ms. The DAW only cares about how much time it has.ĭAWs don’t use ‘real’ CPU usage because it’s complex to do, and because it doesn’t matter how fast the computer can process audio, it only matters if the data arrives in time. It doesn’t actually care about how much CPU is being used. So if it took 2ms to process the project and it has 2.9ms to complete the whole buffer then it will report 69% CPU usage (2 / 2.9). Most DAWs report CPU in terms of ‘how much time is left’. So if you are at 44,100hz sample rate and your buffer is 128 samples, the DAW has 2.9 milliseconds (128 / (441000 / 1000)) to process everything. Everything has to be done in that number of samples. That chunk is what you setup as a ‘buffer size’ in Mixbus. Plugins now can show a CPU usage profile, and it’s done correctly.ĭAW’s process everything in chunks. This might be my personal favorite feature in Mixbus 5. When those get sorted then I think it’ll add some functional value to the Mixbus 32c package for new users. It’s a great addition for people that don’t have a bunch of VST plugins already, but some of the current bugs make it annoying to use. Typing in values doesn’t work at all for me.The knob indicators are difficult to read.Once they’re gone then you need to use the knobs or resize the graph area to get them back. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |