Let‘s speculate about 6.0

[Dionysos]

The latest newsletter settles the debate. Bitwig is for innovators!

Screenshot 2025-07-11 at 11.38.05.png

[coroknight]

Sounds about right.

[perpetual3]

I don’t think I’ve come across so much proactive hate for a DAW before.

[coroknight]

It’s just a bunch of self-centered people on a power trip thinking they can bully a small developer.

[gulugulufish]

What does aliased clips mean? When a clip is dragged/extended it just loops which is almost like a ghost/alias?

Yeah it's just like looping a clip, but it can presumably be after another clip or a gap.

[gulugulufish]

^Probably some of the largest "producers" on youtube choosing Bitwig as their main DAW. A couple professional producers with large swaths of people who want to be like them wouldn't hurt either.

People want to use what their music heroes are using, and or what most people are using, in general.

I'm guilty.

Yeah for sure that makes sense. I feel like I see even more big electronic producers using logic than bitwig. Definitely some big names using it but it would but I'm just surprised there aren't more at this point

[machinesworking]

Yeah, it's kind of hard to say. I think what we've seen is that many of our customers already have another DAW. They maybe have Pro Tools or Cubase or Logic, more linear DAW, but they want to try something that is totally different, and they come to us.

[/quote]

This they even admit. They're already working on an ecosystem for better transfers between DAWs with CLAP and DAWProject. I still have no idea why rewire never got immediately replaced with something even better? Ableton Link is only a sync protocol for example. At least on Mac OS there are already enough open source projects to cobble together a rewire substitute, (blackhole, Jack, IAC) and I'm certain the same could be said for Windows. As mentioned earlier a new more robust protocol for linking two DAWs would help to give Bitwig the push it needs to compete with the established 5 dominant DAWs. The only answer that makes sense to me is it must be harder than I'm making it out to be? because for a company like Bitwig it would help facilitate their own growth.

[machinesworking]

I don’t think I’ve come across so much proactive hate for a DAW before.

Believe me Digital Performer gets this sort of hate, but yeah it's always ridiculous. We're in a golden age with so many DAWs and none of them are awful at all. I guess I must be different that way? I'm a huge admirer of what Bitwig does, even if I need the toolsets of DP and Live.

[Junkyard Sam]

The long-term investments Bitwig did, like that graphics-engine overhaul, are a BIG deal. That bodes well for the future as long as we continue to support.

A lot of times a software DOESN'T get kind of that deep level attention that will pay off in the long run -- specifically because users will be so unappreciative and drop off because they can't see the long term value.

Based on the 5.x updates, I have a feeling 6.x is going to be huge and impressive. The Bitwig team knows what they are facing, both from the fans(and haters) as well as the competition, and they're going to deliver big. As big as they possibly can with the resources they have to work with.

We all bought Bitwig because there was something about it we adored. The same team that knew how to get the product to that point is still evolving it for the future. This public drama isn't doing us any good... If you love a product you should focus on what's great about it, to draw new people in. More users means more resources to invest in future development.

I live in two DAWs. Reaper & Bitwig. They are almost polar opposites of one another, and each has me wishing the other had some of its features... But instead of hating either one of them, I appreciate what's good about both! This is the way.

Bitwig 6 will be great. They 'invested in the future' with that graphics overhaul. This time they'll deliver fundamentals. If you want Bitwig to do well, keep your update plan going... Or at least come back when they deliver something you appreciate. They will, soon.

[TheYke]

At least on Mac OS there are already enough open source projects to cobble together a rewire substitute, (blackhole, Jack, IAC)

Just to be a bit pedantic: Jack (as in "Jack Audio Connection Kit", that is) is an open source audio server with inter-app connectivity mainly driven by the Linux community, and it's even available on Windows, too.
It's awesome. I have it setup as a full replacement for retrospective midi and audio recording on Linux, for example.

[questionaire]

After going back and forward bewteen Bitwig and Ableton, i came to the conclusion. Bitwig is for my workflow better and it runs on Linux so stable and with lower latency. I can trust Bitwig while going live. What i mainly dislike about Bitwig is its lack of controller support. I have sent them several bug reports for the novation launchkey and the akai apc mini mk2. They simply do not see the importance of it.
3 times sent a report spanning a year and they have confirmed i'm right with the found bugs but until now no action from their side. I wish they would listen better to their customers and their wishes. I think that makes the users angry or frustrated.

Overall i'm happy with Bitwig. I have tried Presonus studio one and Cubase aswell. All have their drawbacks.

Hopefully Bitwig will adress a lot of user requests with the version 6.0! Lets see what it will bring.

[koalaboy]

Reaper has Reascript built in.
Ableton live has long had Max (which has several scripting capabilities).
Recently renoise gained Phrase Scripting in LUA.
Now FLStudio gets Patcher Scripting in Python (even better !)

Bitwig really would be superb with a scripting node in the grid. Python would be a dream come true.

It's clear that other DAWs are embracing this capability now.

[coroknight]

If they officially opened up Nitro scripting that would be killer. The problem with languages like JavaScript, python, and lua is they aren’t particularly great at real-time audio processing because they’re interpreted and garbage collected.

Clearly they can do it to some extent, but embracing a language built for hardcore realtime audio processing would be killer.

[koalaboy]

If they officially opened up Nitro scripting that would be killer. The problem with languages like JavaScript, python, and lua is they aren’t particularly great at real-time audio processing because they’re interpreted and garbage collected.

Clearly they can do it to some extent, but embracing a language built for hardcore realtime audio processing would be killer.

Well, ideally it would be full on WASM/WASI and then any language that compiles to WASM would be fine. Of course, there is then the tooling and perhaps not the greatest UX.

There's a careful balance between performance and usability, although they already manage that to some extent with a UI in Java, but this is likely one of the main reasons it hasn't happened yet.

[coroknight]

A built-in WASM plugin system would also be awesome. Although you would still have the same language limitations, so WASM isn’t a silver bullet to make interpreted languages like Python faster.

Ideally we would have options, and hopefully one of those options is something built for fast, real time applications.