Why you left Bitwig?

[THE INTRANCER]

People buy Bitwig to make music with, not endlessly configure its GUI. Studio One is overpriced at $400 when Reaper offers much the same for $60, one could argue. At $399 Bitwig is priced competitively against it's main rival Live, which retails for $749.

£111.00
$169.49 USD -

Is what it cost to buy Studio One 2 Pro and then upgraded to version 3.0, 7 months later on it's release, for around £120. Atm $400 USD is £289.
Saving around £60.. If I had waited I could have saved more during black friday as I did with Studio One 2.

You can try and compare S1-Pro to Reaper in terms of value, but that's a topic for another thread, but Reaper for me just didn't tick the boxes to put it politely and just didn't cut it feature, development and usability wise when I had switched from Reason 7. I already had Reaktor 5 as well, so a modular experience could be had in addition to Rewire with Reason to Studio One.

Abelton is undoubtedly over-priced if you are comparing the Suite version, but the Standard version of Live is still comparable on price to Bitwig Studio.

There are many reasons why one would choose an all round DAW over one that focuses on a particular area. One is that it gives you bigger table and avenues to go down regardless of who you are as a composer. Ofcourse if you have an outboard CV Modular Instrument setup then obviously Bitwig Studio would be the better choice, although I'd expect other modular software having some ground there.

Being able to customise the DAW is important for a multitude of reasons. Bitwig Studio from the very first version that came out felt very restrictive and still does today.

Abelton has a wide range of controllers, so it's naturally the one that feels better suited than Bitwig for customers.

[pdxindy]

Being able to customise the DAW is important for a multitude of reasons. Bitwig Studio from the very first version that came out felt very restrictive and still does today.

There is not one reason it is important to me to customize a DAW. Bitwig works fine for me. Doesn't feel restrictive at all. I feel the same about Logic and Live when I use(d) them.

I would rather the Bitwig devs not waste one minute of time on something so meaningless.

[THE INTRANCER]

Being able to customise the DAW is important for a multitude of reasons. Bitwig Studio from the very first version that came out felt very restrictive and still does today.

There is not one reason it is important to me to customize a DAW. Bitwig works fine for me. Doesn't feel restrictive at all. I feel the same about Logic and Live when I use(d) them.

I would rather the Bitwig devs not waste one minute of time on something so meaningless.

It's restrictive for the reasons I gave in my previous post, which was what I meant. You need to pay for bugs to be fixed that they carry over to new versions, so I can understand why you wouldn't want them to spend time on GUI customisation, but whether you like it or not, how the GUI looks affects your mood and music and that of your environment in which you use it in. Ofcourse you can always use a third party utility to change how the colours on screen look, at least on Windows.

[pdxindy]

It's restrictive for the reasons I gave in my previous post, which was what I meant. You need to pay for bugs to be fixed that they carry over to new versions, so I can understand why you wouldn't want them to spend time on GUI customisation, but whether you like it or not, how the GUI looks affects your mood and music and that of your environment in which you use it in. Ofcourse you can always use a third party utility to change how the colours on screen look, at least on Windows.

Bitwig is by far the most stable DAW I have used. I am not concerned about bugs at all, just like I'm not concerned about GUI customization.

Perhaps you might speak for yourself and not for others.

[EnGee]

You don't pay only for bugs! There are new features as well. Although to be honest, I would pay for a stable near bugs free maintenance rather than new features!

There are still things I'm missing from Cubase like midi review inside the browser, but I gave up! Bitwig and Live are not interested at all in implementing that feature! There are other things like good markers system and other things that made Bitwig not the only DAW I use. But at least I cut it to only three DAWs instead of 5

[apoclypse]

It's restrictive for the reasons I gave in my previous post, which was what I meant. You need to pay for bugs to be fixed that they carry over to new versions, so I can understand why you wouldn't want them to spend time on GUI customisation, but whether you like it or not, how the GUI looks affects your mood and music and that of your environment in which you use it in. Ofcourse you can always use a third party utility to change how the colours on screen look, at least on Windows.

Bitwig is by far the most stable DAW I have used. I am not concerned about bugs at all, just like I'm not concerned about GUI customization.

Perhaps you might speak for yourself and not for others.

100% agree. I like Bitwigs interface the way it is. I’d rather they concentrate on enhancing the workflow than GUI customization. They have enough problems just keeping the GUI performant, I don’t need them to futz around with it to appease people who rather talk about UI customization than make music. Go use Reaper if that’s your thing imo.

[antic604]

