Bitwig 6 Beta coming soon
- KVRian
- 1305 posts since 12 Nov, 2002 from Newcastle, UK
Just invoked the licence renewal I bought ages ago for this update, will play with the new (to me) features while waiting for the beta 
"Micro Kid speaks digi-talk.."
-
- KVRist
- 374 posts since 5 Nov, 2007 from Liverpool, UK
Better still, buy it at JRR shop using code 'FORUM'. You should see a nice little discount.
-
- KVRian
- 924 posts since 24 Sep, 2016
Thanks.pdxindy wrote: Fri Aug 01, 2025 5:57 amThere's a sale on until Aug 4th. An upgrade is normally $169 and is currently available for $129. You can purchase, then activate it whenever you want.3lu5iv3 wrote: Fri Aug 01, 2025 1:15 am Will there be an upgrade discount when the official V6 launches? i am a V4 user. i wanna skip V5 and upgrade to V6.
SoundCloud
"I believe every music producer inherently has something unique about the way they make music. They just have to identify what makes them different, and develop it" - Max Martin
"I believe every music producer inherently has something unique about the way they make music. They just have to identify what makes them different, and develop it" - Max Martin
- KVRAF
- 2192 posts since 8 Jan, 2005
Nice. My license is valid until April 2026, but that's a nice enough of a deal
MacMini M2 Pro …… MacOS Tahoe ……… Reason 14
-
- KVRian
- 1407 posts since 1 Jul, 2023
A few things I'd like to see:
- Midi modifiers actually changing the midi in the piano roll.
-Opening the piano roll automatically focuses on the actual notes painted therein. So annoying that it opens normally on a completely blank section of the piano roll.
-Duplicate notes on top of existing notes similar to Ableton where you can duplicate and drag out from the duplicated note without the original note being consumed. This also happens when you accidentally draw a note over another. The "bottom" note is consumed.
-Editor window contains both bar/beat numbering relative to that particular clip as well as markings for the overall track. If I have a midi or audio clip at, say, bar 18 and click into this, I can only see the clips own internal time scheme. Bar 18 of the project becomes bar 1 of the clip. This is annoying because you need to jump out of the editor to assess overall position of the clip. Or you can just do basic arithmetic.
-Double clicking the editor window doesn't always open the editor window. This is related more to rhe various screen layouts Bitwig provides but very often, I double click the editor window when in arrange view and it simply doesn't open.
-View follows playhead seems to get disabled constantly. Why? I've mapped a shortcut to this but it seems like nearly any action disables it.
-Too often when I click to insert the triangular played button to start playback at a specific point, it just doesn't start there. It normally takes two clicks to get this working.
-Context specific tools can be annoying. You need to position the mouse very carefully to enable the clip gain tool for example, and its too dependsnt on your current zoom level. I know there are workarounds but this gets
annoying.
-Re the above: when I'm editing midi on the piano roll, and trying to adjust velocity, too often I need to change tools or deselect particular notes to quickly adjust velocity. This would be a perfect situation for context specificity. If I'm hovering my mouse over the velocity of a note, I probably want to adjust that velocity so enable the tool which does that!
- when I open a clip to draw in pr edit recorded automation, and open the particular automation lane, there is often literally no automation visible. I then need to randomly draw something after which I can see my recorded automation and have to undo the random scribbling I did to force the automation to reveal itself.
I should note that some of the above could simply be me not getting some key concepts. It was only relatively recently when I fully grasped what is happening with audio clips. The container is a seperate discrete entity housing the audio, it isn't the audio itself. I discovered this because I was painting one shot drums on the time and it wasn't conforming to the groove/shuffle settings I'd established. Once I consolidate all of those hits into a discrete container, the groove quantisation was audible. This was something of a revelation to me. I've been using Bitiwg for about 18months now and it is so deep that I'm never sure if I'm doing something wrong or some functionality I'm after just isn't there.
Love Bitwig for all that. I've used FL, Reason Cubase over the years and BW is easily rhe best for what I'm trying to achieve.
- Midi modifiers actually changing the midi in the piano roll.
-Opening the piano roll automatically focuses on the actual notes painted therein. So annoying that it opens normally on a completely blank section of the piano roll.
-Duplicate notes on top of existing notes similar to Ableton where you can duplicate and drag out from the duplicated note without the original note being consumed. This also happens when you accidentally draw a note over another. The "bottom" note is consumed.
-Editor window contains both bar/beat numbering relative to that particular clip as well as markings for the overall track. If I have a midi or audio clip at, say, bar 18 and click into this, I can only see the clips own internal time scheme. Bar 18 of the project becomes bar 1 of the clip. This is annoying because you need to jump out of the editor to assess overall position of the clip. Or you can just do basic arithmetic.
-Double clicking the editor window doesn't always open the editor window. This is related more to rhe various screen layouts Bitwig provides but very often, I double click the editor window when in arrange view and it simply doesn't open.
-View follows playhead seems to get disabled constantly. Why? I've mapped a shortcut to this but it seems like nearly any action disables it.
-Too often when I click to insert the triangular played button to start playback at a specific point, it just doesn't start there. It normally takes two clicks to get this working.
-Context specific tools can be annoying. You need to position the mouse very carefully to enable the clip gain tool for example, and its too dependsnt on your current zoom level. I know there are workarounds but this gets
annoying.
-Re the above: when I'm editing midi on the piano roll, and trying to adjust velocity, too often I need to change tools or deselect particular notes to quickly adjust velocity. This would be a perfect situation for context specificity. If I'm hovering my mouse over the velocity of a note, I probably want to adjust that velocity so enable the tool which does that!
- when I open a clip to draw in pr edit recorded automation, and open the particular automation lane, there is often literally no automation visible. I then need to randomly draw something after which I can see my recorded automation and have to undo the random scribbling I did to force the automation to reveal itself.
I should note that some of the above could simply be me not getting some key concepts. It was only relatively recently when I fully grasped what is happening with audio clips. The container is a seperate discrete entity housing the audio, it isn't the audio itself. I discovered this because I was painting one shot drums on the time and it wasn't conforming to the groove/shuffle settings I'd established. Once I consolidate all of those hits into a discrete container, the groove quantisation was audible. This was something of a revelation to me. I've been using Bitiwg for about 18months now and it is so deep that I'm never sure if I'm doing something wrong or some functionality I'm after just isn't there.
Love Bitwig for all that. I've used FL, Reason Cubase over the years and BW is easily rhe best for what I'm trying to achieve.
- KVRAF
- 26922 posts since 3 Feb, 2005 from in the wilds
Yeah, it would be handy to have to option to see both relative and absolute timeline values.swilow11 wrote: Sat Aug 02, 2025 10:39 pm -Editor window contains both bar/beat numbering relative to that particular clip as well as markings for the overall track. If I have a midi or audio clip at, say, bar 18 and click into this, I can only see the clips own internal time scheme. Bar 18 of the project becomes bar 1 of the clip. This is annoying because you need to jump out of the editor to assess overall position of the clip. Or you can just do basic arithmetic.
If you switch the editor to track mode, then the clips will show the position on the arrange timeline. You can swap between Clip <-> Track modes via Alt-C
-
- KVRian
- 1407 posts since 1 Jul, 2023
Aha, nice tip- thankyou (and also for summarising my thought much better than I could!)pdxindy wrote: Sun Aug 03, 2025 6:19 amYeah, it would be handy to have to option to see both relative and absolute timeline values.swilow11 wrote: Sat Aug 02, 2025 10:39 pm -Editor window contains both bar/beat numbering relative to that particular clip as well as markings for the overall track. If I have a midi or audio clip at, say, bar 18 and click into this, I can only see the clips own internal time scheme. Bar 18 of the project becomes bar 1 of the clip. This is annoying because you need to jump out of the editor to assess overall position of the clip. Or you can just do basic arithmetic.
If you switch the editor to track mode, then the clips will show the position on the arrange timeline. You can swap between Clip <-> Track modes via Alt-C
- KVRAF
- 37374 posts since 14 Sep, 2002 from In teh net
I hope they fix the browser to make it actually display the content you need it to and also don't do anything to break remote controls editing but do add a means of backing up, exporting and importing remote controls
- KVRAF
- 26922 posts since 3 Feb, 2005 from in the wilds
If you have a selected note(s), you can Alt-click drag to create copies. It does not affect the original.swilow11 wrote: Sat Aug 02, 2025 10:39 pm -Duplicate notes on top of existing notes similar to Ableton where you can duplicate and drag out from the duplicated note without the original note being consumed. This also happens when you accidentally draw a note over another. The "bottom" note is consumed.
Also, FYI, notes on the piano roll can overlap (or completely cover) other notes if the overlapping notes are on different midi channels.
-
- KVRist
- 153 posts since 6 Mar, 2009
Bitwig please add these features to Bitwig Studio 6...
- ARA support
- The ability to route outputs from multi-output VSTI's the same way as other tracks are routed
- The ability to set default output buses on VSTI loading. At least globally, ideally per VSTI or via the browser
- The ability to route the output of the loop browser to any buss or track
- The ability to route MIDI from the loop browser to Instrument tracks
- Please restore the ability to view the clip launcher along with upper meters or at least add separate view controls for left and right panes.
- The option to not automatically route saved instrument presets to the Master bus when reloaded. If a preset is saved without an output bus, that is how it should reload.
-- Insert profound words here --
-
- KVRAF
- 2427 posts since 11 Jan, 2009 from Portland, OR, USA
Why not contact them directly... are they really determining their development workload based on random KVR posts? Doubtful...eBlue wrote: Wed Aug 06, 2025 9:28 pm Bitwig please add these features to Bitwig Studio 6...
Thanks for the awesome Softube Console 1 integration. It still makes me smile every day!
- ARA support
- The ability to route outputs from multi-output VSTI's the same way as other tracks are routed
- The ability to set default output buses on VSTI loading. At least globally, ideally per VSTI or via the browser
- The ability to route the output of the loop browser to any buss or track
- The ability to route MIDI from the loop browser to Instrument tracks
- Please restore the ability to view the clip launcher along with upper meters or at least add separate view controls for left and right panes.
- The option to not automatically route saved instrument presets to the Master bus when reloaded. If a preset is saved without an output bus, that is how it should reload.
-
- KVRist
- 153 posts since 6 Mar, 2009
Just did. Thanks for the suggestion.mholloway wrote: Wed Aug 06, 2025 9:32 pmWhy not contact them directly... are they really determining their development workload based on random KVR posts? Doubtful...eBlue wrote: Wed Aug 06, 2025 9:28 pm Bitwig please add these features to Bitwig Studio 6...
Thanks for the awesome Softube Console 1 integration. It still makes me smile every day!
- ARA support
- The ability to route outputs from multi-output VSTI's the same way as other tracks are routed
- The ability to set default output buses on VSTI loading. At least globally, ideally per VSTI or via the browser
- The ability to route the output of the loop browser to any buss or track
- The ability to route MIDI from the loop browser to Instrument tracks
- Please restore the ability to view the clip launcher along with upper meters or at least add separate view controls for left and right panes.
- The option to not automatically route saved instrument presets to the Master bus when reloaded. If a preset is saved without an output bus, that is how it should reload.
-- Insert profound words here --
-
qtheerearranger qtheerearranger https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=325452
- KVRian
- 919 posts since 26 Mar, 2014 from Denver, Co
I wonder when they are going to drop some real teasers?
Bitwig 6 • Diva, Dune, Serum, and UVI Falcon are my Daily Drivers • Drum Machines • Harrison 32c + DSM 3 + American Class A Enjoyer • Apple M4 Max • Apollo User • DJ • Dance Music is life
-
- KVRist
- 166 posts since 16 May, 2008 from Germany
Frankly spoken I expect this 6.0 to be no big step forward, since I seriously doubt a change in Bitwigs policy to look almost desperately for new users, neglecting a real overhaul of the existing software and a thoroughly removal of existing flaws and weaknesses (this would be - btw - the very first time since Bitwigs "birth", that this company actually aims to develop existing things more towards professional usability).
More likely for me is once more a bunch of "new devices" and "workflows" (which contain once more more additional work flAws... and the need of more workarounds). Since their decision to make use of the GPU's the graphics performance has become god-awful for not few users (including myself) and there has never been any more significant work on this situation (most likely the few "real Bitwig fans" have machines without problems - what is enough for Bitwig to accept this situation). Well... I will see what happens. What ever it might be, it hardly will surprise me anymore.
More likely for me is once more a bunch of "new devices" and "workflows" (which contain once more more additional work flAws... and the need of more workarounds). Since their decision to make use of the GPU's the graphics performance has become god-awful for not few users (including myself) and there has never been any more significant work on this situation (most likely the few "real Bitwig fans" have machines without problems - what is enough for Bitwig to accept this situation). Well... I will see what happens. What ever it might be, it hardly will surprise me anymore.
- KVRian
- 1384 posts since 7 Dec, 2017
^ This dude has been complaining about Bitwig since 2019 
I would have left any DAW I'm that dissatisfied with 1 week in.
I would have left any DAW I'm that dissatisfied with 1 week in.
-JH