Let‘s speculate about 6.0

[pdxindy]

When will Bitwig 6 be released?

There's been no info... nor is it even known if the next update will be 5.4 or maybe 6.0

[Teksonik]

I jumped off the Bitwing train at 5.1 but if the following are added to six I might jump back in....

1. True MIDI Step Record.
2. The ability to have custom display names for Plugins.
3. A way to turn off all scanning at start up including content scanning.

[xbitz]

Just it has some features Bitwig is missing and Bitwig is a DAW not a synth. I trust Bitwig will do a great 6.0 release with this type of feature in piano roll and hopefully some groove stuff.

What specifically do you want to see? (I don't know what's in Serum 2)

Instead of basing it on Serum, it should be inspired by the Harmony Wizard MIDI extension from Studio One — if I may add my two cents.

from 2:40

[Chameleonman]

3. A way to turn off all scanning at start up including content scanning.

The scanning is fast now.

Improvements
• Projects and presets now load faster on all computers
• Bitwig Studio's device/DSP code now compiles in parallel for quicker loading of projects or even preset browsing
• The result is now cached more efficiently so after presets are loaded the first time, they will load faster thereafter

[machinesworking]

Again neither of you are that bad, but you are 100% shields drawn loyalists, that acted like everyone else was crazy and complainers during that whole fiasco.

During that fiasco, I was highly critical of Bitwig. I never called anyone crazy for being angry about. I was one of the people vocally angry about it. I was even briefly banned on the Bitwig Discord for it.

You got a narrative in your mind and you are projecting it onto people. In other words, you are making shit up.

Yawn, I really don't have a bone to pick with you, but you're revisionist history is BS.
One of my last replies to you in that thread before it was locked.

I can repeat what I said if you need. You stood against boycotting, complaining, all of it, even if you believed it was wrong what they did. You also absolutely without a doubt stood against any sort of public outcry. You now benefit from what you stood against.

You're just another human here, no hate here, these are words on a screen, but like many many many people these days you're loath to be wrong at all costs, you will protect your ego from this travesty of simply being on the wrong side even once. You come back with excuses and negativity towards the very people that changed the course of a company you love........

[Fleer]

AU compatibility pretty please.

[_leras]

Just it has some features Bitwig is missing and Bitwig is a DAW not a synth. I trust Bitwig will do a great 6.0 release with this type of feature in piano roll and hopefully some groove stuff.

What specifically do you want to see? (I don't know what's in Serum 2)

Instead of basing it on Serum, it should be inspired by the Harmony Wizard MIDI extension from Studio One — if I may add my two cents.

Definitely it doesn't have to be what's I Serum 2, but it has a piano roll with clips and clips variations, editing for clip length, scales, fold down notes, so it's a neat looking little sequencer. So it's got some utility that Bitwig doesn't, and it's not a DAW...

i.e. bitwig could have slightly different edit windows for clips and for clips/tracks in the arranger, Bitwig could also do with some extra sequencer types (I think). I could see sequencer clips being an interesting thing.

[xbitz]

^^^ I’ve found that Push is the most effective tool for finding the chords and Cubase for writing chord progressions — Push has all ths scales, provides fixed voicing patterns including closed, open, and all inversions, you can transition into an editor where those chords are visually represented in the background. Cubase now supports this kind of integrated workflow natively

Ideally, I’d love to see a DAW that fuses the best of both worlds. Honestly, I didn’t expect Cubase to make the move — adding modulators and native .dawproject support is a big deal. But ... if Steinberg’s stepping up, so be it. Still, fingers crossed for Bitwig to keep pushing the envelope.

[_leras]

Yawn, I really don't have a bone to pick with you, but you're revisionist history is BS.

Be a net positive in the world.

[_leras]

^^^ I’ve found that Push is the most effective tool for finding the chords and Cubase for writing chord progressions — .

Cubase now supports this kind of integrated workflow natively

Ideally, I’d love to see a DAW that fuses the best of both worlds. Honestly, I didn’t expect Cubase to make the move — adding modulators and native .dawproject support is a big deal. But ... if Steinberg’s stepping up, so be it. Still, fingers crossed for Bitwig to keep pushing the envelope.

There are some great things in Cubase, like control room, very good audio editing and decent midi. I've spent probably thousands of hours in Cubase, but...

Compared to Bitwig it is clunky AF. The whole thing is just so rigid. It Bitwig it's super quick to group anything, parallel anything, so the mix structure matches the track much more closely and is less template based.

Of course it's very possible to make music in Cubase, but Bitwig is so fluid. FX chains are way better. For me it's just so nice to use and I just make better music and better mixes.

[pdxindy]

Yawn, I really don't have a bone to pick with you, but you're revisionist history is BS.
One of my last replies to you in that thread before it was locked.

You were wrong then, and wrong now. You're like a flat earther, just a more subtle form of conspiracy nut.

[Teksonik]

3. A way to turn off all scanning at start up including content scanning.

The scanning is fast now.

Improvements
• Projects and presets now load faster on all computers
• Bitwig Studio's device/DSP code now compiles in parallel for quicker loading of projects or even preset browsing
• The result is now cached more efficiently so after presets are loaded the first time, they will load faster thereafter

That's nice but I don't need Bitwig to scan presets at all. I never use its built in preset handling. I always use the plugin's system.

An option to turn off preset scanning would be the answer for me.

[enCiphered]

Plugin presets (the state of parameters in a plugin) are just one tiny piece of Bitwig’s broader preset ecosystem. Bitwig also empowers you to create device presets, chain presets, FX presets, track presets, group/channel presets, macro presets, modifier presets, and so much more.
If you rely solely on plugin presets, you're missing out on the extensive flexibility and creative potential that Bitwig’s full preset system offers. After years of working with it, switching to any other DAW is simply unthinkable. They all look primitive by comparison in preset management and many other critical aspects.

[Trancit]

...After years of working with it, switching to any other DAW is simply unthinkable. ...

I think, this is an extreme dangerous trap... if you go "internal presets only" and you are forced to use a different product (for whatever reason but shit can always happen) you are doomed...

Bitwig is a very small young company... I doubt very much the company has already gained what they probably have dreamed off... if now a company like Adobe make them an offer they cannot deny, I don´t know if they have the balls to refuse because it´s their "baby"...
Adobe would follow their typical scheme and does an expensive subscription only model... and then??
Following the subscription only for plenty of money just because you need Bitwig??
Change nontheless to another DAW??
Then you´ve lost the whole "preset work" of the last years and can start from zero...

Relying on 3rd party stuff is much more future proof... you can easily port over everything to any DAW you like if needed... with often a ton better quality on top (i.e. the multiband containers have very unflexible and noticeable crossovers... nearly everything on the market is much more flexible and advanced... just have a look at Melda´s stuff)

Going DAW internal only is like never doing backups because it works as long as it works...
But if it goes down... all is lost...

[TheYke]

Bitwig also empowers you to create .... track presets ....

How to do this? If I want to save a track with all of its parameters, like I/O, monitoring and stuff in the inspector (like those pitch bend settings), I'm forced to save a project with this track, just to grab this track from the browser, then, am I not?

In fact, I find this very clunky and I'd love to see more easy options for default/preset tracks (maybe a bit like in reaper?).

Am I missing something here?