Mr. Disable & Dr. Hide - Bitwig Tutorial

[polarity-dnb]

After you bounced down some crazy cpu heavy device chains, don't delete them. Use disable & hide to archive tracks inside your project without clogging up cpu & interface.

https://www.youtube.com/watch?v=zU6JD5Olzqs

[Hez]

Nice one for pointing this out, useful tip that I have made good use of in the past!

One enhancement that would be really nice would be for Bitwig not to instantiate deactivated plugins on project load until each specific plugin/track is reactivated. 90% of project load time for me is absurd plugin chains, most of which are deactivated by the time I'm halfway through a project. I'll usually only want to reactivate a couple of these in any given session.

I submitted a feature request for this and whichever dev responded (can't remember who) mentioned that they were also thinking of implementing that, so if a few more people submit feature requests we might get it ; )

[polarity-dnb]

One enhancement that would be really nice would be for Bitwig not to instantiate deactivated plugins on project load until each specific plugin/track is reactivated. 90% of project load time for me is absurd plugin chains, most of which are deactivated by the time I'm halfway through a project. I'll usually only want to reactivate a couple of these in any given session.

yes +1 would appreciate that

[bolba]

Hez, but in that case if you'd like to activate all / a lot of chains at once - you'll need to wait on that action?
I'd rather wait during project load than after actions.

Though it can be option/checkbox in settings.

[craigtumps]

I never even noticed this before .

Could also use it for versioning instead of saving lots of the same project.