Bitwig 6

[webmob]

Hello.
How is the performance when you zoom in very far into a waveform in the arrange view?
For me, the program becomes very slow and unusable until I zoom out again. (linux, flatpak and deb)
thx

On my 7 year old Windows PC, it drops the UI from 120fps to around 60fps by zooming in as far as possible on a waveform in the Arrange view. If I do the same thing, but instead in the Detail editor, there's no change in framerate, and it stays at 120fps.

Do you also have performance issues when you zoom in?

[icaria36]

Hello.
How is the performance when you zoom in very far into a waveform in the arrange view?
For me, the program becomes very slow and unusable until I zoom out again. (linux, flatpak and deb)
thx

On my 7 year old Windows PC, it drops the UI from 120fps to around 60fps by zooming in as far as possible on a waveform in the Arrange view. If I do the same thing, but instead in the Detail editor, there's no change in framerate, and it stays at 120fps.

I can reproduce this performance problem as well. Zooming in a clip in the arranger (and therefore zooming in the entire arranger) slows down the UI very noticeably. As I zoom out, the UI the refresh rate increases until being "normal". And indeed, the problem doesn't happen when zooming in only a specific clip in the Detail editor. Linux Deb on a decently equipped PC.

[icaria36]

Sometimes, very sporadically, when the transport is playing and I'm manipulating midi clips in the arranger (moving a clip, resizing it...), a midi note will get stuck. Sometimes the glitch resolves itself when there is a change of clip in the arranger. A couple of times I got a midi note really stuck and I had to do something like deactivate the device or track or restart Bitwig.

I don't recall this type of problem before Bitwig 6, but I'm not sure whether it is something specific to this new project I'm working on (I started it as Bitwig 6 was available) and I also started using a new midi controller with this project and Bitwig 6 (I also get a note momentarily stuck if the controller isn't connected but I think I only got the note really stuck with the controller connected.

Anyway, too many variables and I will start paying more attention to this problem if it happens again. Until now I have just reacted with surprise and rushing to silent the noise without thinking much. Sharing this here just in case someone has noticed something similar.

[inkling]

Does anyone know what's up with the snapping behaviour in Edit view? If I have a midi event that i'm moving the Loop region from the left to align with, the midi event snaps to the left edge of the screen. This behaviour wasn't present in Bitwig 5. Is there a way to turn this snapping off?

[tumface]

Do you also have performance issues when you zoom in?

If you consider what I described as a performance issue, then yeah. I guess it is.

[webmob]

Do you also have performance issues when you zoom in?

If you consider what I described as a performance issue, then yeah. I guess it is.

If I understand correctly, you don't experience any delay in the GUI's response time when you've zoomed in to the maximum in the arrange view.

[tumface]

If I understand correctly, you don't experience any delay in the GUI's response time when you've zoomed in to the maximum in the arrange view.

The whole GUI runs at a lower frame rate, so yes, the response time is slower.

Actually, I've determined that the problem is worse the later in the waveform you're viewing.

If you zoom to 100% at the first part of the waveform, it barely makes any difference.

If you zoom to 100% at the end part of a waveform that's more than a few seconds long, the entire UI becomes barely usable.

I wonder if perhaps the drawing code is accidentally drawing the entire waveform off the left side of the viewport, and only stops when it hits the end of the visible area on the right side of the viewport.

I've reported this (with video clip reproducing it) to their beta test report email address. I have a lot of reports in that queue.

[webmob]

If I understand correctly, you don't experience any delay in the GUI's response time when you've zoomed in to the maximum in the arrange view.

The whole GUI runs at a lower frame rate, so yes, the response time is slower.

Actually, I've determined that the problem is worse the later in the waveform you're viewing.

If you zoom to 100% at the first part of the waveform, it barely makes any difference.

If you zoom to 100% at the end part of a waveform that's more than a few seconds long, the entire UI becomes barely usable.

I wonder if perhaps the drawing code is accidentally drawing the entire waveform off the left side of the viewport, and only stops when it hits the end of the visible area on the right side of the viewport.

I've reported this (with video clip reproducing it) to their beta test report email address. I have a lot of reports in that queue.

Thank you very much for the explanations.

[webmob]

If I understand correctly, you don't experience any delay in the GUI's response time when you've zoomed in to the maximum in the arrange view.

The whole GUI runs at a lower frame rate, so yes, the response time is slower.

Actually, I've determined that the problem is worse the later in the waveform you're viewing.

If you zoom to 100% at the first part of the waveform, it barely makes any difference.

If you zoom to 100% at the end part of a waveform that's more than a few seconds long, the entire UI becomes barely usable.

I wonder if perhaps the drawing code is accidentally drawing the entire waveform off the left side of the viewport, and only stops when it hits the end of the visible area on the right side of the viewport.

I've reported this (with video clip reproducing it) to their beta test report email address. I have a lot of reports in that queue.

Thank you very much for the explanations.

It's fixed

[krixa]

My subscription just ended a couple of days ago. I still se the beta downloads on my account page. Am I screwed when final release comes?

[Satch1]

My subscription just ended a couple of days ago. I still se the beta downloads on my account page. Am I screwed when final release comes?

No, you will get the release version

[Dionysos]

You're not screwed, you'll get the final version and all of its bug fix releases (6.0.1, 6.0.2...), but not 6.1

[krixa]

Thanks alot!

[mxbf]

i had a very egregious error with automation not moving properly yesterday, which i will detail in #2. these are the two main issues I have with 6 still:

1. crashing
the crashes randomly happen when i have been recording and then stop playing or deactivate recording. most of hte time it works fine but about once per 1-2 hours it will stall and crash. that happens about 5-6 times a day when i am working on stuff. quite annoying.

2. automation not moving when inserting silence / duplicating time. then undo doesn't move the automation!
this was a very bad one for me and prompted me to write this. yesterday i had written a ton of automation and then went to insert a few bars at the start to add stuff and didnt notice that the automation had not moved with the clips when i inserted silence, like it had not been effected at all. i observed this behavior multiple times when duplicating time as well, automation would not move at all. then when I tried "undo" operations, the automation would strangely stay in the same location, it could not be fixed. so for yesterday i couldn't do any insert silence or duplicate time operations. it was very weird. i am about 90% sure that describes the issue, unless maybe i imagined sometime or did something wrong.


(for the record I know it's my fault for using the beta to make stuff)

[Mantras]

The clip automation write button disappeared after installing the latest beta. Anyone know what happened? How can I write automation to clips in realtime now?