Let‘s speculate about 6.0

Official support for: bitwig.com
Post Reply New Topic
RELATED
PRODUCTS

Post

pdxindy wrote: Thu Jul 17, 2025 10:05 am Bitwig updates:
2.5 -> 3
3.3 -> 4
4.4 -> 5
I might cry a bit if a 5.4 was announced. :hihi:

Post

_leras wrote: Sun Jul 20, 2025 12:36 pm
pdxindy wrote: Thu Jul 17, 2025 10:05 am Bitwig updates:
2.5 -> 3
3.3 -> 4
4.4 -> 5
I might cry a bit if a 5.4 was announced. :hihi:
Especially if a 5.4 is labeled 6.0 :hihi:
ABEFLGMOPPRRST :phones:

Post

Maybe it'll be a major minor release and they'll go straight to 5.5, it'll blow people's minds!

Post

The more I think about it, they should 'just' make the grid become a VCV module host, API compatible.

(I'm not saying it's easy). Or maybe work with Cherry Audio who already are also heavily invested in Java aspects - heck, that could be an amazing partnership.

Everything needs to be more modular these days, as otherwise it's just more marketing locking consumers in, which is the opposite of what most people want.

Post

That would be a huge mistake. I like that the grid isn’t trying to look like a eurorack and as a result is far easier and less clunky to use. They should just open the grid up to third-party modules.

They could end up better than those other modular environments.

Post

coroknight wrote: Mon Jul 21, 2025 6:18 pm They could end up better than those other modular environments.
For me, the Grid is already better than the eurorack lookalikes. I find those ones, like VCV, cross the threshold of tediousness such that I just stop using them.

If I'm going to have to cable everything, I prefer to do that in my hardware modular (which also sounds better)

Post

coroknight wrote: Mon Jul 21, 2025 6:18 pm That would be a huge mistake. I like that the grid isn’t trying to look like a eurorack and as a result is far easier and less clunky to use. They should just open the grid up to third-party modules.
I guess I meant in the way that there is a well-known (and understood) API with a wide community set of modules already. If those could be adapted, then fine, but a completely 'new' API means starting again with yet another 'standard'. I agree that Eurorack can feel cluttered at times.
pdxindy wrote: Tue Jul 22, 2025 4:04 am For me, the Grid is already better than the eurorack lookalikes. I find those ones, like VCV, cross the threshold of tediousness such that I just stop using them.

If I'm going to have to cable everything, I prefer to do that in my hardware modular (which also sounds better)
I definitely would prefer wires into/out of the sides of the modules in the UI (like the Grid) more than a Eurorack emulation. I'm just thinking how nice it would be to tap into the already huge community of modules.

As for hardware modular, that's out of reach for many.

Post

gulugulufish wrote: Thu Jul 10, 2025 7:39 pm 6. ARA2 support
Please Bitwig, do this and let me finally put Reaper into the dustbin of history!!!!
gulugulufish wrote: Thu Jul 10, 2025 7:39 pm 3. midi comping
Would be very nice for sure.
gulugulufish wrote: Thu Jul 10, 2025 7:39 pm 1. midi capture
Can someone explain why this is so important to people? Why not just hit the record button? I feel like I'm missing the actual use case here... is it useful for live performance or some other reason?

Post

billinder33 wrote: Tue Jul 22, 2025 1:00 pmCan someone explain why this is so important to people? Why not just hit the record button?
Apart from making it trivial to capture happy accidents, I think it also helps with a mild form of performance anxiety, maybe? I consistently play better when I'm not recording. As soon as I hit record, I tense up and usually need a few tries before I get something that I would've played effortlessly when "just noodling".

I suspect I'm not alone with this as Ableton have built a whole app around this. In their Note app, you never press "Record", you only ever press "Capture what I just played".

Post

I just hope they add midi capture and midi comping so people will stop asking for them all the time.
Last edited by coroknight on Tue Jul 22, 2025 2:34 pm, edited 1 time in total.

Post

koalaboy wrote: Tue Jul 22, 2025 9:01 am
coroknight wrote: Mon Jul 21, 2025 6:18 pm That would be a huge mistake. I like that the grid isn’t trying to look like a eurorack and as a result is far easier and less clunky to use. They should just open the grid up to third-party modules.
I guess I meant in the way that there is a well-known (and understood) API with a wide community set of modules already. If those could be adapted, then fine, but a completely 'new' API means starting again with yet another 'standard'.
Seems like it would have to be a new standard to integrate into Bitwig's Grid... including polyphony, voice stacking, note expressions, etc.

Post

pdxindy wrote: Tue Jul 22, 2025 2:34 pm
koalaboy wrote: Tue Jul 22, 2025 9:01 am I guess I meant in the way that there is a well-known (and understood) API with a wide community set of modules already. If those could be adapted, then fine, but a completely 'new' API means starting again with yet another 'standard'.
Seems like it would have to be a new standard to integrate into Bitwig's Grid... including polyphony, voice stacking, note expressions, etc.
True. Now that you mention those things. It would be nice to *have* a common standard for 'virtual modular' though.

Post

koalaboy wrote: Tue Jul 22, 2025 3:00 pm
pdxindy wrote: Tue Jul 22, 2025 2:34 pm
koalaboy wrote: Tue Jul 22, 2025 9:01 am I guess I meant in the way that there is a well-known (and understood) API with a wide community set of modules already. If those could be adapted, then fine, but a completely 'new' API means starting again with yet another 'standard'.
Seems like it would have to be a new standard to integrate into Bitwig's Grid... including polyphony, voice stacking, note expressions, etc.
True. Now that you mention those things. It would be nice to *have* a common standard for 'virtual modular' though.
Image

Post

I have no idea why no DAW developer I know of has implemented the sort of system that NI did for Reaktor where users created something like 6000 Ensembles for sharing? Easily consolidated on their site.

In the case of Bitwig, Device Panels, patches for the embedded instruments and FX, Grid creations, scripts etc. it's all just scattered over the internet. Same with Reaper, or any other DAW.

Post

machinesworking wrote: Tue Jul 22, 2025 3:11 pm I have no idea why no DAW developer I know of has implemented the sort of system that NI did for Reaktor where users created something like 6000 Ensembles for sharing? Easily consolidated on their site.

In the case of Bitwig, Device Panels, patches for the embedded instruments and FX, Grid creations, scripts etc. it's all just scattered over the internet. Same with Reaper, or any other DAW.
Exactly.

Whilst the xkcd comic is funny, there is no real standard for this which is a shame. Steinberg took over the world with VST, and CLAP tries to bring that out of the corporate world, but there's nothing really for modules and it would be an amazing thing to have.

Post Reply

Return to “Bitwig”