What drives you crazy in Bitwig?

[aMUSEd]

The popup browser getting in the way of the track area - and then having to close it each time I've chosen a preset etc to get access to tracks - really needs an option to dock it along with the side browser or even as part of that

[antic604]

They are more fiddly than Live, but proper multiclip fading more than makes up for it, at least it does for me.

Yeah, yeah! It's a tiny inconvenince for sure. But one that probably can be "easily" fixed, e.g. by only showing clip gain handle in the middle 50% of the clip, so 25% on the left for fade-in handle, middle 50% for gain handle, and 25% on the right for fade-out handle. Or something.

[pdxindy]

Hmmm... just checked, I see no way to do so.

I have a few 3rd party chorus plugins and none of them have a reset on transport option either.

You could automate the mix parameter to start from 0 and fade in a bit to hide any initial difference?

Renoise can do that!

I've never happened upon a need for restarting the Chorus phase at the same value.

[pdxindy]

They are more fiddly than Live, but proper multiclip fading more than makes up for it, at least it does for me.

Yeah, yeah! It's a tiny inconvenince for sure. But one that probably can be "easily" fixed, e.g. by only showing clip gain handle in the middle 50% of the clip, so 25% on the left for fade-in handle, middle 50% for gain handle, and 25% on the right for fade-out handle. Or something.

I haven't found it a difficulty getting the fade envelope and how it currently is is acceptable for me... but if it is going to be changed, I certainly don't need 25% of the clip length given to clip fades. Except of course on short clips, it is already about 25%.

[SLiC]

What drives you crazy in Bitwig?

Having an update plan is like a 'ticking clock' when you are waiting for new updates and wondering if it will come before your update plan expires!

[antic604]

What drives you crazy in Bitwig?

Having an update plan is like a 'ticking clock' when you are waiting for new updates and wondering if it will come before your update plan expires!

I wouldn't be surprised in Bitwig devs had the same "clock" in their office, they just look at it slightly differenly

I miss the machine-gun updates... (yes, I know @pdxindy that you don't, that for you it's often enough and Bitwig is almost perfect as it is )

[Dionysos]

I wouldn't be surprised in Bitwig devs had the same "clock" in their office, they just look at it slightly differenly

Yeah, it is a bit annoying that the current system basically incentivises 13-month development cycles. Even though I guess/hope they don't intentionally plan around that.

A licensing plan like Reaper's that gives you access to a certain major version range may be better, even though of course that can be worked around by more frequent major releases almost as easily.

[pdxindy]

What drives you crazy in Bitwig?

Having an update plan is like a 'ticking clock' when you are waiting for new updates and wondering if it will come before your update plan expires!

I wouldn't be surprised in Bitwig devs had the same "clock" in their office, they just look at it slightly differenly

I miss the machine-gun updates... (yes, I know @pdxindy that you don't, that for you it's often enough and Bitwig is almost perfect as it is )

I never said Bitwig is almost perfect as it is... just cause there are lots of feature requests I don't need or want, doesn't mean there are not also lots of feature requests I do. I've thumbs up'ed more more feature requests than down... you just notice the downs more

What machine gun updates... there never were any

I liked the roughly 3 updates per year pace. Enough time get comfortable with whatever new stuff came before the next one. Now it is more like 2 updates per year. Not as fun, even if it ends up being exactly the same amount of stuff.

I don't care about the "ticking clock" cause I'm gonna upgrade again no matter what, so it is irrelevant.

[pdxindy]

Yeah, it is a bit annoying that the current system basically incentivises 13-month development cycles. Even though I guess/hope they don't intentionally plan around that.

I don't think it incentivizes a 13 month development cycle... Wouldn't that only be the case if everyone updated at the same time of year?

Since everyones update date is distributed throughout the year, 13 months for you might be 3 months for me.

[sensej81]

Zooming by clicking scroll wheel is so damn annoying.

[antic604]

Zooming by clicking scroll wheel is so damn annoying.

Settings / User Interface / Middle-button Natigation -> choose between Pan vs. Pan & Zoom

[antic604]

...you just notice the downs more

I'm risk manager by occupation (and temperament / personality) so I tend to err on the negatives. That's why your unwavering optimism drives me crazy, but in a good way

[machinesworking]

Hmmm... just checked, I see no way to do so.

I have a few 3rd party chorus plugins and none of them have a reset on transport option either.

You could automate the mix parameter to start from 0 and fade in a bit to hide any initial difference?

Renoise can do that!

I've never happened upon a need for restarting the Chorus phase at the same value.

I like my oscillators without temp sync, so I have no need for tempo sync'd oscillators.

That was some poor logic there.

[Hanz Meyzer]

That's very legitime, that you do not miss lfo reset. But still, I miss it

[Dionysos]

I don't think it incentivizes a 13 month development cycle... Wouldn't that only be the case if everyone updated at the same time of year?

I think it's reasonable to assume that the majority of sales are made around the time of a major release, and expired licenses are refreshed around that time, too. I could be wrong, of course.