What drives you crazy in Bitwig?

[apoclypse]

I don haven't read this whole thread but not being able to select multiple tracks and change volume from the arranger or mix view. I don't know of any DAW that doesn't do that at this point.

[antic604]

I don haven't read this whole thread but not being able to select multiple tracks and change volume from the arranger or mix view. I don't know of any DAW that doesn't do that at this point.

Don't you have Inspector open at all times?

[apoclypse]

the lack of Undo for changes made inside third-party plugins is a HUGE one for me, too.

I'm not getting this one. I haven't seen any DAW that can undo changes in a VST? I must be misunderstanding this.

A few DAWs do this. Ableton has been doing that since at least version 8 (I believe). S1 can do it too and has done so since I believe 4.6. It really depends on the VST, if its an automatable or mappable parameter well Ableton and Studio One are always keeping track of any touched automatable or mappable parameters anyway so it can revert changes based on that. Doesn't work on parameters that have no automation as far as I'm aware.

For example let's say you use Hive. The Function sections have a parameter called Input. Those are not exposed as automation parameters so S1 and Ableton can't undo changes made there because it doesn't know what you changed. However in that same section Mode is automatable or mappable so it can be undone if changed.

[apoclypse]

I don haven't read this whole thread but not being able to select multiple tracks and change volume from the arranger or mix view. I don't know of any DAW that doesn't do that at this point.

Don't you have Inspector open at all times?

If I'm in the mixer I select tracks 1-5 the logical approach would be to move the faders in the mixer or arrange view and see all of them update. Why would I use the Inspector when thats supposed to be for track or clip specific functions? If thats what Bitwig wants us to do then thats terrible UX design and completely against the norm imo. Especially since its not even consistent. I can select multiple audio clips in the arrange view and affect the fade levels for all selected clips without using the Inspector, or change the start and end points etc, but still use the Inspector for more precision or if I need to see values.

Bulk actions like volume etc should be handled in the context that user is already in versus forcing them to change focus to another context. It's not immediately obvious these actions should be done in the Inspector. It's also not clear why these can only be done in the Inspector, when thats not the case for other bulk actions.

[antic604]

---

Ok, I get it. Perhaps I do this to rarely to notice and I always have the Inspector Panel open, so it's just a matter of dragging in different place.

And I definitely agree on the consistency argument.

[machinesworking]

I don haven't read this whole thread but not being able to select multiple tracks and change volume from the arranger or mix view. I don't know of any DAW that doesn't do that at this point.

Don't you have Inspector open at all times?

If I'm in the mixer I select tracks 1-5 the logical approach would be to move the faders in the mixer or arrange view and see all of them update. Why would I use the Inspector when thats supposed to be for track or clip specific functions? If thats what Bitwig wants us to do then thats terrible UX design and completely against the norm imo. Especially since its not even consistent. I can select multiple audio clips in the arrange view and affect the fade levels for all selected clips without using the Inspector, or change the start and end points etc, but still use the Inspector for more precision or if I need to see values.

Bulk actions like volume etc should be handled in the context that user is already in versus forcing them to change focus to another context. It's not immediately obvious these actions should be done in the Inspector. It's also not clear why these can only be done in the Inspector, when thats not the case for other bulk actions.

I don't particularly think that because something is done differently it' worse, but I wouldn't mind temporary grouping as an option for selection in general, like DP and others can give you. In DP anyway the t key instantly allows all sorts of group actions to be used. On the other hand if they spend too many man hours on making Bitwig behave like other DAWs instead of improvements to the feature set I would be upset. It's not terrible, it's just different.

I wan't audio and MIDI comping, I'm a guitar player and there are definitely times when MIDI quantize kills the vibe of a piece thats near impossible to get to loop properly. This is far more important to me than making grouping by selection, which is already possible using the Inspector, they designed it that way on purpose, it's not a tack on feature.

