Bitwig 6

[Dionysos]

Editing multiple clips at once is so much better now, it's kind of mind-blowing. I found the old multi-clip editor experience really clunky, and now it's super powerful, easy to engage, and you can display all the things at once, it's really fun.

See here from 3:16 onwards:



I'm really unreasonably happy about that zoomable drum editor!

[tumface]

I am not liking the gradient on clips to indicate where the loop points are. It's hard for me to read, especially once you have a bunch of clips vertically next to each other. I think it's because it requires scanning left and right along the clip for a moment to judge where the breakpoint in the gradient is. I sent them feedback on this. So far, this is the only thing I don't like about the beta, and I'm incredibly picky.

[tumface]

Editing multiple clips at once is so much better now, it's kind of mind-blowing. I found the old multi-clip editor experience really clunky, and now it's super powerful, easy to engage, and you can display all the things at once, it's really fun.

This was, surprisingly, partially possible in Bitwig for a while now. You had to make sure the detail editor was in "track" mode instead of "clip" mode, but you could edit things together side-by-side like that, with some limitations.

New stuff in 6 is that you can also do it in "clip" view now, and it can also now handle overlapped audio and MIDI clips at the same time. (Previously, could only do a single type of clip at once, I think.) Great stuff.

[liquidsound]

Just realised that an automation clip in the 'clip' view, can also affect the arrangement playback...

Makes perfect sense but it hadn't clicked before. So now you can play an arrangement, but also sequence live 'automation' alongside (or just have clip-based repeats without arrangement for automation).

Game Changer !

Next Actions also work for Automation Clips in the Launcher

That’s really cool!

[coroknight]

Clearly I meant one less instruction set within the domain of applicability. Obviously AVX2 doesn't apply to ARM processors. Great point! Always fun when people think litigating language is a good argument.

I'm not trying to argue. I'm just noting that the devs have to support multiple instruction sets in any case. I highly doubt they write SIMD intrinsics or assembly manually for each one, so dropping SSE4 wouldn't significantly simplify their work. You can even test SSE4 code on an AVX2 machine, it's testing ARM Neon requires separate hardware.

It does simplify it somewhat though. But more importantly there are different engineering tradeoffs depending on which instruction sets you support. AVX2 being able to process 2x as much data in a single instruction is not small, and it makes a difference when you tell your engineering team they can rely on that when considering features, algorithms, etc.

[questionaire]

And amazingly stable i have until yet to find something not working right! Still scratched only the surface of new features ofcourse

[fwsuperhero]

Do you know if there is a trick how to allign two points in automatization to have same value?
I was really hoping we get that horizontal line that aligns to other points when we move automatization point vertically.

[monolithx]

Zero improvements for live performances, zero fixes... . Don't we have enough DAWs for editing? Let's see how scaling works with MPE, at least. As Scaler don't support it.

[mholloway]

Zero improvements for live performances, zero fixes... . Don't we have enough DAWs for editing? Let's see how scaling works with MPE, at least. As Scaler don't support it.

Die mad, I guess. This is an amazing update.

[machinesworking]

Great update, only slightly disappointed that most of the editing improvements are about the sub-windows and not the main arrangement window. Lots of improvements to the way you initially create an arrangement but only grid lines and key signatures for the arranger. The other elephant, the key signature functionality is great, but only 23 scales and no customizable scales is so not like Bitwig??? Hopefully that ability comes in the future?

[pdxindy]

Hopefully they will enable multiple automation lanes for the same parameter, and the ability to specify if an automation clip is absolute (default), additive, or multiplicative... in a future update. It would be great to have overlapping/aggregating automation clips for a single parameter on the arranger view, for more ambient/longer pieces.

I'm fine using Macro Knobs for doing that...

[pdxindy]

Editing multiple clips at once is so much better now, it's kind of mind-blowing. I found the old multi-clip editor experience really clunky, and now it's super powerful, easy to engage, and you can display all the things at once, it's really fun.

Yeah... it's a huge improvement!

[anoise]

This is the most radical GUI overhaul they did since version 2. Feels snappier, like a different and better DAW. Not a fan of the gradient on the clips for the loop points and the thin blue lines in the piano roll, but other than that, awesome update.

[koalaboy]

The only disappointment I have with the UI .. okay, three disappointments (Spanish Inquisition):
1) Not able to customise the main toolbar (minimal customisation/no themes overall) - I'd love to move the transport controls to the centre - or the bottom, for example.
2) Not able to right-click 'set default' any of the smart collections (maybe I missed something there).
3) Still not able to multi-select VSTs and toggle the 'Stretch Plugin...' option.

[pdxindy]

Zero improvements for live performances, zero fixes...

I imagine being able to trigger automation clips separately from note clips will be useful for live performance.

Also Next Actions work with Automation Clips and automation points can have spread values so they randomize for each loop. Those both sound useful for live performance as well.