Bitwig Studio 6 is Out Now!

[stamp]

Yeah.
More and more curious who's doing the UI stuff now.
Seems to be a blind mole smoking something unhealthy.

What?? The gui is great for me.

I work in a not too bright room with side lights and it's just right. Are you working in a brightly lit room or something?

I work in bright daylight and 6 is anything but perfect in my case.

[pdxindy]

What?? The gui is great for me.

Overall, I like the changes in V6... With a few things I would tweak. But mostly, I've gotten on fine with every version and they all look like bitwig to me.

[Ou_Tis]

Copy paste for automation still seems to be garbage... amazing. I just want to copy the automation from one parameter to another parameter. And of course there's no manual, and Gemini Thinking can't tell me a better way to do it in Bitwig 6.

I hate the developers.

Edit: I see, I need to use their "Automation clips" feature instead. Unnecessarily convoluted bullcrap.

[Ou_Tis]

Even after turning it into an automation clip it's not copying properly. I'm trying to copy track volume automation to tool gain automation. But it's mapping 0 db to something like +24 db, what BS, what an annoying hassle. And I could swear that in Bitwig 5.x version of the project I was using tool gain automation instead of track volume automation, though I might be mistaken about that.

[pdxindy]

Even after turning it into an automation clip it's not copying properly. I'm trying to copy track volume automation to tool gain automation.

It's not going to adjust the curve to match dB values across different parameters. With the tool device, neither volume nor gain have the same range of values as track volume. Gain has different scaling too. Plus it only goes to -36, not -∞

[Ou_Tis]

Even after turning it into an automation clip it's not copying properly. I'm trying to copy track volume automation to tool gain automation.

It's not going to adjust the curve to match dB values across different parameters. With the tool device, neither volume nor gain have the same range of values as track volume. Gain has different scaling too. Plus it only goes to -36, not -∞

It's trivial to map db to db, and should be trivial to code. (And the obvious solution for values less than -36 db is to make them -36 db.)

[pdxindy]

It's trivial to map db to db, and should be trivial to code. (And the obvious solution for values less than -36 db is to make them -36 db.)

Sorry, but this is just some random thing you decided should work a certain way that doesn't even make sense.

If you want to re-map track volume, at least use Tool-Volume, which is relatively close track volume. Better still, use a bipolar Macro and then when you copy paste the track volume curve to a macro automation lane it will match.

[Ou_Tis]

It's trivial to map db to db, and should be trivial to code. (And the obvious solution for values less than -36 db is to make them -36 db.)

Sorry, but this is just some random thing you decided should work a certain way that doesn't even make sense.

If you want to re-map track volume, at least use Tool-Volume, which is relatively close track volume. Better still, use a bipolar Macro and then when you copy paste the track volume curve to a macro automation lane it will match.

What part of "map db to db, with anything below -36 db mapped to -36 db" doesn't make sense to you? It's an extremely simple and obvious mapping, unless you're being willfully ignorant.

Last I checked the macro buttons were extremely buggy. They've resulted in me losing a lot of work. Have they actually fixed that in Bitwig 6, or were they too busy making the gui crap?

[pdxindy]

What part of "map db to db, with anything below -36 db mapped to -36 db" doesn't make sense to you? It's an extremely simple and obvious mapping, unless you're being willfully ignorant.

Track Volume -> Tool Gain translation makes no sense. There's no reason to want to do that. It's a misunderstanding on your part of how to accomplish a task.

Last I checked the macro buttons were extremely buggy.

Macros are knobs, not buttons. I use Macro modulators constantly in a variety of ways, and they work reliably. If you are having issues, it's most likely user error.

[Ou_Tis]

Track Volume -> Tool Gain translation makes no sense. There's no reason to want to do that. It's a misunderstanding on your part of how to accomplish a task.

The reason to want to do that is that the maximum positive tool gain value is substantially higher than the maximum positive tool volume value. I prefer to use tool gain when I'm not setting something to -infinity.

There should at least be an option to copy over the exact values, with anything above or below the new max or min values set to max or min respectively.

I use Macro modulators constantly in a variety of ways, and they work reliably. If you are having issues, it's most likely user error.

No, it's very clearly a set of bugs when using the macro knobs. For example, if I deactivate and reactivate the plugin with the macro in its controllers section, the macro's value goes from what it had been previously set at to the maximum value.

[Ou_Tis]

[Edit: nm.]

[BazJacuzzi]

"it's not broken, it works for me" is such a tiring response.

Bitwig has a lot of bugs, and it's been that way for some time now. Versions 3 and 4 were pretty stable and had a relatively small number of issues, and most of those could be worked around. That isn't the case now. There's been a huge amount of churn, which has introduced a lot of defects, and it doesn't feel good.

I'm not a hater, I really like Bitwig, but let's be honest, the last few years have been bumpy.

[Captain Crunk]

"it's not a broken, it works for me" is such a tiring response.

Bitwig has a lot of bugs, and it's been that way for some time now. Versions 3 and 4 were pretty stable and had a relatively small number of issues, and most of those could be worked around. That isn't the case now. There's been a huge amount of churn, which has introduced a lot of defects, and it doesn't feel good.

I'm not a hater, I really like Bitwig, but let's be honest, the last few years have been bumpy.

It could be so much worse though. Cubase crashes every 10 seconds, so Bitwig feels rock-solid by comparison.

[permeke]

Got a full crash on OSX while comping audio.
Never had this before in earlier versions.
Just saying.

[BazJacuzzi]

"it's not a broken, it works for me" is such a tiring response.

Bitwig has a lot of bugs, and it's been that way for some time now. Versions 3 and 4 were pretty stable and had a relatively small number of issues, and most of those could be worked around. That isn't the case now. There's been a huge amount of churn, which has introduced a lot of defects, and it doesn't feel good.

I'm not a hater, I really like Bitwig, but let's be honest, the last few years have been bumpy.

It could be so much worse though. Cubase crashes every 10 seconds, so Bitwig feels rock-solid by comparison.

Oof, that sounds rough.

Something I absolutely rate Bitwig for is that whenever it crashes, it will reliably reload the state it was in just before the crash. That is :chefskiss: