Like every other daw... It's not like they magically appear...dellboy wrote: Sat Apr 12, 2025 2:06 pm And I believe that that the actual development started quite a few years before its launch.
Let‘s speculate about 6.0
-
- KVRian
- 1199 posts since 10 Sep, 2014
-
- KVRian
- 1199 posts since 10 Sep, 2014
Don't get me wrong. I mostly agree with what you are saying but having used other daws and Live extensively, Bitwig at version 5 has already done a lot.monolithx wrote: Sat Apr 12, 2025 8:32 am If they could fix and improve all the long time annoyances would be enough for me. Like multitrack selection settings, all the control management system, dump of VST parameters for external controllers, true values instead of %, menus UI fields, restore columns size after crash (audio engine under Windows is not stable, specially after wake up... we are in 2025...), undo mess, colors on devices headers, multi midi inputs on VST3s, multichannels, the routing sub-menus tree mess, modulations on devices buttons, windows UI management system. I don't need any new "visionary" +++ toy!
-
- KVRist
- 221 posts since 25 Sep, 2022
It was just in case the usual 2000's advice to always shutdown your DAW workstation would have come into discussion.stamp wrote: Sat Apr 12, 2025 1:46 pmWhat should this even mean? It's not like in 2025 software is easier or faster to code.
Only because other daws have gotten their acts together doesn't mean the devs don't care or whatever you might think. The other daws had more then double the time to get where they are vs Bitwig being around for only ten years...
Stuff will get fixed eventually.
It's just to speculate about 6.0 as title says, for me. What I need, what I don't and what I see. That's it. And, I come to the conclusion that the workflow is the most critical for me and for a live DAW and I see to much distraction.
-
- KVRian
- 1199 posts since 10 Sep, 2014
Well... I still do. Why ask for trouble if it takes only a handful of seconds to open daw and project?monolithx wrote: Sat Apr 12, 2025 9:30 pm
It was just in case the usual 2000's advice to always shutdown your DAW workstation would have come into discussion.
-
- KVRist
- 221 posts since 25 Sep, 2022
Not my projects. I have many VSTs among local and remote machine using VE Pro instances, external hardware and software, VJing and so on with system wide routing and configuration Windows.
-
- KVRAF
- 2772 posts since 28 Mar, 2007
Not always the case.
Justin Frankel released REAPER v0.41 on December 26 2005 as a barely functioning audio recorder. It was just the basic framework. The download was 850kb. He then released almost daily builds to the public as he designed the DAW. It's been that way right up to today. In contrast Bitwig One was a fully formed DAW on release.
-
- KVRian
- 1199 posts since 10 Sep, 2014
Is there some kind of posthumous AI cencorship on this site? I wrote 'shit' not 'acts'stamp wrote: Sat Apr 12, 2025 1:46 pmWhat should this even mean? It's not like in 2025 software is easier or faster to code.
Only because other daws have gotten their acts together doesn't mean the devs don't care or whatever you might think. The other daws had more then double the time to get where they are vs Bitwig being around for only ten years...
Stuff will get fixed eventually.
-
- KVRian
- 1199 posts since 10 Sep, 2014
Fair pointmonolithx wrote: Sat Apr 12, 2025 10:06 pm Not my projects. I have many VSTs among local and remote machine using VE Pro instances, external hardware and software, VJing and so on with system wide routing and configuration Windows.
-
- KVRian
- 1199 posts since 10 Sep, 2014
Fair pointdellboy wrote: Sat Apr 12, 2025 11:13 pmNot always the case.
Justin Frankel released REAPER v0.41 on December 26 2005 as a barely functioning audio recorder. It was just the basic framework. The download was 850kb. He then released almost daily builds to the public as he designed the DAW. It's been that way right up to today. In contrast Bitwig One was a fully formed DAW on release.
-
- KVRian
- 1199 posts since 10 Sep, 2014
-
- KVRist
- 221 posts since 25 Sep, 2022
In this Bitwig vs DAWs history comparison, I have followed (doesn't mean tried) almost all DAWs market since v. 1 and I don't remember new noticeable releases where more than the half of the release note was full of (fancy) devices and features so poorly improved after they have been issued.
Just to clarify my thoughts. I suspect Bitwig to take some advanced Teenage Engeneering marketing way with some modular hype in it and I don't like it. My thoughts...
One more word regarding devices, the Devices panel is just to limited for an efficient device UI. I think it's more or less related to integration with controllers but it causes many limitations and I don't see any improvement.
Just to clarify my thoughts. I suspect Bitwig to take some advanced Teenage Engeneering marketing way with some modular hype in it and I don't like it. My thoughts...
One more word regarding devices, the Devices panel is just to limited for an efficient device UI. I think it's more or less related to integration with controllers but it causes many limitations and I don't see any improvement.
-
- KVRian
- 1199 posts since 10 Sep, 2014
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. Now that the structural stuff is out of the way they will continue with improving the more tangible side of the daw. Just a wild guess and what I hope...monolithx wrote: Sun Apr 13, 2025 6:36 pm In this Bitwig vs DAWs history comparison, I have followed (doesn't mean tried) almost all DAWs market since v. 1 and I don't remember new noticeable releases where more than the half of the release note was full of (fancy) devices and features so poorly improved after they have been issued.
Just to clarify my thoughts. I suspect Bitwig to take some advanced Teenage Engeneering marketing way with some modular hype in it and I don't like it. My thoughts...
One more word regarding devices, the Devices panel is just to limited for an efficient device UI. I think it's more or less related to integration with controllers but it causes many limitations and I don't see any improvement.
-
- KVRAF
- 1769 posts since 1 Mar, 2010 from Paris
I sometimes really wish I could detach the stock stuff from the device panel and use a x2 or x3 zoom on the floating windows.
It bugs me I have to scale the entire interface to make the devices bigger.
It bugs me I have to scale the entire interface to make the devices bigger.
-
- KVRAF
- 3812 posts since 20 Apr, 2005
I shut my DAW PC when I'm done too.
But when I'm using Bitwig I can often have 9-10 projects open at once and be very happily skipping between them.
(Maybe 30-40s to switch, but I think that's reasonable when I have a full project with many many plugins and VSTs.)