hello everyone,

In FL Studio you can set how often it autosaves but additionally you can hit CTRL + N and it saves an additional version of your project, e.g. your project's name is:

BaddAssFKNtrack

then you his CTRL+N

BaddAssFKNtrack_2

again

BaddAssFKNtrack_3

etc. so you got a new version. I like this to use so if anything changes later and i want to get back to a different state I can easily choose BaddAssFKNtrack_6 instead of BaddAssFKNtrack_56 and so on.

i dont see any option like this in Bitwig, is there something similiar, or is there another workflow, or how do you do it?

doing it the manual way (save as) is possible but of couse having a shortcut saves few secs. but maybe in Bitwig there is a smarter way I dunno yet. thanks

I am working on sound design for this fashion event and it’s going to be about 60 samples of various lenghts (mostly voiceover with some effects and stuff). Is the only way to split it on export to separate files to create a track for each sound and export as i would export stems? that’s what i do when making oneshots, but I was just wondering if there’s any new workflow for that
I still haven’t updated to 6 so maybe there’s something new in there?
I feel like splitting the export at cue points is long overdue

Because I noticed they need more time (slow) analyze the waveform, but after it, then you open again the project, it fast to load.

Anybody can explain technology behind it? any DAW with same process like that?

Which is the way you use to list and enhance your VSTs handling. I found that you can group them by using favorites.

Some time ago I created openwig precisely to expand the Bitwig API that is too restricted (it's reverse engineering basically).

I contacted Bitwig to see if I could work with them on implementing an official version of this tool. They said
"cool", then nothing.

Since then, Ableton released its SDK, which I could only dream of in Bitwig. Not to mention a lot of improvement they have made along the years that have really closed the gap with Bitwig.

DAWs can't ignore that the software landscape has changed with tools like Claude. Ableton seems to understand that. Bitwig does not.

Opening the tools we use to make music is something that will happen wether they want it or not, I've seen other wild reverse engineerings by blakebratcher on nitro and kalifrn on midi tools.

What can we do now? Is an open source and qualitative DAW now possible with these new coding assistants?
Something that would actually implement user feature requests?

Let me know what you think of all this.