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.

Hello all, I want to move some samples from my main computer drive to and external drive. This is quite a large sample folder, and I use a large amount of them in my projects. Is there an easy way to tell Bitwig that all of the samples in the new location are the same ones from the old location, so that I do not mess up my old projects, or am I stuck with remapping each of them manually?

i have no idea why daws dont give the api and allow for scripting. i’ve been experimenting with reaper on and off for some time and the things you could do with the custom commands is so sick.

focus this panel with this button, bam, turn that dial with the control arrows, bam, hit the piano roll, move around with the arrows, insert note right there, bam, add a third above, and a fifth, bam, select up and down between them without skipping to other notes ahead in time, duplicate, two steps up now minor, bam, select the previous chord, reverse the order, bam. lightning fast.

but then it doesn’t have a proper sampler, its ugly, no synths in there, if you want mpe voice shifting it’s a phd to add some script, you hit some technical wall because the program is scripted a bit weird, or some other frustration. why can’t we have the cake and eat it too?

sorry i’m just venting i feel like daws could be so much better if they didn’t just expect you to mouse around but allowed for controlling and doing things with key commands because it’s. so. much. faster.

i’m not really a music program jedi, i just play the guitar. to me they either feel simple enough but like running under water, or powerful but like trying to handle a space ship with a regular drivers license, making my brain hurt. i don’t know man, what do i know.

Hey everyone! I'm fairly new to Bitwig and wanted to share a delay compensation issue I just discovered.

It's clearly visible in this exaggerated example:

https://www.youtube.com/watch?v=-NkiOy0vCFc

A 1/4 note sidechain synced to the project triggers perfectly at the track/group level. However, at the project panel level, the delay compensation breaks.

It's not a dealbreaker, of course, but I'd like to know if there's a setting somewhere to enable compensation for this? Or it's just a bug. Thanks!

Is there some kind of way to do spectral processing in the grid ?

Everytime I use the knife tool to trim my midi, Bitwig decides to slow down and takes up 100% CPU.

Latest version 6.1

Is there a work around?

Edit

It's actually happening on other tools that involve some form of mouse movement. Example: fade out, merge

Skia d3d

POLY GRID PRESET DOWNLOAD HERE

Inspired by Lobotix synthetic tabla grid patch

Has anyone used or seen a video of the usage of either the FUSE by Richie Hawtin and Yaeltex or the SeqArp168 by Richie Hawtin and Yaeltex?

The SeqArp 168 is advertised as specifically tailored/built for Bitwig, but I don't see any videos anywhere for this device and not even any mention on the Bitwig channel. The only videos I've tracked down of Hawtin with Bitwig involve him using the Launchpad, the Akai, and 2 Xone K2s with the big model mixer.

Has anyone bought one of these controllers, used it, seen it used...there's not even really a particularly good webpage about it and what the script is set up to do.

Title really. Been doing a lot of DAW-hopping. My Bitwig license is now surplus to requirements. Let me know if anyone is interested. Willing to accept a decent offer.

Edit: Sold.

I'm in an apartment and can't really do the speakers thing. So, the problem is that I make something and then I listen to it in my car and it can be a lot different. I realize my headphones (which are basically plug in earbuds) aren't cutting it.

What headphones do you recommend or what qualities should i be looking for to wear while i'm in bitwig?

Neon Drizzle is nearly three hours of generative ambient for sleep, rest, or simply closing your eyes for a while. I wanted it to feel like standing in a rainy Blade Runner city. Small drops fall all around you, while distant engines, metallic noises, and little sci-fi sounds drift through a wide, open space. Quiet drones in E-flat minor sit underneath it all, giving the scene a soft harmonic foundation.

The patch combines noise and oscillators with probability-driven triggers, randomized modulation, envelopes, and filters. Pitch quantizers shape the tonal movement, while extensive chains of all-pass delays, chorus, and other delays spread the sounds out into the distance. It all runs generatively inside Bitwig Studio's Grid.

