In the past Bitwig scored as Badly as Live in any CPU stress test I did with it, scoring roughly 70% of what Logic, DP, and Reaper can get, track count wise, with plug ins like U-He Diva etc. Over the last 15 years the most reliable and consistent CPU test to see about track count and general performance for your DAW and your PC or Mac has been a "to failure" test.
Simply put, load a CPU pig like Diva on a track, do a one note or chord run of eighth notes (both have relevance), copy the MIDI and Diva track as many times as you can before you hear audible glitches, back off and that's the amount that DAW can handle on your system. Typically this is consistent, but not anymore. I mean, not even close!
Bitwig tested with Diva on my 2012 2.7Ghz 16GB RAM Macbook Pro is like before, terrible, 4 instances of Diva compared to 8 in DP10.
Bitwig on my heavily modified 09 Mac Pro with 12 3.33ghz cores, 24GB RAM, is scoring and I'm not making this up, 36 instances of Diva!
(in comparison DP10 is scoring only 11 tracks on the Mac Pro, it seems to be able to use the virtual cores on the macbook but not the Mac Pro?)
For the most part other DAWs like Logic, DP and Reaper are consistent with their performance but Bitwig Loves the old Mac Pro, just adores it! The two areas where it beats the macbook clearly are in graphics processing and CPU count, 12 cores as opposed to four, and the Mac Pro has a Radeon RX 580 8 GB graphics card.
No other DAW is showing these wild numbers and you can clearly see Bitwig runs each instance of Diva as a separate process in Activity Monitor on OS X, so it's not cheating somehow, all instances are using CPU etc.
Why is it so terrible on the Macbook Pro and so good on the Mac Pro? All other DAWs on my system are showing more like you would expect with the power and years difference between the two, like a little over half the power of the Mac Pro with the Macbook Pro, but not Bitwig?
