Bitwig Studio 6 released

[TheMaestro]

https://www.bitwig.com/stories/on-anoth ... t-now-416/

Bitwig has announced the release of Bitwig Studio 6, a version update for its digital audio workstation focusing on core sequencing functions, automation management, and project-wide musical scale integration. The update introduces several new clip behaviors and editing tools designed to streamline the arrangement and sound design workflow across macOS, Windows, and Linux.

[oobesan]

Reports that it’s a CPU resource hog. Can anyone confirm?

[wadamek]

Switching from Ableton is becoming more and more tempting...

[pdxindy]

Reports that it’s a CPU resource hog. Can anyone confirm?

Seems the same as v5 to me...

[coroknight]

It’s not a CPU hog, some of the built-in devices are oversampled and use more CPU than people expect. A good example of this is the “Over” device.

But the DAW itself is not a cpu hog

[Yorrrrrr]

Switching from Ableton is becoming more and more tempting...

I did. Couldn't be any happier. I consider Bitwig an upgrade.

[teilo]

One of the best updates in a long time. They focused an entire release mostly on improving the workflow and editing, especially MIDI editing.

Let's hope in future development cycles they split their time between new wiz-bang and improving what already exists.

[pdxindy]

One of the best updates in a long time. They focused an entire release mostly on improving the workflow and editing, especially MIDI editing.

Yeah, I'd say the most significant update since V2 when they switched to the current modulation system!

Automation editing was a weakness before, but now it's a strength.

And there are more little, but useful improvements than one could even list!

[Jac459]

Hi, I have a strange issue with Bitwig 6 (or myself, I may f....up something without knowing).

So I am trying to record the midi notes that are output by another track (with many midi effects).
My last midi effect is a note echo in the track A. I set the track B midi input to be track A/note echo device. I armed the track B, hit the record button, monitor button is on on track B. but while the block is being created, ... no notes inside. I am getting crazy.
Am I doing something wrong?

[pdxindy]

Hi, I have a strange issue with Bitwig 6 (or myself, I may f....up something without knowing).

So I am trying to record the midi notes that are output by another track (with many midi effects).
My last midi effect is a note echo in the track A. I set the track B midi input to be track A/note echo device. I armed the track B, hit the record button, monitor button is on on track B. but while the block is being created, ... no notes inside. I am getting crazy.
Am I doing something wrong?

I just created a new project, made a midi clip with 2 long notes, added an Echo device, then set a second track to receive from the Echo device on the first track and it recorded all the notes generated by Echo as expected.

[aMUSEd]

One of the best updates in a long time. They focused an entire release mostly on improving the workflow and editing, especially MIDI editing.

Yeah, I'd say the most significant update since V2 when they switched to the current modulation system!

Automation editing was a weakness before, but now it's a strength.

And there are more little, but useful improvements than one could even list!

Yes I think automation has changed from being a composition support tool to a composition tool in its own right.

[qtheerearranger]

theres some weird stuff with the clip automation selection when trying to select all the nodes - if you have a node on the first or last point of the grid in the clip its very hard to select them as if you go just a tad outside the clip all the previously selected automation points unselect instantly. I was wondering if other people have had this issue.

in regards to automation clips: its truly overall the best feature I think in any daw ive seen - and I would imagine it would of vastly increased my sound design experimentation techniques during my first few years of music production. I think its a great tool for both beginners and experts and thats pretty awesome. The issue is - I have no idea why every daw wouldn't want to copy this. it may not be something they can do in the next year or even two but I guarantee most developers think this is a really good idea.

[stamp]

Nvm

[pdxindy]

theres some weird stuff with the clip automation selection when trying to select all the nodes - if you have a node on the first or last point of the grid in the clip its very hard to select them as if you go just a tad outside the clip all the previously selected automation points unselect instantly. I was wondering if other people have had this issue.

I can confirm the same result. I reported it as a possible bug.

You can put the editor into clip mode, then you can freely select points including the edge.

[Sakke80]

Reports that it’s a CPU resource hog. Can anyone confirm?

Yes. It uses about 30-50% more cpu than Live 12. Even one instance of Serum 2 with a complex patch is unusable, but in Live 12 cpu is at about 25-40%.

Win 11, i9 12900k, NVMe, 64 GB RAM, Zen Go with 1024 buffer and 48 kHz.