Bitwig 6

[qtheerearranger]

can someone let me know if we've lost the ability to edit multiple midi clips at the same time? I can't select the pen icon for more then one tracks at once for multi track/layer editing. I can easily switch between one track and the other but I can't edit both at once?

I thought it was always the case you had to select the layer/track you wanted to change, and only viewed all notes from multiple tracks. How would it know which you wanted add to otherwise?

In the past you could select the pen on the layer of more then one track iirc but im not a bitwig daily user by any means and could be wrong. But I'm almost positive it worked very similar to how s1 did it.

edit: wasn't using drum editor view for sure

[stamp]

The automation update alone Is worth the upgrade for me...
Step input

[SLiC]

does not run on my trusted machine saying:

A CPU which supports the AVX2 instruction set is required to run Bitwig Studio (since version 6.0)

that's not good.

Have they updated the minimum spec for Bitwig 6?

[tumface]

Fantastic update. So many issues fixed.

[Stan Navi]

Did they add midi comping? Can't find info.

[Dopplgngr]

Awesome update, new editing and automation very inspiring for composing - and clip alias with automators get songs done faster.

Thanks!!

[DashOfLime]

does not run on my trusted machine saying:

A CPU which supports the AVX2 instruction set is required to run Bitwig Studio (since version 6.0)

that's not good.

AVX2 shipped 2 years before you became a member here.

[foosnark]

Literally zero of the changes in the entire changelog are at all interesting to me this time.

I record everything live. I would say I never use clips, except I did once this year (for a very simple MIDI loop with wonky timing). I only use the timeline when mastering, and the automation was absolutely adequate for my purposes before.

Maybe the new look will be nice, if I want to really reach for something positive here.

This is not a complaint, but an observation. I am mostly happy with how Bitwig 5 works. There are a couple of features I'd like to have, but lacking them hasn't stopped me before and won't stop me now. And I'm happy for other people who wanted this stuff.

[Dionysos]

This is a seriously amazing update.

Alias clips address my biggest Bitwig pain point, and the implementation seems slick.

Piano roll interactions are MUCH nicer! The automatic time selection around selected notes is now visually much more subtle (it actually looks… pretty?), AND you can't accidentally drag it at note boundaries anymore, significantly reducing the fiddliness of working with notes.

Speaking of fiddliness, they actually got rid of the behaviour where dragging over the bottom half of the arranger track makes a time selection instead of moving clips. I always found that fiddly (yes, powerful, but ultimately fiddly). I wonder if that will cause a lot community complaints. Clip headers are much less tall now, didn't someone recently complain about that here?

I also love that the drum editor can now be vertically zoomed, making it much more usable and step-sequencer-like.

Did they add midi comping? Can't find info.

You'd have found it if they did, so they didn't.

[SLiC]

Yup- we are still waiting for Midi comping and ARA...Obviously it may never come, its not like they promised it.

[tumface]

The fundamental arrangement view changes are the sort of thing a development team would want to do before adding MIDI comping, since otherwise they'd probably just have to redo the comping implementation after changing the arranger. With the addition of automation clips and other nice things, I'd we might get MIDI comping in a 6.1 or 6.2 release or something like that. For the time being, I've just been adding child tracks and spreading MIDI clips across them. MIDI comping is good, but I've always found it slightly less useful than audio comping, because it's so much easier to make fixes to MIDI clips directly in the data, and to merge them together, unlike audio clips.

[tumface]

On another note, I'm glad they didn't spend energy on other-people's-content-modification technologies like AI stem splitting and vocal pitch editing of pre-mixed vocals. Those things just aren't my cup of tea. I realize other people often ask for them, but it's nice to get things my way for once.

[SLiC]

... because it's so much easier to make fixes to MIDI clips directly in the data, and to merge them together, unlike audio clips.

It's a bit more of a faf with MPE- I prefer to comp in MPE performances from my Osmose and only tweak if absolutely needed, better to take the3 first half of one part, second half of another etc and keep the live feel (like audio) but you can work around it, but you don't need to in other DAWS.

[tumface]

It's a bit more of a faf with MPE- I prefer to comp in MPE performances from my Osmose and only tweak if absolutely needed, better to take the3 first half of one part, second half of another etc and keep the live feel (like audio) but you can work around it, but you don't need to in other DAWS.

That totally makes sense. I didn't even think of that. Good point.

[jules99]

From

https://downloads.bitwig.com/6.0%20Beta ... eta-1.html

When you open a project made in a previous version, the original project file is automatically backed up.

f**k YES, every DAW should do this!