Bitwig: Performance improvements?

[Ah_Dziz]

I've had bitwig since V1. It's a fun environment especially for sound design and live jamming. Unfortunately it's very noticeably the worst host I've got when it comes to performance. I kept updating through V3 on my older system and I can't get even close to the performance out of Bitwig that I can get out of Cubase or even Machine. I was wondering if this is something they've improved through V3 and V5.
I've done all I can with the sandboxing and playing with my drivers. I'd like to get the latest version but I'd also like to see some pretty major performance gains when using 3rd party plugins especially. All the newer fft based devices and stuff seem great but if they are going to knock down my computer it doesn't do me much good.
I'm on Windows 10 and I can run a huge (200 tracks) orchestral template with tons of plugins in place in Cubase while bitwig generally doesn't get past 10 or 20 tracks before it starts acting up. I'm not expecting to be able to replace cubase or anything. I'm happy using cubase for my actual work. I'd love to be able to make a full production in Bitwig though when I'm doing other more exploratory music. I'm not really seeing a huge move up in the old version I have with a newer system. So I'm wondering what (if anything) to expect if I grab V5.2.

Thanks
JJ

[rageix]

I stopped using Bitwig due to to performance issues as well. I would get small stutters here and there on any decent sized project. When I tested out V5.2 it did seem like there were actual performance improvements (no more stutters) when I opened up and played some old projects. I haven't tried making a brand new track in the latest version, but I think it would be worth trying the demo out though.

[BBFG#]

It has issues.
viewtopic.php?t=609583&start=225

Granted that thread is derailed into everything but Bitwig now. But you can still filter through and find problems they've yet to address.
Right now, I'd suggest not.

[Trancit]

If you are looking for Performance, the worst thing you can do is working with most of their native devices...

As especially everything "Grid" based like Polymer, all "+" devices... basically everything a bit more new is at least 4 times oversampled (without the ability to change that!) they are quite CPU hogs and can easily take up to 10 times (Compressor + and Over) more CPU than many suitable 3rd party plugins...

Additionally Bitwig is an extreme RAM hog on my machine... little projects with 40-50 plugins already take 12-15 gigs in Bitwig with being at 2-3 gigs in Reaper or FL Studio...

[dirtydenver]

Huh - interesting. Bitwig is the best performing DAW I've used on my M1 Mac. So incredibly snappy & smooth, even with large projects. Comparatively, Cubase / Logic / etc are all very resource heavy & feel laggy.

You mentioned you're using an old computer. What are your specs?

[Ah_Dziz]

I was using an older 3930 hexcore based windows 7 system for years and years with 128 GB of ram. I have a newer laptop based on an i5 and a newer desktop with an i7 both running windows 10. I've tried out the versions of Bitwig I already own on both of the new systems and they still have relatively weak performance. I did demo v5 at one point and I did seem to notice slightly better performance, but I wasn't looking for that at the moment. I've got a little lull in work and it's discount software season so I'm actually looking into grabbing and setting up some new stuff right now. I'm never going to try and do the things I do in cubase in bitwig but I would love to be able to have a project that takes 25% of my CPU in cubase run in bitwig at all.

Regarding the onboard bitwig devices, I've found they are more efficient than 3rd party stuff (in V3 at least) to the point that I use them almost exclusively when I go to Bitwig. Anyway I'll probably go ahead and get the update. Knowing that they've out some effort at least into performance is good enough for my uses.

Thanks
JJ

[Trancit]

...
Regarding the onboard bitwig devices, I've found they are more efficient than 3rd party stuff (in V3 at least) to the point that I use them almost exclusively when I go to Bitwig. Anyway I'll probably go ahead and get the update. Knowing that they've out some effort at least into performance is good enough for my uses.

Thanks
JJ

For the old devices that´s true...
I think it started with Polymer/Saturator which take at least 4 times more CPU than comparable VSTs or eg Abletons devices...
Other CPU hogs are especially Over and all "+" devices ... this of course all started way later than V3...

[a9k1tp]

Latest Bitwig runs like any other DAW on my 14600k.