The way you go about setting up a multi instrument is even more arcane IMO, but it works. I have yet to see a DAW that doesn't break some UX rule or another.

[apoclypse]

I don haven't read this whole thread but not being able to select multiple tracks and change volume from the arranger or mix view. I don't know of any DAW that doesn't do that at this point.

Don't you have Inspector open at all times?

If I'm in the mixer I select tracks 1-5 the logical approach would be to move the faders in the mixer or arrange view and see all of them update. Why would I use the Inspector when thats supposed to be for track or clip specific functions? If thats what Bitwig wants us to do then thats terrible UX design and completely against the norm imo. Especially since its not even consistent. I can select multiple audio clips in the arrange view and affect the fade levels for all selected clips without using the Inspector, or change the start and end points etc, but still use the Inspector for more precision or if I need to see values.

Bulk actions like volume etc should be handled in the context that user is already in versus forcing them to change focus to another context. It's not immediately obvious these actions should be done in the Inspector. It's also not clear why these can only be done in the Inspector, when thats not the case for other bulk actions.

I don't particularly think that because something is done differently it' worse, but I wouldn't mind temporary grouping as an option for selection in general, like DP and others can give you. In DP anyway the t key instantly allows all sorts of group actions to be used. On the other hand if they spend too many man hours on making Bitwig behave like other DAWs instead of improvements to the feature set I would be upset. It's not terrible, it's just different.

I wan't audio and MIDI comping, I'm a guitar player and there are definitely times when MIDI quantize kills the vibe of a piece thats near impossible to get to loop properly. This is far more important to me than making grouping by selection, which is already possible using the Inspector, they designed it that way on purpose, it's not a tack on feature.

The way you go about setting up a multi instrument is even more arcane IMO, but it works. I have yet to see a DAW that doesn't break some UX rule or another.

Unfortunately Bitwig has a lot what I consider QoL shortcomings. It's not about being like other DAWs its about making the user experience better.

[machinesworking]

Unfortunately Bitwig has a lot what I consider QoL shortcomings. It's not about being like other DAWs its about making the user experience better.

Yeah, I think you're sig says it all. I'm in the same boat, DP10, Reaper, Logic, Live, Bitwig, Reason, MPC, Maschine, ReNoise here. So take it for what it is, I will never be satisfied with one DAW. Especially if another one does it better:
(quoted to separate the comparative DAW 101 part out)

Reaper- is great, but no: Clips, (the script for it sucks, not comparable to any other clip capable DAW), comping is shit, and the MIDI editor is set up in a stupid way and I'm still not satisfied with it after years of tweaking. < pretty much sums up Reaper there.

Logic - no multi midi input by port, messes up workflows with MPE instruments, PDC issues. The looming update that adds new things and messes with old ways, I hate the way tools are selected these days...

DP - slow development, no MPE, articulation mapping, Clips are still a work in progress, no macro parameter control surface support for VSTs.

Live- IMO, patching on Max was a terrible idea. The whole point of Live was UX I thought, then it hits you that it's just a watered down EDM sequencer for IT folks. I'm being harsh here, but there's nothing about Max that says stability, or quick results. Maybe quick results compared to coding from scratch, but I'm just not interested. To this day the piano roll has to be dragged full screen by hand.

Bitwig- there are some UX issues for sure, the mentioned inconsistency in approaches to grouping, some weird panel selection VS shortcuts issues, some odd GUI things like non customizable screensets for dual monitors, odd track resizing behavior, Favorites are way too generic of a catch all for all kinds of things. And of course the same limitations in features that Live has and will have. Neither will get articulation mapping, score editors, SysEx, etc. among other older DAW things that I still use.

