I might cry a bit if a 5.4 was announced.
Let‘s speculate about 6.0
-
- KVRAF
- 5573 posts since 30 May, 2006 from Hollow Earth
- KVRAF
- 2673 posts since 18 Mar, 2006 from The Void
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.
(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.
- KVRist
- 485 posts since 1 Mar, 2010
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.
They could end up better than those other modular environments.
- KVRAF
- 26941 posts since 3 Feb, 2005 from in the wilds
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.coroknight wrote: Mon Jul 21, 2025 6:18 pm They could end up better than those other modular environments.
If I'm going to have to cable everything, I prefer to do that in my hardware modular (which also sounds better)
- KVRAF
- 2673 posts since 18 Mar, 2006 from The Void
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.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 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.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)
As for hardware modular, that's out of reach for many.
-
- KVRian
- 875 posts since 22 Jan, 2022
Please Bitwig, do this and let me finally put Reaper into the dustbin of history!!!!
Would be very nice for sure.
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?
-
- KVRian
- 759 posts since 26 Sep, 2007
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".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?
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".
- KVRist
- 485 posts since 1 Mar, 2010
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.
- KVRAF
- 26941 posts since 3 Feb, 2005 from in the wilds
Seems like it would have to be a new standard to integrate into Bitwig's Grid... including polyphony, voice stacking, note expressions, etc.koalaboy wrote: Tue Jul 22, 2025 9:01 amI 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'.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.
- KVRAF
- 2673 posts since 18 Mar, 2006 from The Void
True. Now that you mention those things. It would be nice to *have* a common standard for 'virtual modular' though.pdxindy wrote: Tue Jul 22, 2025 2:34 pmSeems like it would have to be a new standard to integrate into Bitwig's Grid... including polyphony, voice stacking, note expressions, etc.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'.
-
- KVRAF
- 16733 posts since 13 Oct, 2009
koalaboy wrote: Tue Jul 22, 2025 3:00 pmTrue. Now that you mention those things. It would be nice to *have* a common standard for 'virtual modular' though.pdxindy wrote: Tue Jul 22, 2025 2:34 pmSeems like it would have to be a new standard to integrate into Bitwig's Grid... including polyphony, voice stacking, note expressions, etc.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'.

-
machinesworking machinesworking https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=8505
- KVRAF
- 7990 posts since 15 Aug, 2003 from seattle
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.
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.
- KVRAF
- 2673 posts since 18 Mar, 2006 from The Void
Exactly.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.
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.