...Although to be honest, I would pay for a stable near bugs free maintenance rather than new features!

What bugs are you talking about exactly? Frankly, I'm not aware of any ACTUAL bugs but perhaps it's a matter of workflow and feature set that I'm using?

[PieBerger]

...Although to be honest, I would pay for a stable near bugs free maintenance rather than new features!

What bugs are you talking about exactly? Frankly, I'm not aware of any ACTUAL bugs but perhaps it's a matter of workflow and feature set that I'm using?

The "bug" is that you can't tweak the GUI

[EnGee]

...Although to be honest, I would pay for a stable near bugs free maintenance rather than new features!

What bugs are you talking about exactly? Frankly, I'm not aware of any ACTUAL bugs but perhaps it's a matter of workflow and feature set that I'm using?

Just saying man! I mean that I prefer a stable software than new features if I must choose between the two. It is not unheard that a software company ignore bugs and keep adding new features!

[antic604]

Just saying man! I mean that I prefer a stable software than new features if I must choose between the two. It is not unheard that a software company ignore bugs and keep adding new features!

Ok, it sounds like you meant there are serious bugs remaining in Bitwig that aren't being fixed. It's possible there are, it's just I've not encountered them in my workflow - hence the question.

[Tj Shredder]

In general thats how Bitwig advances. You never pay for fixing bugs. Even if your plan ran out you get bug fixes for free. The new versions add features and are released after the last version is as stable as it can be…
I guess its expected for complex software to find some bugs after release, as there are so many different ways to use it…

[fieldframe]

If I may ask, what was the bug?

When a plugin window is open (and focussed) the mouse pointer icon changes to the ones that would be shown if the plugin wasn't there.

https://www.dropbox.com/s/whi8nnx3nav00 ... 1.mov?dl=0

Happens with all plugins. I thought that the update with M1 support could maybe fix it, but it didn't...
I know it's kinda minor, but it bugs me.

This bug (and reading that they have no plans to fix it) has actually put a stop to my buying Bitwig on the current crossgrade sale. I've really enjoyed using the demo, but this is the kind of thing that's going to keep me on Ableton until Bitwig devotes a few more resources to cross-platform spit and polish.

[machinesworking]

If I may ask, what was the bug?

When a plugin window is open (and focussed) the mouse pointer icon changes to the ones that would be shown if the plugin wasn't there.

https://www.dropbox.com/s/whi8nnx3nav00 ... 1.mov?dl=0

Happens with all plugins. I thought that the update with M1 support could maybe fix it, but it didn't...
I know it's kinda minor, but it bugs me.

This bug (and reading that they have no plans to fix it) has actually put a stop to my buying Bitwig on the current crossgrade sale. I've really enjoyed using the demo, but this is the kind of thing that's going to keep me on Ableton until Bitwig devotes a few more resources to cross-platform spit and polish.

As someone whose used multiple DAWs over the last couple decades, if this is a crippling bug to you and prevents you from using the DAW, then you're in for a bumpy ride.

[hoxclab]

If I may ask, what was the bug?

When a plugin window is open (and focussed) the mouse pointer icon changes to the ones that would be shown if the plugin wasn't there.

https://www.dropbox.com/s/whi8nnx3nav00 ... 1.mov?dl=0

Happens with all plugins. I thought that the update with M1 support could maybe fix it, but it didn't...
I know it's kinda minor, but it bugs me.

This bug (and reading that they have no plans to fix it) has actually put a stop to my buying Bitwig on the current crossgrade sale. I've really enjoyed using the demo, but this is the kind of thing that's going to keep me on Ableton until Bitwig devotes a few more resources to cross-platform spit and polish.

Your loss. I think it’s one of the best DAWs out and certainly on Linux which is where I’m heading to full time shortly.

[Passing Bye]

If I may ask, what was the bug?

When a plugin window is open (and focussed) the mouse pointer icon changes to the ones that would be shown if the plugin wasn't there.

https://www.dropbox.com/s/whi8nnx3nav00 ... 1.mov?dl=0

Happens with all plugins. I thought that the update with M1 support could maybe fix it, but it didn't...
I know it's kinda minor, but it bugs me.

This bug (and reading that they have no plans to fix it) has actually put a stop to my buying Bitwig on the current crossgrade sale. I've really enjoyed using the demo, but this is the kind of thing that's going to keep me on Ableton until Bitwig devotes a few more resources to cross-platform spit and polish.

...but years of broken automation PDC in Live didn't bother you more than this minor bug some users can't even reproduce (like EnGee on his M1)...