Bitwig 6 Beta coming soon

[muzicxs]

let the modular tinkerers go to the dozen of other modular hosts out there.

Dozen of modular hosts? Maybe you are confusing modular synths with modular DAWs?

[pdxindy]

Before they added project level modulators, I would have yawned at the suggestion... now I couldn't imagine being without it!

Can you describe a real-world example from your work? It's a sincere, genuine question.

One example... I want to fade 3 tracks down, while bringing 2 others up. On some tracks which keep playing, I want to change the FX mix levels and on arp track, I want to close the filter a bit and shorten Env decay.

I can put all that on one project level macro knob, then when I move from one section of the composition to the next, I just automate that macro knob. It's freakin awesome!

[muzicxs]

Something I saw Tache Teaches do is to have a macro knob called "energy" and use that one macro knob to modulate the intensity of tracks across the entire project. Opening filters, adding distortion, increase feedback on delays, etc. Now you have one knob controlling the intensity of your song. It's indeed freaking awesome as pxindy already pointed out.

[bboxdw]

Before they added project level modulators, I would have yawned at the suggestion... now I couldn't imagine being without it!

Can you describe a real-world example from your work? It's a sincere, genuine question.

By modulating a single project-level macro knob with another project-level modulator, it's possible to apply (and easily change/adjust) identical volume ducking to several tracks or groups of tracks, or to accent certain beats to enhance the groove (e.g., by opening the filter on one track, increasing the volume on another, increasing distortion or other effect on another).

[stoopicus]

Neat. For me this is actually a more natural way to think about automation as well.

[xmstkvr]

Before they added project level modulators, I would have yawned at the suggestion... now I couldn't imagine being without it!

Can you describe a real-world example from your work? It's a sincere, genuine question.

By modulating a single project-level macro knob with another project-level modulator, it's possible to apply (and easily change/adjust) identical volume ducking to several tracks or groups of tracks, or to accent certain beats to enhance the groove (e.g., by opening the filter on one track, increasing the volume on another, increasing distortion or other effect on another).

Thanks, guys. So, is it ok in my head to view this feature as a "parent" controller system to a "child" subsystem of controls? Bascially, a one giant knob that controls other knobs somewhere in the project is that it?

[xbitz]

^^^ + &

[xmstkvr]

^^^ + &

Got it. Thank you! Awesome video and really, really cool feature.

[muzicxs]

Curious what they'll come up with tomorrow!

[Stan Navi]

Curious what they'll come up with tomorrow!

I think, it will be Bitwig 6 beta.

[Gam456]

Curious what they'll come up with tomorrow!

I think, it will be Bitwig 6 beta.

and... 3 month with people asking everyday when the final will be release

[aMUSEd]

Curious what they'll come up with tomorrow!

I think, it will be Bitwig 6 beta.

and... 3 month with people asking everyday when the final will be release

and...3 months of trying to avoid the temptation of upgrading until the final version is released

[pdxindy]

and... 3 month with people asking everyday when the final will be release

I'm usually too busy using the betas to think or care about when it will officially be released

[pdxindy]

and...3 months of trying to avoid the temptation of upgrading until the final version is released

I cannot think of a single reason why I would want to avoid that temptation...

[bboxdw]

Before they added project level modulators, I would have yawned at the suggestion... now I couldn't imagine being without it!

Can you describe a real-world example from your work? It's a sincere, genuine question.

By modulating a single project-level macro knob with another project-level modulator, it's possible to apply (and easily change/adjust) identical volume ducking to several tracks or groups of tracks, or to accent certain beats to enhance the groove (e.g., by opening the filter on one track, increasing the volume on another, increasing distortion or other effect on another).

Thanks, guys. So, is it ok in my head to view this feature as a "parent" controller system to a "child" subsystem of controls? Bascially, a one giant knob that controls other knobs somewhere in the project is that it?

I suppose that's one way of thinking about it. Macro knobs and other modulators at the project level are not confined to a particular group, track, or device, but rather can control any modulation targets at any of those lower levels anywhere within that particular project. (Alongside, of course, being able to control project-level modulation targets.)