Changes in Bitwig Studio 6.0, Beta 6 [released 07 November 2025]

[JHernandez]

Changes in Bitwig Studio 6.0, Beta 6 [released 07 November 2025]

IMPROVEMENTS

Clip Launcher refinements:

。The relative phase of playing clips is now preserved. (It was working in some cases in previous releases, but with some bugs.)

。For example, if you trigger one Launcher clip and then starting another two bars later:

• Stopping and starting the transport will resume playback of the clips just as they were originally aligned.

• If the Arranger play position is moved, clip playback is also moved relatively with the original alignment.

• Operators and seeded Spread settings are taken into account, so the current loop iteration will be calculated.

• When the Arranger loop is enabled, automatic loop jumps do not update Launcher clip positions.

。A new action to Retrigger playing Launcher clips is now available:

• From transport stop, this action retriggers all clips that were playing, thereby re-aligning them from their start.

• If the transport is playing, this action queues the retrigger using the largest Main Launch Quantize setting of the playing clips.

• Holding [ALT] transforms the Launcher's Return playback to Arranger Timeline buttons into clickable Retrigger playing Launcher clips buttons.

• Both project- and track-level actions are available in this case.

• You can also assign a keyboard or MIDI shortcut to this action.

• Audio playback now uses short anti-click fades on transport stop

• Dragging the start or end of Arranger clips now snaps to various content snap points (such as onsets), when
snapping is enabled [39023]

• Toggle In and Toggle Out (Mix) Grid modules: Active ports are now visualized based on the modulated value

• macOS: Added camera permission to the audio engine, in case plug-ins want to, um, use the camera

FIXES

• MIDI notes are no longer recorded into Launcher clips too early (a regression) [40070]

• Audio clip fade-outs are not preserved thru to next transport start anymore (a regression) [39960]

• Fixed a performance regression with device sleeping rules [40065]

• Dragging parameter values clamps at the extremes again (a regression) [40067]

• Tracks with monitoring set to On now display input when record armed again [40017]

• Fixed slow painting performance with zoomed-in waveforms [40049]

• Group track remote macro automation is played back at the proper speed again [40058]

• Creating a point on the Flying Automation Lane no longer adds an additional point at time zero

• Note clips recorded with pre-roll are no longer late (a regression) [40068]

• Audio events no longer crackle when adjusting their Gain expression during playback (a regression) [40015]

• Muted arranger clips no longer report a note at the beginning (a regression) [39939]

• Split is now in Arrange context menus for clip and time selections[40029]

• Expand action can apply spread and chance settings again[39982]

• Newly created notes are auto-selected more consistently now [39032]

• Relative snapping works again [39023]

• FX Grid (The Grid) device: Voice stack solo (in the Inspector Panel) now works for True Mono cases as well

• Dragging an Arranger time selection no longer leaves clearing preview decorations behind

• Time scrollbars properly show muted clips in their visualization

• Pencil tool now erases notes when double-clicked [39029] Clicking one Arranger clip of a multiselection now selects it as the new target clip [39441]

• Duplicating a scene no longer creates alias clips [38990]

• When dragging from the Browser Panel to the Arranger, holding [SHIFT] toggles the snapping behavior again [39302]

• Automation Follow now works when dragging a time selection on the Arranger [40061]

• Moving a playing Launcher clip to another scene keeps it playing again [39881]

• Reverse and various Scaling functions no longer misbehave in certain multiselection cases [39894]

• Using Split on an Arranger time selection returns a time selection [40030]

• VST3 plug-ins: Better handling of the restart component [39935]

• Dragging audio/note Launcher Clips doesn't bring common automation clips over and leads to strange behaviour and later crashes [38606]

CRASHES FIXED

• Fixed crash when changing Detail Editor Panel time grid settings [40031]

• Fixed audio engine crash when using Arpeggiator to transpose steps with Use Global Key enabled [39722]

• Fixed occasional crash when automation recording starts [40042]

• Fixed crash when unfolding chains for the master track in Mix view [39125]

• Fixed crashes when using time selections with the Detail Editor Panel in Track context [40039, 40043]

• Fixed crash when saving a clip with automation, but excluding devices [39958]

• Fixed crash when recording MIDI automation in a loop [40042]

• Fixed crash when copying a group track to another project [39422]

• Fixed audio engine crash when deleting a muted clip whilst it was playing

• Fixed crash when selecting a Launcher clip, in some cases [40033]

• Fixed crash when dragging a clip's start to erase other clips in Arranger [39943]

[dckyoto]

