What drives you crazy in Bitwig?

[JHernandez]

^FL is the worst looking popular DAW in history in my eyes, it's also a terrible DAW in general imo. Funny enough I'd describe FL similar to how you describe Bitwig, SUPER CLUNKY. Floating windows for a lot things, big squared off sections, it can be super busy looking or at times show random empty spaces, often with floating windows on top, ect Oh and patcher, kill me! Almost full screen piano roll is nice though, except the colors but you know preferences, opinions and what not. I get it. Maybe one day Bitwig will offer themes but who knows when that will be? I certainly hope soon, not for my sake as I think it's great as is, but clearly one theme does not fit all.

I don't experience this lag you bring up though. It simply doesn't exist on my systems until i have a super busy project straining my cpu's, not on the 12 year old machine nor the new one. It's strange, some people say they have these issues, others don't. I wonder what that's about?

The browsers are awesome and customizable to get exactly what I want/need without thinking about it but again, preferences ect. I see a lot of people in vids use the search, I never touch it. (might be handy in the grid though, currently don't use it) I often reach for plugins and or devices with my head turned to the other monitor, or maybe talking to someone, I have it so organized. Collections are awesome imo. If Bitwig changed the browsers I'd be bummed and it may slow me down, or worst case, make me disorganized.

Anyways, I don't mean to come on harsh if it reads that way, I promise.

Good luck on your mission.

[epiphanius]

I have Ableton Suite, Reason and most recently Bitwig: I rarely use Bitwig because of the painfully slow load times. I have tried a number of troubleshooting ideas (disabling vst folder, etc), and cannot get it to load in less the 30 seconds. By the time it opens, I can have either Ableton or Reason up and running to do whatever it was I was thinking of. I would be so pleased to hear that this gets fixed.

[wentzelitis]

i agree with many in here who mention loading/gui issues. seems like i constantly have various loading issues.. either the program itself, plugins, presets, even built in native devices like loading a drum machine preset that comes with bitwig. support is helpful with most problems that i bring up to them, often fixing within 1 or 2 patches. but whenever i contact them about a loading/gui issue they get super defensive and try blaming anyone but themselves. there's a reason so many people seem to complain about loading/gui lag etc..look in the mirror dudz

audio quantize is needed

petty annoyances
- double clicking to revert parameters to default when most daws/3rd party plugins use alt or ctrl + click . at this point i just try all 3 combos and hope i pick the right one each time
-no global velocity curve setting
-can't hide "location" category from browser
-can't map drum machine pads to controller
-no input gain on channels without adding "tool"
-no built in tuner
-vertical zooming
-default velocity 80 with type keyboard, can't change default

[pdxindy]

petty annoyances
- double clicking to revert parameters to default when most daws/3rd party plugins use alt or ctrl + click

Hmm... AAS, U-he and Valhalla are double click. Isn't Live double click? (I'm really forgetting Live at this point)

Logic is Alt-click and Fab-filter is Cmd-Click

[wentzelitis]

petty annoyances
- double clicking to revert parameters to default when most daws/3rd party plugins use alt or ctrl + click

Hmm... AAS, U-he and Valhalla are double click. Isn't Live double click? (I'm really forgetting Live at this point)

Logic is Alt-click and Fab-filter is Cmd-Click

u-he is ctrl click, and valhalla is alt click, but i guess double click does work as well for both i've just never tried it since nothing else i've ever used uses double click. studio one is ctrl click, fl studio is alt click. every plugin i've ever used that I can remember is ctrl or alt click

obviously there's no standard, but i personally never or rarely have seen double click as the method, so now it's just a 3rd method i have to try before i get it right if I'm not super aware. again it's listed in my petty annoyance. i know it's petty, but i still don't love it. double click is just more sloppy to me, resulting in accidental misclicks and extra undo layers on occasion.

if live is in fact double click then it makes more sense originating from there and all

[VVRV]

Things that drive me absolutely crazy:

1. Absence of audio quantization. Bitwig implemented numerous time-stretch algorithms, but still didn't manage to implement such an obvious feature.
2. Note Editor remembers length of the last touched note. It is extremely inconvenient to work with.
3. Clip level envelopes' points (e.g. Pitch, Pan) can't be duplicated without duplicating chunks of the audio event they are placed on.
4. Low Pass Filter in Chorus device. Wow! "Let's make basic audio effect, but anti-Ableton way... Uhm, we meant the Bitwig way!" Bitwig Studio has quite a few illogical design decisions throughout the whole app.
5. UI responsiveness is (as it has been said in this thread) clunky. Watching someone work in Bitwig Studio from aside doesn't give you the whole picture. Once you get your hands on it yourself, you instantly feel each and every microlag between click and response. It feels clayish, clumsy and sluggish.

[perpetual3]

