Let‘s speculate about 6.0

[pdxindy]

One thing that I'd love to see (but think is unlikely to happen) would be for the audio clip editor to gain multiple lanes, to make it possible for a clip to have polyphonic events, and for events to be moved around without them necessarily erasing what's underneath.

Numerous times I've wished that Comped Clips could have some sort of logic to realtime switch between take lanes. Maybe like Operators. So a single event could randomly switch between take lanes, etc.

[Dionysos]

That sounds useful, too.

[coroknight]

Kinda like a clip selector container.

[Echoes in the Attic]

How would that work with multi-samples?

Add the time stretch parameter per sample mapping instead of as a setting on the whole device?

In Ableton, Sampler, which does multi-samples, doesn't have timestretching. It is Ableton's Simpler that has timestretching. It is the same thing with slicing which is only in Simpler.

I've sorta assumed Bitwig would need their version of Simpler to add timestretch and slicing.

Kontakt and Tal Sampler are a couple examples of samplers with timestretch and multi-samples.

[krankyone]

What I want, and can't figure out why it's never been implemented, is a setting to be able to toggle start/stop on clips with a press. Hunting for the stop button on a large project is awkward, and it's even worse when using a control surface with pads, like a Push or Launchpad.

[duanosforde]

In Ableton, Sampler, which does multi-samples, doesn't have timestretching.

I believe that's just an arbitrary technical limitation of how Live originally implemented Simpler and Sampler as separate things (with Sampler having a bunch of licensed code for its multi-sampling implementation.)

I'm not seeing why a sampler can't have timestretching. Like I said, just have stretch mode as a parameter for each zone or sample mapping. It would work without any problem. If you think that wouldn't work, feel free to let me know why it wouldn't. (I know that it works, because there are already samplers that do this.)

Your idea sounds good. I'd welcome the ability to timestretch individual samples in Sampler. It would make for some interesting layering, even with unstretched versions of the same sample.

I was kinda imagining a large multi-sample and trying to stretch all the samples en-mass. Seems like a CPU killer.

I wonder if timestretch modulation would be possible?

I do mult-isample timestretching in UVI falcon just fine. Barely touches CPU. It even has multiple stretch algorithms to play with (ICRAM, granular, scrub, etc). So it is possible, i guess. not sure how easily it could be implemented in bitwig though.

[slackhead]

How would that work with multi-samples?

Add the time stretch parameter per sample mapping instead of as a setting on the whole device?

In Ableton, Sampler, which does multi-samples, doesn't have timestretching. It is Ableton's Simpler that has timestretching. It is the same thing with slicing which is only in Simpler.

I've sorta assumed Bitwig would need their version of Simpler to add timestretch and slicing.

Kontakt and Tal Sampler are a couple examples of samplers with timestretch and multi-samples.

Add Geist and Geist 2 to that list.

[strovoknights]

I anticipate that the beta program for Bitwig 6.0 will begin in the fall of 2025, that the official 6.0 release will be launched by the end of 2025, and that Bitwig 6.0 will be showcased at NAMM in January 2026.

[slackhead]

I anticipate that the beta program for Bitwig 6.0 will begin in the fall of 2025, that the official 6.0 release will be launched by the end of 2025, and that Bitwig 6.0 will be showcased at NAMM in January 2026.

I suspect (with my cynical hat on) that they will announce the Beta once the current sale has finished, with a view that that will generate extra sales

[koalaboy]

I 'just' want vst3 devices available in the grid. That's it. I know I can 'workaround' to some extent using sends/receives and putting multiple grids etc... but it's just such a mess. Let me drop one or more vst3 devices in the grid, and connect them all up there, along with the other flexibility that exists. It's so close to being able to replace many other hosts/wrappers...

I don't expect it will happen, but I will forever hope.

[liquidsound]

I 'just' want vst3 devices available in the grid. That's it. I know I can 'workaround' to some extent using sends/receives and putting multiple grids etc... but it's just such a mess. Let me drop one or more vst3 devices in the grid, and connect them all up there, along with the other flexibility that exists. It's so close to being able to replace many other hosts/wrappers...

I don't expect it will happen, but I will forever hope.

So you want a Grid-(R)Studios

[coroknight]

I anticipate that the beta program for Bitwig 6.0 will begin in the fall of 2025, that the official 6.0 release will be launched by the end of 2025, and that Bitwig 6.0 will be showcased at NAMM in January 2026.

I suspect (with my cynical hat on) that they will announce the Beta once the current sale has finished, with a view that that will generate extra sales

So according to the bitwig community, bitwig can’t:
1. Work on any other products other than the bitwig DAW.
2. Can’t release premium DAW extensions.
3. Can’t optimize their sales/marketing/release schedules to bring in revenue.

So yet again people are extra critical of the underdog even though they need the extra revenue the most.

Sorry to say Saint Bitwig still needs capital to keep the lights on and people paid without shrinking until they go out of business.

[Rivanni]

People are just critical, not extra.

The rest of your comment is bullshit. You have no insight into the finances of any (DAW) company.

[BobDog]

I anticipate that the beta program for Bitwig 6.0 will begin in the fall of 2025, that the official 6.0 release will be launched by the end of 2025, and that Bitwig 6.0 will be showcased at NAMM in January 2026.

I predict it will start the day after my update plan finishes

[_leras]

- Sampler will receive a substantial update, maybe with time stretching and/or a built-in slicer

How would that work with multi-samples?

Ah, here we go again with the classic Bitwig response: “It’s not gonna work.” Just like the nonsense blah blah blah

He just asked 'How' would that work.

You're not a very chill person are you vroteg?