The reason the beta period was longer is because the changes to the audio system took time to iron out.Zikax wrote: Fri Feb 21, 2025 2:53 pm
5.3 is out now. The beta phase took quite a long time—almost 3 months.
The reason it took so long might be that they needed their resources for Bitwig 6.
Let‘s speculate about 6.0
- KVRAF
- 26935 posts since 3 Feb, 2005 from in the wilds
-
- KVRist
- Topic Starter
- 73 posts since 8 Nov, 2021
I can definitely agree that it took a lot of time. For me, beta 4 was already running well enough. They could have released 5.3 back in January and patched it gradually afterward.pdxindy wrote: Fri Feb 21, 2025 3:03 pmThe reason the beta period was longer is because the changes to the audio system took time to iron out.Zikax wrote: Fri Feb 21, 2025 2:53 pm
5.3 is out now. The beta phase took quite a long time—almost 3 months.
The reason it took so long might be that they needed their resources for Bitwig 6.
I always assume that we get three updates within about 12 months. The 5.3 beta came out in November, so Bitwig 6 could be released in April. It wouldn’t be the first time that the next beta came out just 2 to 3 months after the end of a previous beta phase.
- KVRAF
- 26935 posts since 3 Feb, 2005 from in the wilds
When they are still changing how something works, releasing it and patching it afterwards is problematic because that can break users projects/templates/presets created in the interim.Zikax wrote: Fri Feb 21, 2025 3:18 pm I can definitely agree that it took a lot of time. For me, beta 4 was already running well enough. They could have released 5.3 back in January and patched it gradually afterward.
-
- KVRist
- Topic Starter
- 73 posts since 8 Nov, 2021
The risk is always there; even after a beta phase, there’s no guarantee that everything will run smoothly. It depends on your system. That’s why they released the 5.3.1 patch just one week later.pdxindy wrote: Fri Feb 21, 2025 3:39 pmWhen they are still changing how something works, releasing it and patching it afterwards is problematic because that can break users projects/templates/presets created in the interim.Zikax wrote: Fri Feb 21, 2025 3:18 pm I can definitely agree that it took a lot of time. For me, beta 4 was already running well enough. They could have released 5.3 back in January and patched it gradually afterward.
-
- KVRist
- 202 posts since 20 May, 2020
At this point, I'd be happy if 6 just fixed the bugs.
-
- KVRist
- 312 posts since 25 May, 2021
Half year ago i raised a ticket for the Launchkey controller not working right with the native script still not repaired untill now.
Other then repairing bugs i would be happy to see slicing/warping in the sampler as said by others and me already. And the new drum devices consume way too much cpu that should be solved aswell. It is crazy how new drum machine presets suck the life out of my labtop.
-
- KVRist
- 312 posts since 25 May, 2021
Double post
-
- KVRAF
- 2623 posts since 20 Oct, 2014
Transparent clips in the arranger and maybe even notes in the pianoroll would be amazing. Maybe easy to add, too.
- KVRAF
- 9544 posts since 6 Jan, 2017 from Outer Space
Version 6 will have milestones. Either Midi 2.0 support or encapsulation with GUI elements in the Grid and Grid GUIs for the device panel.
-
- KVRist
- 247 posts since 19 Aug, 2015
That feeling when you realize that Ableton has more releases per year—and generally more useful ones—than Bitwig, despite the promise that a subscription (!) plan would boost the number of updates. And despite Bitwig crowning itself as the most innovative DAW. Shame…
-
- KVRAF
- 5056 posts since 27 Jul, 2004
Very true...vroteg wrote: Wed Mar 12, 2025 6:18 pm That feeling when you realize that Ableton has more releases per year—and generally more useful ones—than Bitwig, despite the promise that a subscription (!) plan would boost the number of updates. And despite Bitwig crowning itself as the most innovative DAW. Shame…
Since V12 AL wipes completely the floor with Bitwig... a single point update feels containing a lot better stuff than the last 10 Bitwig upates together...
I think the Bitwigs must be very careful if they can allow their own "nerdiness" for the future updates ... many former AL > now Bitwig users will switch back the more they come up with such great stuff.
If they continue with their BS updates mainly for Modular lovers, they will force a lot of people to jump train (again).
- KVRist
- 485 posts since 1 Mar, 2010
Are you seriously arguing that they should be releasing known buggy software?Zikax wrote: Fri Feb 21, 2025 3:51 pmThe risk is always there; even after a beta phase, there’s no guarantee that everything will run smoothly. It depends on your system. That’s why they released the 5.3.1 patch just one week later.pdxindy wrote: Fri Feb 21, 2025 3:39 pmWhen they are still changing how something works, releasing it and patching it afterwards is problematic because that can break users projects/templates/presets created in the interim.Zikax wrote: Fri Feb 21, 2025 3:18 pm I can definitely agree that it took a lot of time. For me, beta 4 was already running well enough. They could have released 5.3 back in January and patched it gradually afterward.
- KVRist
- 485 posts since 1 Mar, 2010
Don’t forget Ableton adding more modulators to existing devices which bitwig doesn’t need because the modulator system works everywhere.ere2learn wrote: Wed Mar 12, 2025 7:13 pm Nice features you got over there
Bounce to New Track
Vowel/Comb Filter
Chord Device
Only took 23 years, their is hope for bitwig
-
- KVRist
- 247 posts since 19 Aug, 2015
The only thing keeping me from switching and saying farewell to this program is MIDI post-instrument. If Ableton introduced MIDI Sidechain (SC) input on all devices—like they’ve already started doing for some—I’d jump ship without thinking twice. I even bought a license and tried to switch, but this little feature is too crucial for me. I’m aware of some M4L devices that can handle this, but they can be a bit buggy at times.Trancit wrote: Wed Mar 12, 2025 6:43 pm Very true...
Since V12 AL wipes completely the floor with Bitwig... a single point update feels containing a lot better stuff than the last 10 Bitwig upates together...
I think the Bitwigs must be very careful if they can allow their own "nerdiness" for the future updates ... many former AL > now Bitwig users will switch back the more they come up with such great stuff.
If they continue with their BS updates mainly for Modular lovers, they will force a lot of people to jump train (again).
Otherwise, Ableton is leading the way right now, while Bitwig is dragging behind with its head down.
And you’re right—if they keep up the “we only do what we want” mantra, they’ll eventually be left with just a handful of die-hard users… or as I call them, fanatics.
