![]() ![]() Given that Bitwig was able to outperform Ableton in my stress test, I'm curious as to what is the cause for it handling so poorly during actual writing with sidechaining (shaper 2), analysis (oszillos mega scope / spectrum2) and mastering plugins (Pro-L 2) etc. I'm running a 2020 M1 Macboook Pro 13-inch with 16gb RAM on macOS Big Sur 11.5.2. ![]() Ableton has no issue while running all this is in the background, but I'm not sure if that would affect Bitwig differently. In the background, I am running google chrome with a TON of tabs open, music app, rekordbox and mixedinkey. Whereas Ableton has no issue whatsoever until maybe at the very end stages of a very heavy project. However, when actually writing a track, using the same settings (256 buffer, 44.1) in both programs - Bitwig starts to break up almost immediately. Bitwig was able to handle 63 Repro tracks, while Ableton maxed out at 45. I stress tested it before by putting Repro-5 playing the init patch and one note on a 2 bar loop and duplicating the track until it started to introduce artifacts from cpu overload. Loving it so far BUT the cpu takes a shit once I start adding tracks/plugins etc. I'm trialing Bitwig 4.0.1 right now after spending 10+ years with Ableton Live.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |