Let‘s speculate about 6.0
- KVRAF
- 4803 posts since 21 Jan, 2008 from oO
Scale lock maybe, because there is the word “inor” on the grid.
JamWide - a cross-platform Ninjam client for DAWs
-
- KVRist
- 144 posts since 31 Jan, 2017
Scale/chord support is my biggest wishlist item. That might even go as far as DAW-level MTS-ESP integration, in terms of tuning. (There are Open Source tools which bring MTS-ESP support fairly deep into BWS. Just wishing for a full integration.)
Was thinking of letting my upgrade plan run out. The recent updates haven't done much for me, in part because I'm less tied to DAW features, especially if they only work on desktop. With Logic Pro for iPadOS and now Loopy Pro, desktop DAWs have less appeal to me.
Plus, I started vibecoding my own plugins. Well, ok, one VST3/AU so far. In some ways quite limited. In others, much more enabling than anything I’d do in the Grid.
So, despite how big of an improvement this new beta is likely to be, I’m not entirely sure I’ll renew my upgrade plan while the discount lasts (three weeks before the new beta). Would save $40 compared to the usual price. Though I could also wait for other sales, once BWS6 is fully stable.
In the past, bundle sales have been decent deals. That’s how I got u-he Hive 2, which is among my favourite softsynths. Would never have bought it on its own, as I have way too many synths already.
So, like others, I’m a bit torn. I could invest another $130 (178CAD) to invest more time in the platform as I’m doing other things. Or I could keep using the plugin host as I’m creating more stuff for my own needs on a variety of platforms. (If I end up creating an AUv3 version of my one plugin, I basically want to spend less time on a desktop DAW).
All this to say…
Yes, it’s exciting. The timing isn't as good as it could be.
Wish we had just a tiny bit more info to make a decision.
Was thinking of letting my upgrade plan run out. The recent updates haven't done much for me, in part because I'm less tied to DAW features, especially if they only work on desktop. With Logic Pro for iPadOS and now Loopy Pro, desktop DAWs have less appeal to me.
Plus, I started vibecoding my own plugins. Well, ok, one VST3/AU so far. In some ways quite limited. In others, much more enabling than anything I’d do in the Grid.
So, despite how big of an improvement this new beta is likely to be, I’m not entirely sure I’ll renew my upgrade plan while the discount lasts (three weeks before the new beta). Would save $40 compared to the usual price. Though I could also wait for other sales, once BWS6 is fully stable.
In the past, bundle sales have been decent deals. That’s how I got u-he Hive 2, which is among my favourite softsynths. Would never have bought it on its own, as I have way too many synths already.
So, like others, I’m a bit torn. I could invest another $130 (178CAD) to invest more time in the platform as I’m doing other things. Or I could keep using the plugin host as I’m creating more stuff for my own needs on a variety of platforms. (If I end up creating an AUv3 version of my one plugin, I basically want to spend less time on a desktop DAW).
All this to say…
Yes, it’s exciting. The timing isn't as good as it could be.
Wish we had just a tiny bit more info to make a decision.
-
- KVRAF
- 5144 posts since 3 Oct, 2013
^^^ I think it’s a good strategy, but tell me if it’s not. Grab the update from the store now while it’s still discounted, but don’t activate it yet. Then, once the first beta is out, test it via Splice for $16 for a month, and if it actually includes features that are genuinely useful, activate the update the following month.
Of course, odds are the hype train will run over and activate it the second the first beta lands — but, let’s pretend we won’t.
Of course, odds are the hype train will run over and activate it the second the first beta lands — but, let’s pretend we won’t.
"Where we're workarounding, we don't NEED features." - powermat
-
- KVRist
- 70 posts since 10 Mar, 2022
It makes sense if you think about it, because you want to be able to carry on the value of a parameter between clips, and if so, it should probably be visualized in some way, so why not mix clips and track level automation so you can perfectly visualize which value has taken hold? And hopefully they will allow the addition of the "+" and "x" automation types we already have in clip-level automation editingcoroknight wrote: Mon Jul 28, 2025 8:30 pmIt looks like a hybrid of the current system and automation clips. I’m guessing by default it functions like normal automation lanes but then you can select a chunk of automation to create a clip.
-
- KVRist
- 241 posts since 16 May, 2012 from Sverige
i hope they put some effort into the midi editor, and automation workflow. One of the reason why I went fully back to Ableton is the lack of good keyboard workflow in those areas, actually dont miss any of Bitwigs selling points over Ableton because I can overcome them easier than the lack of fast workflow in these areas in the way I work.
- KVRAF
- 3812 posts since 20 Apr, 2005
You can buy an upgrade and not activate it immediately.wintoid wrote: Mon Jul 28, 2025 8:19 pm
I'm one of those nutters who usually keeps his upgrade plan active regardless. I'm definitely verging on Bitwig fanboy. It was annoying to me to see some recent promotions which would only get you benefits if you upgraded with another update plan, and I already had over a year of plan outstanding.
I don't usually install betas anyway. But thanks for all the input. Just one of those mild irritations.
-
- KVRist
- 65 posts since 9 Oct, 2015
Bitwig had already announced that the update to 6.0 was about workflow improvements
-
- KVRist
- 409 posts since 6 Apr, 2014
I've got one in my back pocket, purchased from JRR. Wondering actually if I can register it on the Bitwig site without starting it, but I can just hang on to the code until I need to I guess.
-
- KVRist
- 436 posts since 26 Jul, 2012 from Prague, czech republic
I can't wait.. But it looks we are still not getting automation clips. I would just steal everything from FL Studio TBH.
-
- KVRist
- 386 posts since 21 Jun, 2019
It totally looks like they added automation clips. Just check the image posted earlier. There are clip handles only on the automation part of a track. Why does it look like automation clips? Because the track itself seems to be a single clip. If it were just regular clips, I would not expect them to stick out, it would just be a regular clip block on the same level as the original clip.fwsuperhero wrote: Tue Jul 29, 2025 10:41 am But it looks we are still not getting automation clips.
-
- KVRist
- 70 posts since 10 Mar, 2022
Yeah, I can't imagine that being anything BUT automation clips.muzicxs wrote: Tue Jul 29, 2025 1:15 pmIt totally looks like they added automation clips. Just check the image posted earlier. There are clip handles only on the automation part of a track. Why does it look like automation clips? Because the track itself seems to be a single clip. If it were just regular clips, I would not expect them to stick out, it would just be a regular clip block on the same level as the original clip.fwsuperhero wrote: Tue Jul 29, 2025 10:41 am But it looks we are still not getting automation clips.
-
- KVRist
- 70 posts since 10 Mar, 2022
Just checking, did you see the "Precision Editing" keyboard workflow improvements that came with bitwig 5.2? I don't know ableton well enough but I find the current shortcuts pretty useful. Chopping is one area that takes a few more clicks in bitwig however, cause you have to do an operator and then slice it.backtomusic wrote: Tue Jul 29, 2025 6:29 am i hope they put some effort into the midi editor, and automation workflow. One of the reason why I went fully back to Ableton is the lack of good keyboard workflow in those areas, actually dont miss any of Bitwigs selling points over Ableton because I can overcome them easier than the lack of fast workflow in these areas in the way I work.
-
- KVRian
- 759 posts since 26 Sep, 2007
I'm quite excited about this!
Very curious about the linked clips, wonder if the number before the clip name identifies the clip instance? It seems to coincide with the bar number for some of the clips.
I wonder how much the piano roll usability was tweaked beyond the scale feature.
I don't expect full theme support, it might just be an option to make the arranger background dark (which would be fine with me).
Very curious about the linked clips, wonder if the number before the clip name identifies the clip instance? It seems to coincide with the bar number for some of the clips.
I wonder how much the piano roll usability was tweaked beyond the scale feature.
I don't expect full theme support, it might just be an option to make the arranger background dark (which would be fine with me).
