Bitwig studio engine cpu usage 2018 Patch#
Bitwig studio engine cpu usage 2018 pro#
Bitwig studio engine cpu usage 2018 software#

I updated to the latest version of Bitwig today and got 36 instances! ! In the test I did Diva was used, it's not made by Bitwig, and it's clearly running as a process in separate instances in OS X, Bitwig are using the systems core allocation to get better performance, and the shocking thing to me is it's an old as the hills Mac Pro, 2009 with a modified chip base of 12 3.33Ghz cores. Now if you're thinking about Apple showing off Logic with their latest hardware with Logics built in instruments, yeah, that's cheating. This is without any time stretching or other CPU intensive task, just virtual instruments and CPU. Live for instance consistently gets roughly 70% of the performance CPU wise of Logic, Reaper, or DP on my system. Over the course of 15 years, using and testing at least 6 different DAWs on roughly ten machines, stress tests are a great indicator of real world performance. The only thing it's good for is to put a load on your hardware to see how well it comes (like an SSD to get a true speed readout) but software? That's not reliable at all.

Bitwig studio engine cpu usage 2018 software#

In other words: ensuring that the test routine gives a much better result because the software itself caters to providing a higher priority in order to get those better results. I wouldn't even be surprised if they have added routines in their software in order to cope with such stresstests and address the testing environment directly. They're good to put load onto an engine to see how the engine behaves under stress, but that usually doesn't even come close to resembling a real working environment.Īnd considering the way Bitwig started and all. See: stress tests seriously don't mean all that much within this context. Pardon me for being very skeptic here, up to a point where I'm having a hard time taking this serious (no offense). I have no idea why they aren't shouting this from the rooftops?įor the first time since Bitwig came out I'm seriously thinking of switching. They talked about improved performance but I didn't expect this! In the Activitly monitor in OSX it shows Bitwig running a separate process to the OS for every instance of the plug in, thereby giving the OS the task of allocating resources for the plug in, and just destroying all other DAWs in the process.

Live has always performed worse than Logic every time I've ever done this test in the past, and unless something has changed it will be the same.īitwig just killed everyone, literally wipes them off the map. You add tracks until the audio starts messing up then back off.

Bitwig studio engine cpu usage 2018 pro#

OSX Mojave, 2009 Mac Pro 3.33ghz 12 cores, at a 256 buffer in all four DAWs.

Bitwig studio engine cpu usage 2018 Patch#

Running a simple test of the INIT patch Diva instance playing an eighth note run for four measures cycled. I'll come back to this thread with Lives results, but we were talking about Logic, Digital Performer, Reaper and Bitwig.

So, in a thread on another forum about various DAWs and CPU usage I was prompted to run a performance test again.