Why you left Bitwig?

[EnGee]

Although I think they feel good when they shit on such unknown monster and there is no response!

Anyway, back to Bitwig! The thing that I see very underrated are the synths! I know the Grid got all the attention (deservingly) but the other smaller synths are really excellent! The problem there is no enough good presets for them, but when I begin to make my own, they are really very good synths!

Your car might be one of the sports in the bird Olympics

I find them so... even the humble Polysynth has grown on me. I kinda dismissed it at first.

My car is not pretty! It is an old 2008 black Auris (Corolla)! So, I'm sure they hate it

Yes, me too! At first I just played little and then ignored it. But then, when I was in Linux (not many native choices there), I started to play with Polysynth and FM4 (I already like a lot Polymer and Phase4) and begin to like them a lot! Yes, Operator in Live might sound sharper than FM4, but giving it the chance, well, it sounds nice Polysynth I actually like more than Analog in Live. It is great for bread and butter sounds

Anyway, another reason that I don't leave Bitwig is that all the DAW plus all the devices look great in scaled Windows (and Mac) on my 4k 27" monitor. Some criticized me for getting such monitor, but I love it and it is perfect for my space and need. Bitwig, Cubase and Live look great whatever scaling I'm into. These DAWs are very inviting and almost problems free for me (and my setup/plugins) except some minor GUI negatives here and there that I can live with

[fuziohm]

btw. open<>closing/focusing plugins(groups) can be key assigned

I like it in BWS (AFAIK AL also knows it just AL blocks the macroed plugin params) ... so can live with nesting

How did you make this work?? is this a controller script?? i already serachied for this feature because i was so used to it on reaper.
Thanks dude

[fuziohm]

btw. open<>closing/focusing plugins(groups) can be key assigned

I like it in BWS (AFAIK AL also knows it just AL blocks the macroed plugin params) ... so can live with nesting

[fjolle]

I've used Bitwig for a while but I run into performance issues. Both Ableton Live and Logic Pro handles my sessions just fine. I record a lot of audio from my hardware but then arrange and mix my things in the DAW. I switched from Live to Bitwig because I had serious issues with Live crashing often, Bitwig hasn't crash at all on me. But I constantly run into massive performance issues to the point where everything starts crackling and slowing down. I'm running with the same buffer settings and quality settings as I do in the other DAWs. I did some home grown performance tests and found that Logic Pro can handle about 20-30% larger sessions on my MBP.

There's a few other things, such as a lacking Console 1 integration (not really Bitwigs fault I suppose), but I can live with that. I have a much harder time living with the fact that Logic Pro can run approximately 30% more instances of the same plugins on my MBP (6 core i7, it's not that old).

I don't know. I feel more creative in Live and Bitwig, but Live's constant crashing and Bitwig's serious performance issues leaves me going back to Logic Pro.

I especially noticed that some plugins barely work in Bitwig (such as UVI Relayer), that other GUI's are severely lagging etc. When Softube upgraded their stuff to VST3, the VST3 versions were taking 10-20% more CPU than their VST2 counterpart, to the surprise of both Bitwig and Softube who I spent a lot of time communicated with. I first contacted Bitwig about this sluggishness and what they said was "Plugins that tend to be slower than others might show this earlier in Bitwig Studio than in Ableton Live as Bitwig Studio is a bit more demanding and also running at 60 frames per second, compared to other hosts that most often use lower frame rates.".

I'm sad because the workflow in Bitwig is fantastic for me, but I constantly bang my head on performance issues.

If anyone has stumbled into this as well and found solutions, I'd be happy to hear about it before I let my license go.

[moss]

I've used Bitwig for a while but I run into performance issues. Both Ableton Live and Logic Pro handles my sessions just fine. I record a lot of audio from my hardware but then arrange and mix my things in the DAW. I switched from Live to Bitwig because I had serious issues with Live crashing often, Bitwig hasn't crash at all on me. But I constantly run into massive performance issues to the point where everything starts crackling and slowing down. I'm running with the same buffer settings and quality settings as I do in the other DAWs. I did some home grown performance tests and found that Logic Pro can handle about 20-30% larger sessions on my MBP.

There's a few other things, such as a lacking Console 1 integration (not really Bitwigs fault I suppose), but I can live with that. I have a much harder time living with the fact that Logic Pro can run approximately 30% more instances of the same plugins on my MBP (6 core i7, it's not that old).

I don't know. I feel more creative in Live and Bitwig, but Live's constant crashing and Bitwig's serious performance issues leaves me going back to Logic Pro.

I especially noticed that some plugins barely work in Bitwig (such as UVI Relayer), that other GUI's are severely lagging etc. When Softube upgraded their stuff to VST3, the VST3 versions were taking 10-20% more CPU than their VST2 counterpart, to the surprise of both Bitwig and Softube who I spent a lot of time communicated with. I first contacted Bitwig about this sluggishness and what they said was "Plugins that tend to be slower than others might show this earlier in Bitwig Studio than in Ableton Live as Bitwig Studio is a bit more demanding and also running at 60 frames per second, compared to other hosts that most often use lower frame rates.".

I'm sad because the workflow in Bitwig is fantastic for me, but I constantly bang my head on performance issues.

If anyone has stumbled into this as well and found solutions, I'd be happy to hear about it before I let my license go.