Anyone else getting the issue of the audio engine going awry after you’ve dragged the boundary between two clips, one of which is disabled? Looks like a memory splat, there is also no way to create a fade in on an audio clip that is adjacent to the right of a disabled audio track.

After dragging (with the slip tool) the boundary between a disabled clip and an enabled clip, one of my other tracks stops outputting audio, and when I stop/start all I hear is a sharp click on that track. So if anyone wants to test this make sure you have a bunch of audio tracks, and in my case I was adjusting the clip boundary on a track below the one that stopped sounding.

[dckyoto]

Just noticed this beta came out overnight for me, and the issue I was having above was in beta 5. I will try the same thing later today and see if it is fixed.

[dckyoto]

I think something has regressed, I am getting different results from exporting wavs compared to realtime playback - it feels like the plugin is being woken up during export and causing a small fade in kind of glitch (Guitar Rig in this case). In Bitwig itself it plays fine, but in the exported wav file there is the ducking fade as (I presume) the guitar rig plugin is woken up?

The above problem I posted about is fixed I think, but I am getting "plugin crashed - reload plugin" errors, and in all the years of using Bitwig I've never seen this many plugin errors.

[silicon1138]

Clip playback/stop/playback seems to be fixed for me now. I was having clips really struggling to lock onto their bar 1 starting point and they were occasionally playing from all over the place. Alas, bounced clip sSTILL do not have Looping switched on by default. This is killing me having to manually activate this for every single bounce.

[Milkman]

Browser behavior, for me, has regressed. I usually start BWS with audio file locations set to not refresh because it speeds up startup scanning. This time, regardless if folder scanning is enabled or not, BWS 6 b6 is scanning forever and refreshing the same folder view over and over. It keeps disappearing, refreshing, disappearing, refreshing, like when the browser was first updated under 5.0.

[_leras]

Clip playback/stop/playback seems to be fixed for me now. I was having clips really struggling to lock onto their bar 1 starting point and they were occasionally playing from all over the place. Alas, bounced clip sSTILL do not have Looping switched on by default. This is killing me having to manually activate this for every single bounce.

Make sure to email them.

[_leras]

So many tweaks and fixes.. that must be so hard to keep track of!!!

[koalaboy]

So many tweaks and fixes.. that must be so hard to keep track of!!!

Welcome to Software Engineering (The devil that is JIRA or similar - the world of tickets)

(I have no insight into Bitwig, but a lot of insight into other high-profile development)

[c_bomb]

Is there a way to return the behaviour with the pointer tool where the time selection becomes available when hovering over the lower half of a clip?

[Dionysos]

Is there a way to return the behaviour with the pointer tool where the time selection becomes available when hovering over the lower half of a clip?

Yes, enable the "Pointer tool supports time selection" option in the arranger settings menu, the button for it is in the very bottom-right corner of the arranger.

[c_bomb]

Is there a way to return the behaviour with the pointer tool where the time selection becomes available when hovering over the lower half of a clip?

Yes, enable the "Pointer tool supports time selection" option in the arranger settings menu, the button for it is in the very bottom-right corner of the arranger.

Thank you very much, appreciate it!

[silicon1138]

Clip playback/stop/playback seems to be fixed for me now. I was having clips really struggling to lock onto their bar 1 starting point and they were occasionally playing from all over the place. Alas, bounced clip sSTILL do not have Looping switched on by default. This is killing me having to manually activate this for every single bounce.

Make sure to email them.

I have been in contact with them and they are aware of it.

[_leras]

I have been in contact with them and they are aware of it.

I'm looking forward to downloading this. I've moved many things over to the Beta.

I've also found the start position jumping when looping in arrange, for me it seemed to be if I selected notes by dragging a box around a few, it would change the restart position, when I want to keep using space to stop and restart from the same place. Hoping thats fixed here now.

btw, I feel fairly safe using the Beta as I always use a version number on every file I save e.g. trackname v1_01, so I can always go back to any earlier versions.

[silicon1138]

BW6 seems to have been in beta for a very long time now. It's been the most buggy version of BW i've personally used. I have quite a lot of niggling little graphical anomalies on my M1 MacBook Air. Things like audio clips suddenly becoming unresponsive to cutting or dragging and also backgrounds of audio clips flickering. I've had arrangement page graphical glitches too with stripy phantom parts left behind after moving around chunks of arrangement. One project became so bugged out the other day (spinning beachball of doom) that i ended up eventually reloading and saving the entire thing as a project file which i was then able to open in BW5. It's frustrating. Going back to 5 feels REALLY horrible now too. A final public release can't come soon enough. Perhaps they bit off a bit more than they could chew with this jump in features...