Bitwig 4.3 is out - Space & Tone (RELEASED)

[summer2000]

After watching a bunch of videos on the new 'delay+' I caved and bought the update (I was going to wait for the Summer sale but I have next week off (double bank holiday- thanks UK Queen!) so want it now!

I had missed the last update as well, so I get a bunch of + effects and midi grid...I must admit the new fx sound amazing, delay+ in particular...as a guitarist I can pretty much get anything I want from Bitwig natively now which is pretty amazing....glad to be back up to date with an entire year of free stuff to come

I still haven't taken the leap and upgraded my subscription yet. Mind testing this out for me when you get a chance?

In a test project, create a few send fx tracks and then route the output of a few of them to another send track as to create a group mix bus. Also will a similar setup work with audio/instrument tracks in one group folder with send tracks in another group folder? I'm trying to replicate the workflow I use in Cubase/Nuendo and S1. Please let me if this works. Thanks in advance.

[pdxindy]

After watching a bunch of videos on the new 'delay+' I caved and bought the update (I was going to wait for the Summer sale but I have next week off (double bank holiday- thanks UK Queen!) so want it now!

I had missed the last update as well, so I get a bunch of + effects and midi grid...I must admit the new fx sound amazing, delay+ in particular...as a guitarist I can pretty much get anything I want from Bitwig natively now which is pretty amazing....glad to be back up to date with an entire year of free stuff to come

Yeah, the + fx are impressive. Btw, in Poly Grid, the Phaser+, Flanger+ and Chorus+ can be per voice. Very cool (though does hit the cpu a bit)

Note Grid is also useful for lots of tasks. For example, if you want to filter out just CC#11 from incoming midi, now you can. Want to add expression curves for any MPE synth, check. Constrain incoming midi to any scale (ones not covered by Key Filter)? Yup.

Note Grid doesn't need to be complex generative sequences. It has a lot of uses. I really couldn't do without at this point.

[pdxindy]

I still haven't taken the leap and upgraded my subscription yet. Mind testing this out for me when you get a chance?

In a test project, create a few send fx tracks and then route the output of a few of them to another send track as to create a group mix bus. Also will a similar setup work with audio/instrument tracks in one group folder with send tracks in another group folder? I'm trying to replicate the workflow I use in Cubase/Nuendo and S1. Please let me if this works. Thanks in advance.

You can now send FX tracks to other FX tracks, so yes, you could make a mix bus. You can also send an FX track to itself or in a feedback loop between 2 FX tracks (BE CAREFUL!!).

The basic hierarchy is the same. You cannot send from one group to another group.

[summer2000]

I still haven't taken the leap and upgraded my subscription yet. Mind testing this out for me when you get a chance?

In a test project, create a few send fx tracks and then route the output of a few of them to another send track as to create a group mix bus. Also will a similar setup work with audio/instrument tracks in one group folder with send tracks in another group folder? I'm trying to replicate the workflow I use in Cubase/Nuendo and S1. Please let me if this works. Thanks in advance.

You can now send FX tracks to other FX tracks, so yes, you could make a mix bus. You can also send an FX track to itself or in a feedback loop between 2 FX tracks (BE CAREFUL!!).

The basic hierarchy is the same. You cannot send from one group to another group.

Thanks pdxindy for the quick response. Do you know how close the beta version is to being fully polished for final release? I'm debating whether to renew my subscription now or wait for the final version.

[SLiC]

In a test project, create a few send fx tracks and then route the output of a few of them to another send track as to create a group mix bus. Also will a similar setup work with audio/instrument tracks in one group folder with send tracks in another group folder? I'm trying to replicate the workflow I use in Cubase/Nuendo and S1. Please let me if this works. Thanks in advance.

I haven't had long to play (I had forgotten this was a new feature- lost in reverb/delay+ guitar fun

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!)

A group mix for me is sort of '1 slider' for all reverbs in a group etc...Bitwig doesn't have a mixer like like S1/Cubase etc with relative VCA mixers etc (that I know of), I would say its more of a creative mixer! Its fun feeding the delay back on its self though, and you can but delay tails in to reverb and have some of the delay unaffected by reverb for example...

PS- It does seem like something that could easily be used for a little 'cross talk' to simulate the old analogue mixers...that's a paid extra in S1

[pdxindy]

Thanks pdxindy for the quick response. Do you know how close the beta version is to being fully polished for final release? I'm debating whether to renew my subscription now or wait for the final version.

I'm not finding a lot of bugs but there are still some. My guess is 2 weeks, but maybe 3

[pdxindy]

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.

[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.

Would you mind attaching a simple project file demonstrating how this would work? I'm having a hard time grasping the concept. I may just go ahead and renew my subscription since I've already bought the license and been sitting on it for over a year. Don't really have much to lose at this point. Might as well have some fun with the new toys in Bitwig.

[SLiC]

Now Beta 3...interesting all about sends and being able to turn them off so
Release may be a bit closer!

Changes in Bitwig Studio 4.3, Beta 3

NEW FEATURES

FLAC files can now be directly played back across Bitwig (in clips, by Sampler, etc. etc.)
Sends can now be toggled on/off individually:
Click the name of any track/channel's send to toggle that send off/on
SHIFT-click any track/channel's send to toggle all sends
A new function, Disable All Unused Sends, disables any unused sends in the project, which minimizes CPU-usage/latency
Sends in new projects are now disabled until used (by an initial knob turn)

IMPROVEMENTS

Linux: Debian package (a DEB file) is available again for Ubuntu distributions in addition to the Flatpak bundle
Added support for compressed WAV files (such as those not in PCM or float formats) [8604][21352]
Adding an instrument to an audio track no longer forces conversion to a hybrid track
Invoking the Rename function on audio events will now open a dialog to rename the audio file itself
CC In Grid module: Now has MIDI learn functionality for setting the CC message and channel to use
Layered editing of audio tracks no longer allows resizing the lanes when the auto-size mode is on (it was too easy to do this accidentally)
Added button to stop an active trial phase [28446]

FIXES

Delay+ device: Was not forwarding notes to devices in the FB FX slot [28605]
Convolution device: Window footer line now for start / end times now display proper values [28615]
Union (Oscillator) Polymer/Grid module: Now has a remote control page [28609]
Low-pass MG (Filter) Polymer/Grid module: Input stage was noisy around the clip level [28552]
Sallen-Key (Filter) Polymer/Grid module: Was adding some clicks [28611]
AD (Envelope) Polymer/Grid module: Loop mode wasn't working when Model was set to the Analog or Digital modes [28608]
Test Tone device: In Dirac mode, impulses were not steady when using with a Time Shift device. In an FX Layer. [28619]
Note Out (I/O) Grid module: Sending a note on with velocity of 0 % now creates a note (the same as with Bitwig's note events); now only negative velocity values will fail to produce a note with Note Grid, etc. [27984]
Note Out (I/O) Grid module: Routing an envelope signal to the Gain In port expression was creating a pop [28618]
FX Layer device: Solo state was not remembered when reloading a project [28553]
Rare crash when quitting Bitwig Studio while importing impulses [28544]
Clip Launcher clips could drift out of time with arrangement loop active [28607]
Inconsistent "meta clip" (on group tracks) selection behavior [28296]
Sliding clip content no longer affects track automation [28425]
Reversing a clip no longer affects track automation [28428]
Audio events could get inserted into the same clip when moving a multiselection in layered audio editor [28339]
Wrong loop region length could happen after consolidating a clip with an odd time signature [28347]
32-bit float WAV files could be clipped on import [28338]
Some corrupt WAV files weren't loading [26961]
Glitches when drawing a spectrum display in certain modes [28621]
Notes with velocities below 0.39% were not being sent to VSTs anymore [28610]
Was crashing when scrolling scenes on a controller while Mixer Panel was visible but the Clip Launcher was hidden [28561]
Fixed a crash with an error message when renaming a file
Windows: Crash in certain circumstances when a spectrum display is shown on AVX processors [28526]

[SLiC]

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!

[Echoes in the Attic]

After watching a bunch of videos on the new 'delay+' I caved and bought the update (I was going to wait for the Summer sale but I have next week off (double bank holiday- thanks UK Queen!) so want it now!

I had missed the last update as well, so I get a bunch of + effects and midi grid...I must admit the new fx sound amazing, delay+ in particular...as a guitarist I can pretty much get anything I want from Bitwig natively now which is pretty amazing....glad to be back up to date with an entire year of free stuff to come

Yeah, the + fx are impressive. Btw, in Poly Grid, the Phaser+, Flanger+ and Chorus+ can be per voice. Very cool (though does hit the cpu a bit)

Note Grid is also useful for lots of tasks. For example, if you want to filter out just CC#11 from incoming midi, now you can. Want to add expression curves for any MPE synth, check. Constrain incoming midi to any scale (ones not covered by Key Filter)? Yup.

Note Grid doesn't need to be complex generative sequences. It has a lot of uses. I really couldn't do without at this point.

I haven't been using the grid at all. Interested how you added curves for plugins. I guess you can only do a global mpe expression curve. Still could be useful. Which module was it? The curve module or something? I think I used it once.

[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. ***

[pdxindy]

Note Grid is also useful for lots of tasks. For example, if you want to filter out just CC#11 from incoming midi, now you can. Want to add expression curves for any MPE synth, check. Constrain incoming midi to any scale (ones not covered by Key Filter)? Yup.

Note Grid doesn't need to be complex generative sequences. It has a lot of uses. I really couldn't do without at this point.

I haven't been using the grid at all. Interested how you added curves for plugins. I guess you can only do a global mpe expression curve. Still could be useful. Which module was it? The curve module or something? I think I used it once.

What do you mean only a global MPE expression curve? You put a Note Grid device before a synth (native or VST), add a Curve module (under Shaper) in-between Pressure In and Pressure Out and shape the curve how you want. That is individual for each instance.

And if you want to go a bit crazy, the Curve nodes are modulatable so you could have the curve change depending on the velocity of the note you play!

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.

[pdxindy]

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

[Echoes in the Attic]

Note Grid is also useful for lots of tasks. For example, if you want to filter out just CC#11 from incoming midi, now you can. Want to add expression curves for any MPE synth, check. Constrain incoming midi to any scale (ones not covered by Key Filter)? Yup.

Note Grid doesn't need to be complex generative sequences. It has a lot of uses. I really couldn't do without at this point.

I haven't been using the grid at all. Interested how you added curves for plugins. I guess you can only do a global mpe expression curve. Still could be useful. Which module was it? The curve module or something? I think I used it once.

What do you mean only a global MPE expression curve? You put a Note Grid device before a synth (native or VST), add a Curve module (under Shaper) in-between Pressure In and Pressure Out and shape the curve how you want. That is individual for each instance.

And if you want to go a bit crazy, the Curve nodes are modulatable so you could have the curve change depending on the velocity of the note you play!

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.