Compression Sidechain effect using native bitwig plugins

Hi @BOJ,

What particular aspect of this technique is the problem in Bitwig?

Hi @BOJ,

I've attempted to recreate the preset in the first video. I've made an adjustment, by chaining two dynamics compressors in serial because one dynamics device on it's own was not cutting the reverb volume fully. The other thing I would suggest is that you try another reverb (personally I think the Bitwig Reverb Device is garbage, you can get better ones for free on KVR:
https://www.kvraudio.com/plugins/instruments/effects/hosts/newest).

I've uploaded the preset I made to this website: https://bitwiggers.com (sticklebrick: Side Chained Reverb)

Let me know if it sounds any good, if it doesn't, then we can look at why, & how to make it better.

Hi @BOJ,

Bitwig devices differ to Ableton's so there will be differences but the principles are the same. Spend some time familiarising yourself with the differences. Watch some tutorials online. Break down the preset I made into smaller parts to see what each section is doing. Practice building your own simpler devices first.

Bitwig has a dedicated Mid/Side Splitter device for handling Mid/Side. It has two internal chains, you can add/view any nested device chains inside it, by clicking on the dark grey boxes labelled Mid or Side. The 2 knobs adjust the volume of Mid or Side.

I routed the output of the Mid Side Device to the Dynamics Sidechain inputs. I could have routed the output of say the synth feeding the whole Side Chained Reverb (SCR), but doing this would have meant that this would need to be re-assigned every time I load up the SCR, the way I've done it, it is automatically routed when loaded up.

Probably the reason why you're a bit confused, is the way that a lot of Bitwig devices have internal chains built in, allowing devices to be nested within devices nested within other devices and so on..... Once you get you head around this, it is actually a very powerful workflow. The colour coded brackets above each device help you to keep track of where each device is nested. I also try to think of nested devices as "children" of the "parent" device they are nested inside of. Nesting devices in this way also allows you to make the most of Modulators and Device Remote Controls Pages (Device Remote Control Pages is another subject I recommend you study). For example: A Modulator or Remote Control in a "parent" device, can be assigned to any parameter of any nested "child", "grandchild" or "great grandchild " device, and so on. Setting up Modulators and Remote Control Pages at higher levels to control key parameters, means you don't have to go digging down into your nested devices to make adjustments.

I will leave it there (TLDR). I hope this has been helpful.

https://www.bitwig.com/en/community/learning.html

In Ableton many things had to be made in multiple steps, while in Bitwig it can be done way faster and simpler. For one thing, there's ready made mid-side split device, so you can start putting your effects on mid and side right away. Second, by utilising modulators you can sidechain anything from anywhere in the project. You really need to see all the tutorials for Bitwig before trying to apply Ableton Live workflow. I don't even see the point in having Bitwig without understanding the difference and why/where it's better, where it's not.

Reverb + Tool Left Bottom of "Tool" Choose "Show modulators" Choose Audio Sidechain or even better: Note Sidechain, and connect this to the "Amplitude" Of Tool and drag it down... Make sure the incoming signal is from one of the midi's you play...... this is imo way cleaner and more controllable then with Ableton... One of the best features of Bitwig!

Learn to do this fast, and its even easier.