Bitwig 6

[icaria36]

In the beta of BWS 6 there is a bug that I suddenly can't type in the fields, search fields, exact values and so on.

Only by restarting BWS I can type again.

This is a massive bug for killing the workflow.

Are you maybe using a Linux distribution with GNOME i.e. Ubuntu? From which version did you upgrade to 6-beta? If you are using Linux indeed, did you upgrade your OS recently?

I'm asking because I have the same problem since 5.3.8, and even if I have reported it to Bitwig support, they couldn't reproduce it so far. The bug I'm hitting seems to be in an upstream component Bitwig uses, not in Bitwig itself -- see https://discourse.ubuntu.com/t/text-inp ... u=icaria36

[pdxindy]

Have you seen what they have done to gruop tracks?

I think there is a good chance they will revert the group master... with suitable user feedback

What is the group tracks issue?

I haven't noticed a problem, but also haven't tried to do much beyond group tracks to add group FX so far...

In V5, you could have the group track show the tracks visualization, or the group master content. SO if you use the group master to bounce the sub-tracks to audio, it could show on the group track.

In V6, they made the group master a sub-track that can be shown or not inside the group. So if you bounce to audio on the group master, you can only see it by unfolding the group.

[pdxindy]

The great thing about Bitwig was the clarity.
Why mess up everything that was good about Bitwig?

What have they made less clear? I'm not really getting that from the updated UI.

No matter what the change, there are always going to be some people who dislike it. That's just how these things go.

Overall, V6 is being well received by users and I can say for myself, the UI in V6 is significantly improved in a variety of ways.

I like that they returned the the rounded top on clips. It makes it easier to see where one clip ends and the next begins.
I like that they reduced the height of the clip header, making more room for the content.
They got rid of the small/large track height option and now any track can freely be the small or larger size.
In V5, when the tracks were the smallest size, you did not see clip contents at all. Now you do. Yay!

Another improvement to visual clarity of the clips is being able to see the grid lines in the clips.
And the grid lines themselves now have user control over how bright or dark they are.

I like that the automation lanes are now tinted the track color. I find it groups them with their associated track better at a glance.

I find the Arrange section is clearer and more effective at communicating what's going on.

Then there is the clip editor. The clip editor is worlds better in V6, both visually and functionally.

Overall, much improved, with a few gotchas that need some work. For example Polarity made some good points about how automation is accessed in the track header that was more effective in V5. That stuff will get sorted and a few user suggested refinements already made it into beta 2 from beta 1.

[Cyoon]

I also like the new indicator that cycles when you have a clip in the launcher running, you know, the one where you switch between launcher and arranger. Generally also pretty amazed by the update, visually and feature wise.

[webmob]

In the beta of BWS 6 there is a bug that I suddenly can't type in the fields, search fields, exact values and so on.

Only by restarting BWS I can type again.

This is a massive bug for killing the workflow.

Are you maybe using a Linux distribution with GNOME i.e. Ubuntu? From which version did you upgrade to 6-beta? If you are using Linux indeed, did you upgrade your OS recently?

I'm asking because I have the same problem since 5.3.8, and even if I have reported it to Bitwig support, they couldn't reproduce it so far. The bug I'm hitting seems to be in an upstream component Bitwig uses, not in Bitwig itself -- see https://discourse.ubuntu.com/t/text-inp ... u=icaria36

I have the same issue here with Debian 12 Gnome and now also with Debian 13.

[pc999]

Are you maybe using a Linux distribution with GNOME i.e. Ubuntu? From which version did you upgrade to 6-beta? If you are using Linux indeed, did you upgrade your OS recently?

I'm asking because I have the same problem since 5.3.8, and even if I have reported it to Bitwig support, they couldn't reproduce it so far. The bug I'm hitting seems to be in an upstream component Bitwig uses, not in Bitwig itself -- see https://discourse.ubuntu.com/t/text-inp ... u=icaria36