petty annoyances
- double clicking to revert parameters to default when most daws/3rd party plugins use alt or ctrl + click

Hmm... AAS, U-he and Valhalla are double click. Isn't Live double click? (I'm really forgetting Live at this point)

Logic is Alt-click and Fab-filter is Cmd-Click

u-he is ctrl click, and valhalla is alt click, but i guess double click does work as well for both i've just never tried it since nothing else i've ever used uses double click. studio one is ctrl click, fl studio is alt click. every plugin i've ever used that I can remember is ctrl or alt click

obviously there's no standard, but i personally never or rarely have seen double click as the method, so now it's just a 3rd method i have to try before i get it right if I'm not super aware. again it's listed in my petty annoyance. i know it's petty, but i still don't love it. double click is just more sloppy to me, resulting in accidental misclicks and extra undo layers on occasion.

if live is in fact double click then it makes more sense originating from there and all

Most plugins I use are double click.

[wentzelitis]

petty annoyances
- double clicking to revert parameters to default when most daws/3rd party plugins use alt or ctrl + click

Hmm... AAS, U-he and Valhalla are double click. Isn't Live double click? (I'm really forgetting Live at this point)

Logic is Alt-click and Fab-filter is Cmd-Click

u-he is ctrl click, and valhalla is alt click, but i guess double click does work as well for both i've just never tried it since nothing else i've ever used uses double click. studio one is ctrl click, fl studio is alt click. every plugin i've ever used that I can remember is ctrl or alt click

obviously there's no standard, but i personally never or rarely have seen double click as the method, so now it's just a 3rd method i have to try before i get it right if I'm not super aware. again it's listed in my petty annoyance. i know it's petty, but i still don't love it. double click is just more sloppy to me, resulting in accidental misclicks and extra undo layers on occasion.

if live is in fact double click then it makes more sense originating from there and all

Most plugins I use are double click.

interesting. i use a lot of plugins across multiple (5) DAWS and they're literally all alt or ctrl . though i've learned today a couple of them also have the double click 2ndary option. bitwig was literally the first thing i've used that was double click exclusively. would be nice if they had alt as an option as well since i don't believe it's used for anything? double clicking a parameter is just sloppier than a single click, not to mention the inconsistency reasons. again, bottom of my list on things that matter but it will irk me from time to time.

[pdxindy]

Most plugins I use are double click.

interesting. i use a lot of plugins across multiple (5) DAWS and they're literally all alt or ctrl . though i've learned today a couple of them also have the double click 2ndary option. bitwig was literally the first thing i've used that was double click exclusively. would be nice if they had alt as an option as well since i don't believe it's used for anything? double clicking a parameter is just sloppier than a single click, not to mention the inconsistency reasons. again, bottom of my list on things that matter but it will irk me from time to time.

I've always thought double click was kinda the standard. Most stuff I use is double click. I prefer double click cause it only takes 1 hand instead of 2. Anyway, an option would be fine.

[Tj Shredder]

Things that drive me absolutely crazy:

1. Absence of audio quantization. Bitwig implemented numerous time-stretch algorithms, but still didn't manage to implement such an obvious feature.

I love Bitwig for that, audio quantization is evil…
We get better music with that, and it forces bad musicians to practice more…

(Sorry couldn’t resist… Isn’t as serious as it reads… but has truth in its core…)

[squeaky]

two small things that always annoy the hell out of me:

1) when starting up Bitwig to start play on the last project that is loaded, space bar doesn't work. you have to mouse click play button in transport bar

2) last search in browser is remembered and still there , even after quitting the program

[VVRV]

I love Bitwig for that, audio quantization is evil…
We get better music with that, and it forces bad musicians to practice more…

(Sorry couldn’t resist… Isn’t as serious as it reads… but has truth in its core…)

Despite I mostly agree with this statement, yet we are here in a DAW forum looking for more QoL features

[killmaster]

I end up having a very hard time troubleshooting midi flow. I use a lot of hardware controllers and with all the different scripts, I can't see how midi gets filtered through the device chains. I've requested an inline MIDI monitor and the response was positive. This would be the most welcomed feature for me.

[Biscotto]

2. Note Editor remembers length of the last touched note. It is extremely inconvenient to work with.

It does, but not in Pencil mode.
Touching vs Drawing
In Pointer mode it will remember the length of the last note you “draw” or “touch”
In Pencil mode it will remember the last note you “draw” but not the last you “touch”

[VVRV]

It does, but not in Pencil mode.
Touching vs Drawing
In Pointer mode it will remember the length of the last note you “draw” or “touch”
In Pencil mode it will remember the last note you “draw” but not the last you “touch”

Well, that doesn't change anything in its inconvenience. And in case of Draw Tool it's also inconsistent An option to deactivate this behavious altogether would be useful.