Basically if you've bothered to read through my rant here you're probably in a similar place, still stuck between Live and Bitwig, and still not committed completely to one old school do everything style DAW. I just think it's clear that Bitwig never set out to be a better initial UX experience than Live, which is OK, I don't need to be up and running in a DAW right away only to then later hate the limitations of that easy UX experience. I'm banking on Bitwig right now because it's initial UX is much more to my tastes than Live, I can't stand Lives lack of commitment to shortcuts, the mousing is probably twice the amount of any other DAW I use. The full screen MIDI and audio editor is the real reason. Ableton lost me when they allowed two windows, but not a separate MIDI and audio editor window. We just don't think alike anymore at all.

All this to say I agree with you, group editing shouldn't be limited to the Inspector panel, but I acknowledge that no DAW is designed the way I want. I was looking at the announcements for Studio One's new version and they were still selling it as a "drag and drop" DAW, like this was some amazing thing.

[pdxindy]

Unfortunately Bitwig has a lot what I consider QoL shortcomings. It's not about being like other DAWs its about making the user experience better.

Midi Grid will make my user experience better...

[PieBerger]

I'm still finding my feet, as it were, but one thing that is starting to get annoying, is disabling the Note Audition for every single track. I know where the icon is to disable it and it's smart enough to save the off state, but what I would really like is a global option in the Preferences, to set the default state to off, for all current tracks in the project and or any new ones added.

[Tj Shredder]

I'm still finding my feet, as it were, but one thing that is starting to get annoying, is disabling the Note Audition for every single track. I know where the icon is to disable it and it's smart enough to save the off state, but what I would really like is a global option in the Preferences, to set the default state to off, for all current tracks in the project and or any new ones added.

Yes + a lot...
Or having the option to define a default for each type of a new track... I have to do many clicks to get my default.
Auto monitor to off
Midi channel to same
Pb - expression to off
And then when adding a MPE capable synth MPE to on...

[PieBerger]

I'm still finding my feet, as it were, but one thing that is starting to get annoying, is disabling the Note Audition for every single track. I know where the icon is to disable it and it's smart enough to save the off state, but what I would really like is a global option in the Preferences, to set the default state to off, for all current tracks in the project and or any new ones added.

Yes + a lot...
Or having the option to define a default for each type of a new track... I have to do many clicks to get my default.
Auto monitor to off
Midi channel to same
Pb - expression to off
And then when adding a MPE capable synth MPE to on...

Default tracks are something else I miss coming from Live. Not so much for Instrument Tracks as in your case, more for audio tracks, where I like to have an instance of True Iron and Hornet VU Meter. The Shift+click to add a device from favourites, almost makes up for it, but default tracks would be welcomed still.

[antic604]

...but what I would really like is a global option in the Preferences, to set the default state to off, for all current tracks in the project and or any new ones added.

Yeah, or at least a f**king keyboard shortcut!

I've been asking for this - and few others - for years and it's probably 5 minutes dev time to add it, but no - we're getting some weird things no one uses (or even understands whet they mean) that are bindable, but note audition, toggling of audio editing mode or merging devices in a Chain are apparently impossible to implement

Grrrr... Bad day at work, sorry

[antic604]

To offer a more positive spin...

One of the "features" added in one of 3.3.x and I don't think it was ever mentioned anywhere, is that if you're working in "small track height" view and you adjust the width of track's header, then if you switch back to "large track height" the width will be uniform / the same. It was always driving me crazy that it was chaingng & different between the two. Yay, I guess!!!

[PieBerger]

...but what I would really like is a global option in the Preferences, to set the default state to off, for all current tracks in the project and or any new ones added.

Yeah, or at least a f**king keyboard shortcut!

I've been asking for this - and few others - for years and it's probably 5 minutes dev time to add it, but no - we're getting some weird things no one uses (or even understands whet they mean) that are bindable, but note audition, toggling of audio editing mode or merging devices in a Chain are apparently impossible to implement

Grrrr... Bad day at work, sorry

It's kind of odd that it's not already implemented, I'm finding everything else is generally very well thought out and elegant, then there's this potato here that they just left out for us