3.2 (Beta 1) is OUT!!!

[Redukt]

And to think I've upgrade plans paid up to end of 2021 AND I've just sold Live 10 Suite...

Are you kidding?

No. But I already found another copy of Suite and lost ~5EUR on the whole back & forth deal.

While I agree with you that Bitwig updates get worse and worse I could never go back to Live, honestly.
After being disappointed with 3.2 yesterday, I installed the Live 10 demo and it just feels so clunky and non-intuitive compared to Bitwig. No modulators, no in-clip editing, zoom via bar on top of the screen,...

I still have an update license ready to redeem that I bought in early 2019...until then I can more than comfortably work with 3.0

Why did you renew your licenses until the end of 2021, though? That doesn't really make sense considering their license model. The whole point is to only update when you are interested in the features of a new version - otherwise it's just a blank check for the devs...

[FlareStar]

Just bought Bitwig Studio. I love the colorful GUI in Bitwig compared to bleak/boring grey of Ableton Live. Good job Bitwig team!

P.S. Saturator is top-notch!

[antic604]

Why did you renew your licenses until the end of 2021, though? That doesn't really make sense considering their license model. The whole point is to only update when you are interested in the features of a new version - otherwise it's just a blank check for the devs...

That was the whole point. I was ready to blindly trust them and wanted to support them. That's over now.

[fwsuperhero]

I would love to see retrigger on evey step (like 1x,2x,4x,8x..) in the updated arpegiator too. It would make it complete imho. Like some drum machines have.

Great update, thanks.

[anoise]

The rainbow effect doesn't bother me in the EQ's but I agree, it should be only optional. EQ+ is very nice but does it supersede EQ-5? If so why keep EQ-5, is it more CPU efficient, why should I use it instead of EQ+? Too many EQ devices.
This beta is very buggy indeed. It can't even play projects without the midi cutting out all the time.

[antic604]

I would love to see retrigger on evey step (like 1x,2x,4x,8x..) in the updated arpegiator too. It would make it complete imho. Like some drum machines have.

Great update, thanks.

You can use Note Echo for that and automate its on/off for certain notes.

[SmajjL]

I guess if they updated everything into EQ-5 that could break compatibility with old projects? and EQ+ is my new fav EQ! and have 8 bands, can't call it EQ-5 then
I manage to see the color as a practical and i can make use of that info, like coloring my tracks or what have we.
And last time i looked, Linux have no Fabfilter, so
So keeping EQ-5 will make sure your old hits still work (is my guess).

[xbitz]

^^^ fabfilter eq instances see each other (and the collided frequencies), this is the only feature what I miss

https://soundbytesmag.net/review-pro-q- ... ab-filter/

but that note-off modulator is brilliant

[SLiC]

And to think I've upgrade plans paid up to end of 2021 AND I've just sold Live 10 Suite...

Are you kidding?

No. But I already found another copy of Suite and lost ~5EUR on the whole back & forth deal.

While I agree with you that Bitwig updates get worse and worse I could never go back to Live, honestly.
After being disappointed with 3.2 yesterday, I installed the Live 10 demo and it just feels so clunky and non-intuitive compared to Bitwig. No modulators, no in-clip editing, zoom via bar on top of the screen,...

I still have an update license ready to redeem that I bought in early 2019...until then I can more than comfortably work with 3.0

Why did you renew your licenses until the end of 2021, though? That doesn't really make sense considering their license model. The whole point is to only update when you are interested in the features of a new version - otherwise it's just a blank check for the devs...

I did exactly the same, I have 9 suite but demoted 10 to see if it was worth upgrading with the 30% off deal...thought I would use the 60 day demo first but deleted it after 10 days...for the way I work (and party due to the browser) there is no going back. Bitwig was already vastly superior to Live in many ways that matter to me, adding more features doesn’t detract from that and upgrades are optional. I’ll judge the 3.2 beta when it’s out of beta, but for me it’s better than the 3.1 incremental upgrade and both had some really nice little workflow upgrades even if you didn’t want the new rack devices or grid modules. As a side note I consider all this stuff as free as As far as I am concerned all I paid for was an upgrade to V3...

[anoise]

Another idea is too keep only 1 device, the EQ+, and add an option to "downgrade" it to EQ-5 or EQ-2, like how you can upgrade EQ-2 and EQ-5 to EQ+. For old project it downgrades automatically.

[SB-SIX]

I know. Bugs are expected. But I'm starting to hate where they're going (3rd EQ, instead of adding those things to perfectly capable EQ-5?! We have now FOUR EQs. That's gotta be a record). Instead of fixing existing issues - often simple things - they're adding more clutter...

Agreed that it could use some cleanup. Make some devices legacy seems like a good plan. I’m always struggling to find the correct lfo for instance, where one good versatile lfo would be preferable. But it does not feel like something to ditch bitwig for. It seems they included a little bit of everything (new devices, workflow improvements, etc). In the next round (or maybe even in this beta round) they could make eq5 legacy.

[SLiC]

Given bitwig can already hide redundant VSTs such as 32 bit or VST2 (by selection in options) I would think it would be very easy to add a tick box to hide legacy devices in browser.

[anoise]

...add a tick box to hide legacy devices in browser.

It is there already, in the right click menu for the browser: "Include Legacy Devices".

[dreamstate42]

Considering how (seemingly?) long it has been since 3.1, I have to admit that I'm a little bit disappointed about 3.2. Don't get me wrong, the new EQ+ and Saturator are fantastic, but this update kind of reinforced something that has been gnawing at me in the back of my mind for some time about Bitwig: It seems they prioritise "adding stuff" over "fixing stuff" (fixing not necessarily meaning bugs, but also inconsistencies and so on).
The "fear" in the back of my mind was always this little voice saying "Mh, the big benefit of paying for 12 months of updates is that it kind of forces Bitwig to keep innovating, but doesn't this also kind of tip the scales for them towards prioritising new features over sitting down and consolidating what they already have? An update plan doesn't really invite saying 'let's sit down for a few months and make everything consistent', because that doesn't really sell well as a "feature".

Again, that's not meant as "doom saying", more an existing concern from someone who is jumping between DAWs way too frequently, and loves the ideas Bitwig has (common Bitwig, you're my biggest hope for staying with a DAW for good, don't screw that up! ).

[antic604]

...add a tick box to hide legacy devices in browser.

It is there already, in the right click menu for the browser: "Include Legacy Devices".

That's different:
1) It reveals them, not hides
2) It's only for the pre-2.0 modulation devices: LFO-Mod, Note-Mod, etc.