Bitwig 6 Beta coming soon

[pdxindy]

No Leras I’m moving notes down the scale on the same track in the same clip. I believe it’s a bug.

The pattern list is only comprised of clips currently in the project. There's no saving of patterns to form a list. So I'd say it is an oversight of their implementation, not a bug.

I agree it is odd to have the pattern disappear, but what would be the solution?

[ere2learn]

sames as 5. its a bug in 6

Screenshot 2025-09-07 021157.png

Screenshot 2025-09-07 021213.png

[D-Fusion]

sames as 5. its a bug in 6

Screenshot 2025-09-07 021157.png

Screenshot 2025-09-07 021213.png

It does the same in latest V5.

If i drag the notes to the same place like you have done in the bottom picture and i try to move those selected notes to a new pitch placement after that in the piano roll it breaks up the long sustained note under it in the note lengths that the notes you are moving are set to.

This must be a bug in Bitwig since it should keep the note that was there before intact and not cut it in pieces from the overlapping notes when those are moved.

Added some new discoveries on this Mystery:

This is Weird.
I Did do some more testing now and it does not do it when i select the notes and use the up/down arrow keys to move the selected notes but if i use the mouse to drag the notes to another pitch after they has been overlapped it cuts the notes like i explained but if i then use the up/down arrow keys right after that the long note looks Normal again.

[pdxindy]

sames as 5. its a bug in 6

What do you expect to happen?

[qtheerearranger]

No Leras I’m moving notes down the scale on the same track in the same clip. I believe it’s a bug.

The pattern list is only comprised of clips currently in the project. There's no saving of patterns to form a list. So I'd say it is an oversight of their implementation, not a bug.

I agree it is odd to have the pattern disappear, but what would be the solution?

to have the pattern stay in the pattern list? especially if its been physically renamed I feel like that should be some sort of hard save.

[el-bo (formerly ebow)]

I'm not a bitwig user - testing the beta right now.

I thought a current update plan was required to play with the BETA.

What's the trick?

Splice rent-to-own has a free trial or just pay 16 bucks and use Bitwig for one month + trial period.

Gotcha! Thanks

[Dionysos]

What do you expect to happen?

As long as the notes are selected, Bitwig needs to consider them as separate from the other notes so that they can't destroy them during an ongoing move action. Then destructively commit when deselecting.
Or alternatively, allow events to overlap even if the displayed notes then differ from the midi that they generate – this is probably the most user friendly approach.

Bitwig's current behaviour is also quite annoying when editing audio, where simply moving things around inside a clip can easily overwrite existing events, and because there are no multiple lanes to move things to, sometimes you don't have a choice.

But it's a quite fundamental issue that's probably not trivial to fix.

[pdxindy]

to have the pattern stay in the pattern list? especially if its been physically renamed I feel like that should be some sort of hard save.

Yeah, I understand you don't want to lose that pattern and I agree.

My question was how should it be saved? Currently there is no savable patterns or pattern lists. It would require a new feature (which sounds useful to me) be added.

[pdxindy]

What do you expect to happen?

As long as the notes are selected, Bitwig needs to consider them as separate from the other notes so that they can't destroy them during an ongoing move action. Then destructively commit when deselecting.
Or alternatively, allow events to overlap even if the displayed notes then differ from the midi that they generate – this is probably the most user friendly approach.

Bitwig's current behaviour is also quite annoying when editing audio, where simply moving things around inside a clip can easily overwrite existing events, and because there are no multiple lanes to move things to, sometimes you don't have a choice.

But it's a quite fundamental issue that's probably not trivial to fix.

Ahh, thanks for the explanation. I didn't understand that it's the destructive aspect while still selected that is being referred to.

It's possible it may not be hard to address... since if you select some notes and arrow them around, notes that get passed as you do so are not destructed.

Also, if you set the 3 notes to a different midi channel, then they can overlap fine. So there are a couple cases already where this doesn't happen.

[Dionysos]

It's possible it may not be hard to address... since if you select some notes and arrow them around, notes that get passed as you do so are not destructed.

You're right, there are cases where Bitwig already handles this correctly. So maybe it is simply a bug and not some fundamental limitation

[jens]

I am just amazed anyone playing in instruments or vocals doesn't need to fix pitch, maybe its just my playing/singing!

There are lots of tuning plug ins like Autotune, that's usually plenty if the vocals need tuning.

The classic Autotune is a realtime effect and a completely different thing. The current Autotune Pro also can function in a similar way to Melodyne - but to make full use of it... you need ARA2

So nice suggestion there - you basically proved yourself wrong.

Maybe... just an idea... I mean it's pretty obvious that you don't use these tools yourself and have a rather rudimentary idea what they do and how they can be used (suggesting offline use instead of ARA is funny at best) so why don't you concentrate on topics you know a lot more about instead?

You said tuning vocals, and just saying there are non ARA tools to do this. (My Autotune is not ARA)

(I am not up to date with ARA, you are correct)

I didn't mention vocals, SLIC did - as an example. But that is beside the point either way.

The classic Autotune is a realtime-effect and as such is not related to ARA in any way at all.

The classic Autotune can make as much use of ARA as any conventional compressor, EQ, reverb or flanger plugin - absolutely none whatsover.

And thus here is no point in even mentioning realtime pitch-correction plugins when it comes to ARA.

Bu let's put it this way: would there be any offline pitch-correction tools at all, if realtime plugins would be the be all and end all of pitch-correction? No, there wouldn't. And then there'd be no need for ARA in the first place, at least when it comes to pitch-correction.

ARA is a godsend for offline processes i.e. plugins that can see the complete file at once, not just 100-200 (or so) samples.

[qtheerearranger]

to have the pattern stay in the pattern list? especially if its been physically renamed I feel like that should be some sort of hard save.

Yeah, I understand you don't want to lose that pattern and I agree.

My question was how should it be saved? Currently there is no savable patterns or pattern lists. It would require a new feature (which sounds useful to me) be added.

we have a pattern list now that I think we just need to add icons to - right click your midi region go to patterns and you can scroll through the list there. I'm not a dev but to me you just put a small pin button next to the pattern name so you can pin certain patterns or a lock icon. or it can be done in the inspector on the left too.

[_leras]

What do you expect to happen?

As long as the notes are selected, Bitwig needs to consider them as separate from the other notes so that they can't destroy them during an ongoing move action. Then destructively commit when deselecting.
Or alternatively, allow events to overlap even if the displayed notes then differ from the midi that they generate – this is probably the most user friendly approach.

Bitwig's current behaviour is also quite annoying when editing audio, where simply moving things around inside a clip can easily overwrite existing events, and because there are no multiple lanes to move things to, sometimes you don't have a choice.

But it's a quite fundamental issue that's probably not trivial to fix.

I think they should allow this as an option where notes can overlap.

It can be confusing how duplicating a note can eat into a subsequent note, I come across this when editing quite often.

Stacking notes can also be confusingly, and probably needs a midi note list in text to be very clear. But if I am trying to copy and move a note for a SD hit to add a hit in front of a note, an option to trim the note being moved, and not the note already in the right place would be good.

I guess their approach is wysiwig, but definitely for notes it should not be destructive until after something has finished moving...

[Dionysos]

It can be confusing how duplicating a note can eat into a subsequent note, I come across this when editing quite often.

Totally agree. I sent a request about this to Bitwig just yesterday, I figured chances were quite good that they might address it during the v6 beta period. I suggested that any notes inserted or moved to before other notes on the same key should be trimmed so they don't mess with the subsequent notes' start time.

[jonljacobi]

Okay, I give up. Where's the onset editing?