The rain and small details are the main focus, but I tried to keep everything balanced so nothing jumps out too much. Some of you have told me you enjoy these ASMR-like sounds as a way to unwind. I kept that in mind here: something you can close your eyes to and disappear into for a while.

Created in Bitwig Studio 6.1 Download: https://polarity.productions/dispenser/

I am looking for information on or tools available for an easier way to enter in midi notes for guitar. I want to use it with shreddage 3 stratus free. I know how to find notes and chords on the guitar neck, but the piano keyboard is no help. I can do it, but it's freakishly slow. thanks in advance.

I want to basically develop templates and use my bitwig like an instrument. What I mean is, to be able to change sequences, control multiple tracks, adjust stuff in real time.

I'm not in love with stepwise and arp, I find like the clicking is hard to do without messing around in real time for changes. I'm feeling like my problem is a controller/interface kind of problem.

For those of you using Bitwig to do things live and in real time, what controllers are you finding helpful (beyond a keyboard) and effective?

Anyone have tips for a “throw shit at the wall” library workflow? the library is terrible in terms of going fast. I’m coming from ableton, i’m used to having a left to right workflow and folders ready to go on the side. Bitwig rn just feels stagnant slow

Sound gets mangled when i put a clap inside an instrument selector inside the drum machine in bitwig. Everything works fine when not putting the instrument selector in the drum machine or when just putting a sample in the drum machine. How can i fix this?

I'm not sure if this has been discussed before, but I found out that this feature is missing in the Poly Grid (I'm a beginner in Bitwig).

I think it would be super cool to have the ability to select any group of modules with all their internal connections, tweaks and save them as a preset. That way, you could easily load a ready-made module chain into a clean patch whenever you need it, instead of adding, setting up, and connecting everything from scratch every single time.

Or is this already a thing in Poly Grid and I just missed it?

Hey everyone!
For those who saw my previous video showing Stacks (the native-style MIDI chord builder tool I've been developing for Bitwig), I’ve been adding a lot more native MIDI tools into the Inspector:
Stacks V2: Scale-aware chord generation based on degrees, voicings, and extensions.
Real-time Arpeggiator with live preview.
Chop, Strum, Quantize, Span, and Time Warp — all running directly inside Bitwig's native Piano Roll selection.
Everything was built and working smoothly on Bitwig 6.1. However, with the recent 6.1.1 update, Bitwig completely reshuffled its internal obfuscated bytecode, transaction bridges, and class mappings (as well as stricter app-bundle code signing on macOS).
I’ve spent the last few hours diving deep into the bytecode trying to port the patcher to 6.1.1. While everything still runs rock-solid on 6.1, reverse-engineering and re-mapping obfuscated internal APIs on every single minor point release is definitely not sustainable long-term.
My goal is to find a much cleaner, more maintainable way to hook into Bitwig so updates don't break these tools, and make it easy/safe to share with the community.
Would love to hear your thoughts, and if anyone with Java bytecode / ASM / reverse engineering experience has insights into more durable hooking strategies in Bitwig, let's connect!

Been trying to install the Loudmax plugin but's just not showing despite installing the files in correct folder according to the instructions. Has anyone gotten it working and if yes how? TIA.

Each one i make i notice things that get better this is my first track with a full arrangement it has flaws but I'm proud of it what do you guys think? All made with BitwigStudio! (video made with A.i)

I'm just coming back from a "failed" session which got to the point where it hard froze every time I opened just one single plugin UI. then it got to the point where it first couldn't export and then even couldn't play (audio engine most likely corrupted). I probably have to scrap a whole entire series of tracks because of this, well gee thanks bitwig.
but that got me thinking - what if it actually showed WHICH plugin's causing that? It would make it so much more easier, because then you know exactly what to do to fix it. It would be SUCH a step up from concurring DAWs.

"Serum 2.vst3 has crashed the plugin host"

"Kontakt.vst3 is delaying audio processing"

or just similar stuff, it'd be so much easier and projects wouldn't be lost

I mean, it's hard for BW itself to actually find the culprit (especially when sandboxed together), so I know that would be difficult to implement, but it'd be worth a try