Bitwig 4.3 is out - Space & Tone (RELEASED)

[billcarroll]

FLAC support is cool. Anyone actively using it?

[pdxindy]

I mean the curve will apply that curve to all mod destinations in the synth for that modulator. Since there is no other way obviously. It can be really useful to have different curves for different modulation destinations in a synth but this method wouldn't be able to offer that. I know that's obvious, just thinking through it.

Ahh... yes, as I described, that would be the case.

However, there are the mod curves on each target in Bitwig. You can also mod the depth of a target by another modulator.

Not as slick as Vital which has a full multi-point curve editor for every mod target!

[lokanchung]

Still no thicker bar lines in piano roll... obviously devs don't use piano roll

[SmajjL]

Ahh, the .DEB -link is in the release notes
If i'm not planning to use WINE then, Flatpak

[Tj Shredder]

And of course you can do all sorts of other stuff cause it is just a signal in the Grid which can be affected by many modules.

I mean the curve will apply that curve to all mod destinations in the synth for that modulator. Since there is no other way obviously. It can be really useful to have different curves for different modulation destinations in a synth but this method wouldn't be able to offer that. I know that's obvious, just thinking through it.

If your synth/fx is done in the grid you can do that by adding curves for each destination. If not you could try to create a curve with the polynom modulator and lead it through a different one for different destinations (requires some math skills). Yes, we need some more modules of the grid as modulators… (send a FR…)

Thinking about it, if your synth is a Clap plugin, you can also create as many curved modulators as you want in the Grid and send it as per voice modulation to your destinations in the plugin. I didn‘t try, could be complicated but should be possible…
We are spoiled with Bitwig. In the modulation department its so much ahead of any other DAW…

[u-u-u]

And of course you can do all sorts of other stuff cause it is just a signal in the Grid which can be affected by many modules.

I mean the curve will apply that curve to all mod destinations in the synth for that modulator. Since there is no other way obviously. It can be really useful to have different curves for different modulation destinations in a synth but this method wouldn't be able to offer that. I know that's obvious, just thinking through it.

[...]
Thinking about it, if your synth is a Clap plugin, you can also create as many curved modulators as you want in the Grid and send it as per voice modulation to your destinations in the plugin. I didn‘t try, could be complicated but should be possible…
We are spoiled with Bitwig. In the modulation department its so much ahead of any other DAW…

That's not possible. You cannot send per-voice modulation between two devices. Even if you put the CLAP plugin into the FX slot of the Grid device, it's not possible.
Individual voices are handled per-device.

So only a modulators on that CLAP plugin would work.

-> I'd love to see something from Bitwig that allows me to send per-voice modulation from the Grid to third party devices. For now I see 2 ways how this could be made possible by the devs:

• Introduce a Grid module plugin format (or open up Grid module development to third-party devs / users). Those third-party Grid plugins / modules of course would work per-voice then.
• Introduce a Grid modulator. You could put it on any device, edit the internal Grid patch, create as many modulator outs as you want.
  • All that would be per voice.
  • Of course Audio/note out modules wouldn't work in this context and shouldn't be allowed inside the Grid modulator.
  • Maybe the user should be able to select a 'standard modulator out' whose mod source then is visible on the Grid modulator itself.

[Tj Shredder]

So only a modulators on that CLAP plugin would work.

Then modulate a macro, which is a modulator…
Anyway its would be a complicated workaround. Better we get a curve modulator…

Actually all U-he plugins which support voice per channel would understand per voice Midi modulation as the voice is determined by the Midi channel…

[anoise]

FLAC support is cool. Anyone actively using it?

I converted my 24 bit stems and bounces on some finished tracks to FLAC, to save storage space. There was a bug though, 24 bit FLACs were played back only in 16 bit in Bitwig, but now, it seems it is fixed.
Anyway, now I use 32 bit bounce, and FLAC doesn't support that bit depth.

[ReleaseCandidate]

Anyway, now I use 32 bit bounce, and FLAC doesn't support that bit depth.

FLAC does theoretically support 32 bit integers (but no encoder supports more than 24 AFAIK), but no floats.

[u-u-u]

FLAC support is cool. Anyone actively using it?

I converted my 24 bit stems and bounces on some finished tracks to FLAC, to save storage space. There was a bug though, 24 bit FLACs were played back only in 16 bit in Bitwig, but now, it seems it is fixed.
Anyway, now I use 32 bit bounce, and FLAC doesn't support that bit depth.

But the Bounce/Bounce in place actions still always use WAV, don't they? So no problem there.
For audio export, you are able to choose whether you want to export to WAV or FLAC. So this covered as well.
So what is the problem? But maybe I misunderstood (?)

[anoise]

FLAC does theoretically support 32 bit integers (but no encoder supports more than 24 AFAIK), but no floats.

I know WavPack supports 32 bit float. Theoretically Bitwig could add WavPack as does FL studio, but priorities... it would be nice though.

[anoise]

But the Bounce/Bounce in place actions still always use WAV, don't they? So no problem there.
For audio export, you are able to choose whether you want to export to WAV or FLAC. So this covered as well.
So what is the problem? But maybe I misunderstood (?)

After I'm done with the track, I convert the wav's in the project folder to FLAC, to save space, for archival purposes. FLAC is only 24 bit, so you have to use 24 bit bounce in Bitwig but if you bounce to 32 then I can't use FLAC anymore to save space. Not a big problem... but would be nice to have WavPack support to compress the 32 bit wav's.

[u-u-u]

But the Bounce/Bounce in place actions still always use WAV, don't they? So no problem there.
For audio export, you are able to choose whether you want to export to WAV or FLAC. So this covered as well.
So what is the problem? But maybe I misunderstood (?)

After I'm done with the track, I convert the wav's in the project folder to FLAC, to save space, for archival purposes. FLAC is only 24 bit, so you have to use 24 bit bounce in Bitwig but if you bounce to 32 then I can't use FLAC anymore to save space. Not a big problem... but would be nice to have WavPack support to compress the 32 bit wav's.

Thanks for clarification! Makes sense.

[SLiC]

Any other users trying BETA 3 on Windows 10

I am getting massive lag when I click on a wave form in the editor and drag to select time etc (almost a second) - never had this before with any other version.

NVidia GTX 980 if it mases a difference

[anoise]

Any other users trying BETA 3 on Windows 10

I am getting massive lag when I click on a wave form in the editor and drag to select time etc (almost a second) - never had this before with any other version.

NVidia GTX 980 if it mases a difference

Can confirm, also lags in zooming in/out on waveforms, and resizing the editor panel. (Win 11)