Let‘s speculate about 6.0

[JHernandez]

One thing that still really bothers me about Bitwig is the way it handles plugin windows. Unlike basically every other DAW, Bitwig doesn't remember the size or position of plugin editors when reopening a project. Every time I reopen a session, all my plugins stack up or reset to random positions, no matter where I placed them before saving. It's super frustrating, especially when working on complex projects and templates with dozens of plugins open.

I've already contacted support about this a while ago, but so far nothing has changed.
Am I the only one with this issue? I´m on a WIN11 machine

Weird. Bitwig does remember size and position of plugin windows on my systems. Both macOS and Win 11. What it doesn't remember is when I leave a plugin window open and save. I always have to reopen the plugin windows when I come back to the project, but they do reopen in the size and position I saved them in.

[BazJacuzzi]

For me it doesn't even remember the window location when reopening plugins within the same project (Windows 11). I wonder what's different on my system.

[Boudin]

And finally… AU compatibility

Serious question: what's the real benefit of AU on Mac?
I'm totally new to the Mac ecosystem and use VST3 or CLAP wherever it's possible. I was always under the impression that AU most beneficial usage is in Logic and for all other DAWs it's more or less a combatibility thingy...
Or is there actually a remarkable difference and it's better to use AU whenever it's possible?

for me, it's a matter of space on my 512 SSD, If I want to use a plug in both in Logic and Bitwig, I must install both au and vst versions. If the plugin is 1 Go, that's 2 go for one plugin. If you have several big plugins, it takes twice the ssd memory space !

[pdxindy]

for me, it's a matter of space on my 512 SSD, If I want to use a plug in both in Logic and Bitwig, I must install both au and vst versions. If the plugin is 1 Go, that's 2 go for one plugin. If you have several big plugins, it takes twice the ssd memory space !

Lots of plugins don't take double because the resources are shared.

The real solution of course is for Logic to support CLAP!

[] Peter:H []

I think there was some talk about stepwise in here as well, right ... because I was reading about chord demix (https://killihu.vstskins.com/chord-demix/) I wanted to share my opinion (opinion, aka subjective thinking).

I think stepwise is a missed opportunity.
Why is there no "trigger by note(s)" option in the plugin?
Why is there no "chord splitter" option in the plugin, which splits a chord into it's notes from bottom to top and assigns them to a steps lane, to allow user to create sophisticated custom arpeggios?
So it's again a "-" device thrown on us and creating head scratches for me and the usual "wait for stepwise+, it's gonna excel bro"...

But I see a real conceptional issue. I think Bitwigs mindset is: Hey, simply combine 5-10 modules and wiring it in a complex manner and we are so confident, that you can come close to what you want to achive. That's what Polarity does on a regular basis. Constructing dozends of workarounds that in the end only solve 80% of the task, or gives you a hugh Grid page where the CENTRAL elements are burried in a bunch of modules that distract attention.
But I don't want this. I want to do a very simple thing: Feed it a chord. Split that chord into it's notes and assign it to a lane...

By the way: Since it was released I'm completely stunned that Note Grid has no way to split a chord... at least to my knowledge. And please don't point me to "here's the 57 modules workaraound that solves it for some easy cases".
Their obsession to stick to mimik a analogue modular system in "Note Grid" is (opinion follows!) completely bolocks and the wrong level of abstraction. The concept "Note" is closer to "MIDI" and "Chord" as it is to CV...

So what do I do? Scratch my head, still use pizMidi to split chords and scratch my head a second time.
And I try to not lose the hope that Version 6 brings something for the MIDI/Pianoroll guys, after I observed with another head scratch that scarce dev capa went into their new hardware (If I'd knew they'd spend money and effort on hardware I wouldn't have bought and immediately activated 2 upgrade plans to support them... reminder to myself: better not do a single time again)

[Dirkitator]

The next Version could bei 6.0 probaly.

[coroknight]

What a tease! But that's a good sign that the next update is going to be on the large side and probably coming soon-ish. They usually don't talk to social media folks until development has progressed a decent amount.

[Rivanni]

sign that the next update is going to be on the large side and probably coming soon-ish.

Perhaps they informed him that 6.0 is set to launch after 5.4 and will enter public beta in the fall. We have not become any wiser.

[coroknight]

sign that the next update is going to be on the large side and probably coming soon-ish.

Perhaps they informed him that 6.0 is set to launch after 5.4 and will enter public beta in the fall. We have not become any wiser.

I don't think they'd be talking about 6.0 if it wasn't the next update. But sure.

[kultschar]

Sounded like Polarity had some ideas of the 6.0 content

[Jolaff]

Bitwig 3.0 : released 10 Jul 2019

Bitwig 4.0 : released 13 July 2021

Bitwig 5.0 : released 29 June 2023

Bitwig 6.0 : released .... find the algorithm

[coroknight]

Those are the official releases right? I think the betas start a couple months before that.

[coroknight]

If the pattern holds then we might see a beta next month and a full release in August. Seems like the releases are getting later and later in the year.

[Jolaff]

Yes, those are official releases... so I guess we will soon see a public beta...

why do you say it's getting later and later ?

[coroknight]

Nevermind I derped about the dates getting later. That’s what i get for skimming