Bitwig 4.3 is out - Space & Tone (RELEASED)

[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

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

Thanks- its pretty much unusable for me- I have reported to beta@ but I am surprised this slipped though unless they only develop on MACS! (I am assume it isn't a bug on MACS!)

[pdxindy]

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.

CLAP is going to support Bitwig's per voice modulation and voice stacking just like native Bitwig Instruments.

[pdxindy]

-> 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:

Bitwig is already doing that with the CLAP plugin format.

And the easiest feature to give the functionality that Echoes is looking for is to add 1 more target mod curve which is a user curve. Takes up no space, easy to understand, and fulfills the purpose.

[aMUSEd]

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.

CLAP is going to support Bitwig's per voice modulation and voice stacking just like native Bitwig Instruments.

Now I get the name

[summer2000]

This is probably wrong so other will hopefully correct me, but my take...

It doesn't work like like a normal bus or group bus say in Studio One, having had a quick go I made 2 fx (one reverb, one delay) and fed them to another I called 'group'...you have to feed the track in to the fx tracks first (reverb, delay) and what comes is is just the fx (reverb tails and delays etc) but if you mute the 2 feeding fx (the reverb and delay) nothing comes out, so the 'group' fx mix seems dwarfed by the single track fx (if that makes sense!)

You can also add an FX track that has no FX added so you can also have the dry signal.

OK I have fixed it now, you cant mute but you can set the send to pre-fader and the turn the fader on the individual fx down- then you cam just use the 'group' fader to control all FX with one fader (across different levels of sends like a VCA) so it dopes work!

Any chance you can attach some screenshots or a project file with this setup? I'll be using my upgrade license and grab the demo to test it out after I get off work today.

*** Much thanks to you and pdxindy for providing good feedback to my questions. ***

If you wait a couple weeks until it is released, you can then download the demo of 4.3 without using your upgrade and try it out to make sure it works in a way you are satisfied with before activating

I've given it some thought and I think it's best to wait to give the demo a spin before upgrading.

[Echoes in the Attic]

-> 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:

Bitwig is already doing that with the CLAP plugin format.

And the easiest feature to give the functionality that Echoes is looking for is to add 1 more target mod curve which is a user curve. Takes up no space, easy to understand, and fulfills the purpose.

I guess a possible workaround for using multiple expression curves on a VST would be to send each separate curve (split off from the pressure or timbre input) to modulate a different CC signal, and those in turn could modulate VST synth parameters (rather than using Timbre CC74 or aftertouch directly). This would only work polyphonically of course as modulation if the VST could use CC messages as mod sources (some do), otherwise midi learning the cc would be an option for mono sounds.

[SLiC]

Great to see Bitwig and UHE working together on CLAP, they seem to have a very close relationship which can only be good for the Bitwig Community.

[pdxindy]

-> 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:

Bitwig is already doing that with the CLAP plugin format.

And the easiest feature to give the functionality that Echoes is looking for is to add 1 more target mod curve which is a user curve. Takes up no space, easy to understand, and fulfills the purpose.

I guess a possible workaround for using multiple expression curves on a VST would be to send each separate curve (split off from the pressure or timbre input) to modulate a different CC signal, and those in turn could modulate VST synth parameters (rather than using Timbre CC74 or aftertouch directly). This would only work polyphonically of course as modulation if the VST could use CC messages as mod sources (some do), otherwise midi learning the cc would be an option for mono sounds.

Until Bitwig adds a user curve to the existing mod curve options per target, I find it acceptable to use the existing log and exp options, plus the Note Grid curve. That way I can have one target come in first and then the second.

I rarely need that much control and I can use Vital in case I do.

[pdxindy]

I've given it some thought and I think it's best to wait to give the demo a spin before upgrading.

Seems like a good plan... the new Beta 3 has a number of new issues. May as well wait until 4.3 is sorted and stable.

[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

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

Thanks- its pretty much unusable for me- I have reported to beta@ but I am surprised this slipped though unless they only develop on MACS! (I am assume it isn't a bug on MACS!)

OK, weirdly just booted up for the second time and after a lot of scanning working normally now, no graphics lag...I wonder if this has/had to do with background scanning?

[liquidsound]

OK, weirdly just booted up for the second time and after a lot of scanning working normally now, no graphics lag...I wonder if this has/had to do with background scanning?

Mine is as slow as described above. No improvements regardless of rebooting or indexing.
Just a Beta 3 issue to be resolved for sure in Beta 4x

[Trancit]

I have this issue as well... everytime I start Bitwig it starts indexing with quite some huge CPU spikes which sometimes freeze the whole prog for some seconds...

From what I have seen during indexing, CPU load goes inbetween 30-60% which is far too high for my taste for a silly background service I would like to shut off better yesterday than later... which then now and then freezes the whole programm i.e. when trying to load a plugin...

Why do all developers seem to think everybody using their software is too silly to decide themselves when they like to update their database and when not?? I hate this silly auto indexing...
Note only that Bitwig clutters my my local folder with thousands over thousands of index files (count goes far above 80.000) but Bitwig is atm for me unusable the first 2-3 minutes after starting the programm

EDIT: This is how my CPU load looks like since a few versions... I just captured the last few seconds but this keeps going for at least the first up to 3 minutes after I started a new instance of Bitwig where even the little scanning circle indicator freezes when the CPU spikes occur...
And this is on high performance plan so not related to any throtteling:

Index.jpg

[SLiC]

I have this issue as well... everytime I start Bitwig it starts indexing with quite some huge CPU spikes which sometimes freeze the whole prog for some seconds...

From what I have seen during indexing, CPU load goes inbetween 30-60% which is far too high for my taste for a silly background service I would like to shut off better yesterday than later... which then now and then freezes the whole programm i.e. when trying to load a plugin...

Why do all developers seem to think everybody using their software is too silly to decide themselves when they like to update their database and when not?? I hate this silly auto indexing...
Note only that Bitwig clutters my my local folder with thousands over thousands of index files (count goes far above 80.000) but Bitwig is atm for me unusable the first 2-3 minutes after starting the programm

EDIT: This is how my CPU load looks like since a few versions... I just captured the last few seconds but this keeps going for at least the first up to 3 minutes after I started a new instance of Bitwig where even the little scanning circle indicator freezes when the CPU spikes occur...
And this is on high performance plan so not related to any throtteling:
Index.jpg

Yes, this has been an issue for some time also resulting in crashes on windows if you try to shut down when it is indexing (which seems to happen a lot even when I haven't added anything new). I don't really want this in the background unless it takes almost no resource, maybe just have a button go red when indexing is required and we can press it when we go for a coffee...or an option in preferences to turn it off for performance use etc (I have already suggested this to beta@)

[Trancit]

Yes, this has been an issue for some time also resulting in crashes on windows if you try to shut down when it is indexing (which seems to happen a lot even when I haven't added anything new). I don't really want this in the background unless it takes almost no resource, maybe just have a button go red when indexing is required and we can press it when we go for a coffee...or an option in preferences to turn it off for performance use etc (I have already suggested this to beta@)

Yes exactly... I did a report too and asked more or less for the same...

[SLiC]

Yes, this has been an issue for some time also resulting in crashes on windows if you try to shut down when it is indexing (which seems to happen a lot even when I haven't added anything new). I don't really want this in the background unless it takes almost no resource, maybe just have a button go red when indexing is required and we can press it when we go for a coffee...or an option in preferences to turn it off for performance use etc (I have already suggested this to beta@)

Yes exactly... I did a report too and asked more or less for the same...

I also asked about the amount of index and cache files Bitwig keeps, seems they are never...I have over 7000 folders in my Bitwig Index Folder (in User/App data) and more than that in the Cache folder...not sure if this is related to the duration and frequency of scanning or if it can be tidied up (I have had Bitwig since V1 so maybe it just makes a new file very time you boot up!)

I also ran a duplicate finder on the files and there are a lot (and I also have duplicate pre-sets in Bitwig)