I am indeed using Linux with Gnome, Ubuntu 25.04 (wayland) and it indeed it also happened with the latest 5.3 BWS version that I used.

I can't recall if it started to happen after the update to 25.04, but probably yes.

[chaocrator]

beta 2 is out.

[questionaire]

Are you maybe using a Linux distribution with GNOME i.e. Ubuntu? From which version did you upgrade to 6-beta? If you are using Linux indeed, did you upgrade your OS recently?

I'm asking because I have the same problem since 5.3.8, and even if I have reported it to Bitwig support, they couldn't reproduce it so far. The bug I'm hitting seems to be in an upstream component Bitwig uses, not in Bitwig itself -- see https://discourse.ubuntu.com/t/text-inp ... u=icaria36

I am indeed using Linux with Gnome, Ubuntu 25.04 (wayland) and it indeed it also happened with the latest 5.3 BWS version that I used.

I can't recall if it started to happen after the update to 25.04, but probably yes.

I dont have these issues with Kubuntu 24.04 which has a KDE desktop ofcourse and not GNOME. Just to let you know. Maybe switch to KDE? Its all personal ofcourse but i prefer KDE above GNOME. Nearly everything can be modified visually in KDE.

[questionaire]

beta 2 is out.

Unbelievable what a list with fixes...

[icaria36]

I dont have these issues with Kubuntu 24.04 which has a KDE desktop

Yes, in the link I have shared above I explain that I can only reproduce the bug with GNOME, not with KDE. I'm well familiar with Qt, Plasma, KDE, but I'll try to find the buggy component and stick with GNOME.

Anyway, it doesn't seem to be specific to Bitwig.

[Sysagent]

Seem to have a MIDI loop issue with the Beta…

Have a Hydrasynth Deluxe in multi voice mode and two different string voices on each separate midi channel (2 & 3), they are both nested in a group as well. Once the clips have stopped playing in the arrangement view one of the chord clips that has been playing (channel 3) just stays stuck on, in version 5.3 this does not occur with the same arrangement.

Somewhat annoying, on an otherwise good beta release.

[kultschar]

Make sure report - might be fixed for next beta

[stamp]

Have you seen what they have done to gruop tracks?

I think there is a good chance they will revert the group master... with suitable user feedback

I really hope so. If not, I will stay with 5 forever. I'm ultrafast with 5 and the overhaul to automation (missing last parameter lane in unfolded automation lane) and the new groups would just slow me down and all the new can't compensate for lost workflow. Let's see.

I haven't sent in an email yet about the group master. I figure they are focused on all the crashes and obvious bugs... but I will soon.

[stamp]

Have you seen what they have done to gruop tracks?

I think there is a good chance they will revert the group master... with suitable user feedback

What is the group tracks issue?

I haven't noticed a problem, but also haven't tried to do much beyond group tracks to add group FX so far...

When selecting 'show track master content' in group right click menu it creates a track inside instead of showing it on the group so you have to unfold to see it. To make it worse, the track appears on the end of the group under all other tracks.
If you time select a section on the group and bounce in place it won't show the rendered wafevorm on the track wich is really bad since that waveform was editable (cut, copy, paste, duplicate, split, slide content, etc) and when double clicked opens the wave editor. Before you could 'show master track content' to loop the bounce or stretch via alt-drag on border of bounce. All this was possible without unfolding your groups, keeping arrangement clutter free and compact.
They removed funcionality and made the overview of arrangement worse, in regards to bounces on groups.

[stamp]

Have you seen what they have done to gruop tracks?

I think there is a good chance they will revert the group master... with suitable user feedback

What is the group tracks issue?

I haven't noticed a problem, but also haven't tried to do much beyond group tracks to add group FX so far...

In V5, you could have the group track show the tracks visualization, or the group master content. SO if you use the group master to bounce the sub-tracks to audio, it could show on the group track.

In V6, they made the group master a sub-track that can be shown or not inside the group. So if you bounce to audio on the group master, you can only see it by unfolding the group.

Read post above this one.