I don't think this reasoning holds up. There's no reason why they'd stop adding new and updated devices. I think people here underestimate how important these are to the overall selling proposition of a product like Bitwig, they're not just "filler" while the plumbing of the DAW is worked on. It's more of a permanent sidetrack of development with independent design and dev phases. So the people working on the devices likely don't work on the core DAW.stamp wrote: Sun Apr 13, 2025 8:42 pm I think that they gave us all the + devices while doing all the stuff in the background like graphics and audio engine stuff just so people get something in the meantime.
Let‘s speculate about 6.0
-
- KVRian
- 759 posts since 26 Sep, 2007
- KVRian
- 1199 posts since 10 Sep, 2014
You're right, too.Dionysos wrote: Mon Apr 14, 2025 2:12 pmI don't think this reasoning holds up. There's no reason why they'd stop adding new and updated devices. I think people here underestimate how important these are to the overall selling proposition of a product like Bitwig, they're not just "filler" while the plumbing of the DAW is worked on. It's more of a permanent sidetrack of development with independent design and dev phases. So the people working on the devices likely don't work on the core DAW.stamp wrote: Sun Apr 13, 2025 8:42 pm I think that they gave us all the + devices while doing all the stuff in the background like graphics and audio engine stuff just so people get something in the meantime.
-
machinesworking machinesworking https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=8505
- KVRAF
- 7985 posts since 15 Aug, 2003 from seattle
I mean it's not a mystery that people worry about the UX and core DAW features when most DAWs including Bitwig tend to focus on plugins over core DAW features. The next version is supposed to be about core DAW features, so we will see how it goes.stamp wrote: Mon Apr 14, 2025 2:37 pmYou're right, too.Dionysos wrote: Mon Apr 14, 2025 2:12 pmI don't think this reasoning holds up. There's no reason why they'd stop adding new and updated devices. I think people here underestimate how important these are to the overall selling proposition of a product like Bitwig, they're not just "filler" while the plumbing of the DAW is worked on. It's more of a permanent sidetrack of development with independent design and dev phases. So the people working on the devices likely don't work on the core DAW.stamp wrote: Sun Apr 13, 2025 8:42 pm I think that they gave us all the + devices while doing all the stuff in the background like graphics and audio engine stuff just so people get something in the meantime.
We all have our wishes, I wish Bitwig would write to Ableton Live Sets, not just translate them to Bitwig format, if this was the case I could use Bitwig to write Sets for Push 3 standalone. No doubt it's not a priority, Bitwig can't afford to spend time translating Bitwig Sampler to Lives sampler, drum to drum, and that's all that would really work anyway besides Clips.
-
- KVRist
- 221 posts since 25 Sep, 2022
I don't agree. Plugins came after most DAWs were quite improved as must have. Just compare the number of customization settings and you will notice how poor it's in Bitiwig compared to others. But, I know the trend is to "click" music that sounds the same way as it was generated by AI. It's a general music production problem. I like MAX MSP, but I don't like Live. The promised Bitwig and Grid are a failure for me.machinesworking wrote: Mon Apr 14, 2025 4:53 pm I mean it's not a mystery that people worry about the UX and core DAW features when most DAWs including Bitwig tend to focus on plugins over core DAW features. The next version is supposed to be about core DAW features, so we will see how it goes.
-
machinesworking machinesworking https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=8505
- KVRAF
- 7985 posts since 15 Aug, 2003 from seattle
Sorry, Bitwig probably isn't for you. That's fine there are other DAWs. Bitwig follows suite with Live in a lower level of customization in favor of a generally higher level of intuitive UX.monolithx wrote: Mon Apr 14, 2025 7:11 pmI don't agree. Plugins came after most DAWs were quite improved as must have. Just compare the number of customization settings and you will notice how poor it's in Bitiwig compared to others. But, I know the trend is to "click" music that sounds the same way as it was generated by AI. It's a general music production problem. I like MAX MSP, but I don't like Live. The promised Bitwig and Grid are a failure for me.machinesworking wrote: Mon Apr 14, 2025 4:53 pm I mean it's not a mystery that people worry about the UX and core DAW features when most DAWs including Bitwig tend to focus on plugins over core DAW features. The next version is supposed to be about core DAW features, so we will see how it goes.
If you need a DAW that isn't "click" music, or to a grid, the old school ones are the current best choices, i.e. Logic, DP, and I'm pretty sure Cubase and Reaper both have features for more free form music production.
- KVRAF
- 3812 posts since 20 Apr, 2005
Not sure that's fair. Bitwig itself is pretty much all a cohesive set of DAW features.machinesworking wrote: Mon Apr 14, 2025 4:53 pm I mean it's not a mystery that people worry about the UX and core DAW features when most DAWs including Bitwig tend to focus on plugins over core DAW features. The next version is supposed to be about core DAW features, so we will see how it goes.
The plug ins are a different stream of work, and it can't be denied it's, for better or worse, a key DAW metric. I don't use a lot of the audio FX, but the modulators and other midi/controller type stuff is insanely good.
Of course there are some DAW functions people want, and I hope they come along, but it's not like the haven't been adding them over time.
The most recent batch of 'core' develop seems to be the mainly invisible type. ARM support, UI update, audio engine update, CLAP. Things that no doubt too a lot of effort but are long term impacts.
-
machinesworking machinesworking https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=8505
- KVRAF
- 7985 posts since 15 Aug, 2003 from seattle
and those are super important too, but I think for every DAW I’ve ever used there’s a list of core flashy features that people want, things like retrospective record, a groove pool, automatic tempo adjustment to free form music like this guy seems to want etc. that people always think get overlooked for plugins etc. That wa ll I was trying to say._leras wrote: Mon Apr 14, 2025 9:47 pm The most recent batch of 'core' develop seems to be the mainly invisible type. ARM support, UI update, audio engine update, CLAP. Things that no doubt too a lot of effort but are long term impacts.
-
- KVRAF
- 2623 posts since 20 Oct, 2014
When do you think a Bitwig 5.4 beta will be announced? The sale already has ended... Can't remember the last years pattern 
-
- KVRer
- 18 posts since 25 Sep, 2024
It is expected to be released in mid-MayHanz Meyzer wrote: Wed Apr 23, 2025 10:36 am When do you think a Bitwig 5.4 beta will be announced? The sale already has ended... Can't remember the last years pattern![]()
-
- KVRAF
- 2623 posts since 20 Oct, 2014
Ah yes, very logical. Sadly my update plan runs out at end of April, for some stupid reason... Should be after Superbooth of course... Ah, I don't like these plans at all....
- KVRAF
- 3812 posts since 20 Apr, 2005
There just isn't an open standard for this. I'm sure if Ableton didnt like Bitwig reading their file format they could easily tweak it and break that functionality.machinesworking wrote: Mon Apr 14, 2025 4:53 pm
We all have our wishes, I wish Bitwig would write to Ableton Live Sets, not just translate them to Bitwig format, if this was the case I could use Bitwig to write Sets for Push 3 standalone. No doubt it's not a priority, Bitwig can't afford to spend time translating Bitwig Sampler to Lives sampler, drum to drum, and that's all that would really work anyway besides Clips.
It's such a pain also that there isn't an open drum machine/kit format. People will make kontakt and Ableron kits, but Bitwig and others simply don't get the kits in that format. Very annoying.
Made slightly worse by wave alchemys wonderful triaz that adds a fade between three sounds on a pad in another closed format, that would stretch a 'standard' format anyway.
-
machinesworking machinesworking https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=8505
- KVRAF
- 7985 posts since 15 Aug, 2003 from seattle
DAWproject hopefully eventually gets universally adopted. Meanwhile bought Chicken Systems Translator and it does a decent job but no Bitwig format, so to get from UVI to Bitwig Sampler is Translator 7 UVI to one of Moss's translator formats then to Bitwig sampler from his translator. Reminds me to ask Moss to support UVI._leras wrote: Thu Apr 24, 2025 10:15 am There just isn't an open standard for this. I'm sure if Ableton didnt like Bitwig reading their file format they could easily tweak it and break that functionality.
It's such a pain also that there isn't an open drum machine/kit format. People will make kontakt and Ableron kits, but Bitwig and others simply don't get the kits in that format. Very annoying.
Made slightly worse by wave alchemys wonderful triaz that adds a fade between three sounds on a pad in another closed format, that would stretch a 'standard' format anyway.
-
- KVRAF
- 2772 posts since 28 Mar, 2007
The only feature that I want in Bitwig Studio 6 is the ability to turn off all notifications at startup. I am not interested that a new version is available. Nor do I want to install any of the packages offered. I find it irritating to have to click the notifications off every time I boot Bitwig Studio up. Why is it not possible in a professional DAW to switch this stuff off?
-
- KVRAF
- 2056 posts since 13 Dec, 2016
One thing that still really bothers me about Bitwig is the way it handles plugin windows. Unlike basically every other DAW, Bitwig doesn't remember the size or position of plugin editors when reopening a project. Every time I reopen a session, all my plugins stack up or reset to random positions, no matter where I placed them before saving. It's super frustrating, especially when working on complex projects and templates with dozens of plugins open.
I've already contacted support about this a while ago, but so far nothing has changed.
Am I the only one with this issue? I´m on a WIN11 machine
I've already contacted support about this a while ago, but so far nothing has changed.
Am I the only one with this issue? I´m on a WIN11 machine
Its over for Bitwig--CUBASE WON !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
