What drives you crazy in Bitwig?

[coroknight]

The multiband containers have been driving me crazy because the crossover filters are definitely not linear-phase. Simply adding a multiband container (with no fx) is enough to mess with the phase of your sound.

Here's a simple example I created. First image is with the container enabled and second disabled. Again no fx or anything.

[NomadMonad]

Probably the pettiest complain ever for a software but this button

Screenshot 2021-09-01 at 07.54.05.png

Should be OK not Ok. Looks so ugly

[PhilipVasta]

Probably the pettiest complain ever for a software but this button

Screenshot 2021-09-01 at 07.54.05.png

Should be OK not Ok. Looks so ugly

If we don't make petty complaints, who will??

[anttimaatteri]

no midi capture.
i switched back to ableton very fast, after a short stint on bw4 with getting nervous breakdowns whenever i realised that i have to push the record button everytime on impro sessions, e.g. when searching for a certain sound that fits with lounge lizard or piano presets on analog lab etc...

[Coloss]

What drives me crazy is sometimes simply editing notes. You have that selection thingy which doesnt just select bunch of notes you selected but it creates that selection range/brackets around them. And then, sometimes, when i wanna edit the last note, its giving me "move selection end" cursor instead of "adjust (note) end" one. It happens quite often to me so i feel like this shouldnt be a default behaviour and should be only accessible via hotkey/modifier.

[lokanchung]

What drives me crazy is sometimes simply editing notes. You have that selection thingy which doesnt just select bunch of notes you selected but it creates that selection range/brackets around them. And then, sometimes, when i wanna edit the last note, its giving me "move selection end" cursor instead of "adjust (note) end" one. It happens quite often to me so i feel like this shouldnt be a default behaviour and should be only accessible via hotkey/modifier.

I've wrote about this several times to Bitwig since version 3.1 iirc. Time range handle should be disabled around notes but nothing has been changed yet.

[Tj Shredder]

Should be OK not Ok. Looks so ugly

Ok, noted…













P.s. I won‘t send a bug report…

[NomadMonad]

Should be OK not Ok. Looks so ugly

Ok, noted…

[slo_poe]

Having recently discovered this thread and skimming through it for a little, I have to say I agree with those of you who've been annoyed with the mouse/cursor and its overall behavior.

If i had a dollar for every time I wanted the cursor to do one thing but had it force me to do another (ie. wanting to move a clip but the mouse keeps trying to change lengths instead, etc.) I'd be able to join those guys going in up space

Other than that though there's not a whole lot I can complain about with Bitwig. It's been proving to be a fantastic for me DAW regardless

[questionaire]

What annoys me really is that the velocity sensitive knob/adjustment is presented in dB's and not in percentage and that it is also affects the overal volume while adjusting. So lowering the velocity sensitivity increases the volume. That is with sampler and polysynth for example. So adjusting the velocity means readjusting the volume bweeehhhhh.

Phase 4 is in percentage.

In ableton it is done properly in perecentage and keeping the volume at a controlled volume.

[docbot]

that it's such a great daw, it should run on a graphics engine that is on par with FL Studio or at least Ableton. Don't know if they do something about this at this point, but I hope so.

[antic604]

...So adjusting the velocity means readjusting the volume bweeehhhhh.

That only happens if your notes are not at full velocity and Bitwig's default is I think 100 out of 127. Once I understood what's going on it never really bothered me anymore. And frankly working in volume domain with dB rather than % makes sense to me.

[takaperry]

My only gripe with Bitwig is the lack of audio quantise… in 2021 you should be able to select the audio event and hit ‘Q’ to quantise the onsets.. I don’t know why this is not a function yet, seeing as we have Elastique in the DAW.

And no, the ‘Slice at Onsets’ and quantising the individual events is not an acceptable workaround

[questionaire]

...So adjusting the velocity means readjusting the volume bweeehhhhh.

That only happens if your notes are not at full velocity and Bitwig's default is I think 100 out of 127. Once I understood what's going on it never really bothered me anymore. And frankly working in volume domain with dB rather than % makes sense to me.

Maybe you are right it is only that simpler from ableton and the synths of ableton reacts so much more natural to vel;ocity sensitive settings. I just want to know why that is i have really no clue about that. I changed the velocity curve on my Novation SL MK3 to normal (i suppose that means lineair. And it feels like that the keybed responds better to velocity now, also reducing the velocity on sampler to 20dB did a lot good and saved it as default.

[docbot]

What annoys me really is that the velocity sensitive knob/adjustment is presented in dB's and not in percentage and that it is also affects the overal volume while adjusting. So lowering the velocity sensitivity increases the volume. That is with sampler and polysynth for example. So adjusting the velocity means readjusting the volume bweeehhhhh.

Phase 4 is in percentage.

In ableton it is done properly in perecentage and keeping the volume at a controlled volume.

Ableton handles velocity very wrong in their stock devices. When you increase velocity sensitivity, the loudest sounds with 127 vel. should stay at the same volume and the notes with lower velocity should become more quiet, but Ableton for some reason decided that increasing velocity sensitivity will make the loudest sounds louder, which throws off the whole mix and makes you having to readjust the volume fader constantly.

Bitwig does it the correct way. You set the device volume which equals a 127 note. If you increase velocity sensitivity, Bitwig shows you how much quieter a 0 velocity note will be in relation to the volume you chose for the loudest notes. It's actually a genius feature.