Plugins require more performance in Bitwig because at the default setting they all run in their own process, which means that the DAW keeps on running when a plugin crashes. You have different options from totally safe (all plugins in their own process) to all running in the same process as Bitwig with no safety at all. The later should give you the same performance as in Ableton. My current setting is "Together", which means all plugins will die if one crashes but Bitwig keeps running.

[fjolle]

Plugins require more performance in Bitwig because at the default setting they all run in their own process, which means that the DAW keeps on running when a plugin crashes. You have different options from totally safe (all plugins in their own process) to all running in the same process as Bitwig with no safety at all. The later should give you the same performance as in Ableton. My current setting is "Together", which means all plugins will die if one crashes but Bitwig keeps running.

I'm running it in the most unsafe mode currently since I otherwise couldn't even export my latest work (earlier I was using "Together"). It does not give the same performance as Ableton for me, unfortunately. I just repeated my basic test now, which was: short midi track, Omnisphere, bunch of plugins, let the record spin and then keep replicating the track (+ the midi event) until it blows up. Ableton handled about 20% more tracks for me.

[Influx808]

I left ableton for bitwig and I thought the modulation capabilities were really cool but am I the only one here that believes ableton midi function are quicker ?

[machinesworking]

I did some home grown performance tests and found that Logic Pro can handle about 20-30% larger sessions on my MBP.

Yes, that's normal. Logic, DP11, Reaper all have much better CPU handling than Live or Bitwig.
It has to do with the real time uninterrupted audio engine design of Bitwig and Live, they simply don't hiccup when altering things while the sequence is running as often as Logic etc. You and any Logic user is familiar with overload message which half the time is due to you doing something like instantiating an instrument while the sequence is running. The increase in performance is mostly due to track buffering methods that Logic, DP etc. use to give extra time to functions of the sequence that are not being interacted with, it pre- buffers or renders the non record enabled tracks saving massive amounts of CPU. You can test this yourself, just record arm all tracks in Logic VS live or Bitwig. All of a sudden Logic is the piggy DAW!

Moss pointed out the one area where Bitwig can chew up more CPU, but in general I've found it to be the opposite. I have an older Mac Pro with 12 core 3.33 Xeon's but they get hit much harder by Live than Bitwig, probably because Bitwig is slightly better at allocating cores to plug ins etc. I have every plug in in it's own process in Bitwig and still get slightly better performance out of it than Live.

[Passing Bye]

I don't know. I feel more creative in Live and Bitwig, but Live's constant crashing and Bitwig's serious performance issues leaves me going back to Logic Pro.

Every DAW have shortcomings, even Logic, visit this channel, you will wish to ditch Logic again


there was long standing latent automation bug that was finally fixed in newest version, after been broken for whole Logic life, there's more stuff that isn't still up to specs...

You need to pick lesser evil or combine stuff, like compose in one DAW, arrange and mix in another or third or find the way to do all that in one, they are all flawed.

[Passing Bye]

probably because Bitwig is slightly better at allocating cores to plug ins etc.

Yes, it handles multi-core stuff like an champ, especially U-He stuff that I mainly use and that really are multi-core capable.

[machinesworking]

probably because Bitwig is slightly better at allocating cores to plug ins etc.

Yes, it handles multi-core stuff like an champ, especially U-He stuff that I mainly use and that really are multi-core capable.

Yep, Bitwig is better than any DAW in most stress tests with Diva for instance, with or without multicore on in Diva.

I'm super curious about how Bitwig works on the M1 and upcoming Apple Silicon chips?! It might work even better depending on how it interacted with x86 multithreading. Not that you'll be able to tell really considering how much faster they are anyway, but it mostly seems like faster in single core... hard to say? we're dealing with essentially a 4 core with 4 "helper" cores rather than an 8 core with the M1.

[EnGee]

It works great on the M1 When I turn on my M1 Air, mostly I use Bitwig. Even I can browse u-he presets from my Arturia keylab mk2 which I can't on Windows!
Still, on my 5800x CPU on Windows, it has slightly a better CPU preformance, but I use few tracks (10 average), so it is like my Corolla! It just works, no main problems at all! Sometimes it gets boring from stability

But I agree with Passing Bye! There is no prefect DAW overall, just pick the one that works for you the best

[Passing Bye]

Yeah, you know what it is, black and orange! (sorry, being drinking, got off from work, happy weeknd and all that)

[Passing Bye]

Yep, Bitwig is better than any DAW in most stress tests with Diva for instance, with or without multicore on in Diva.

Yeah, I can't believe how amazing Diva runs in Bitwig!

Bitwig is far from perfect, but dunno, anyone that is reading, if you have fun, if you can get stuff done, stick with it, it's not worse than any DAW out there, it's not better either, it is what it is, true cat, quirky, but lovable.

[machinesworking]

But I agree with Passing Bye! There is no prefect DAW overall, just pick the one that works for you the best

or the three

Mostly I'm interested in playing with Jitter in Live.

I'm not sure I can ever go back to dragging the MIDI subwindow around all the time, and Bitwig has the best implementation of native Apple silicon VS x86 plug ins of any DAW.

I'll always use DP for bigger projects for the reasons mentioned about Logic, plus just better handling of those sorts of things.