Plugins help - Gaffel & Captain Chords

Official support for: bitwig.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Hii there. :)
My Gaffel plugin:
https://klevgrand.se/products/gaffel/
& Captain Chords
https://mixedinkey.com/captain-plugins/captain-chords/ does work, but not like they should.

When you add a Gaffel and another Gaffel, they should "speak" to eachother. Be linked.
Same with Captain Chord when you add a "Captain Chord and Captain Deep.
And they work in Reaper, Reason and Fl Studio but not in Bitwig.

Something i havent turned on or something? Same for you who uses one or both of these plugins?

Post

Could be the "Independant plugin host process" feature of Bitwig blocking the cross plugin communication.
Go into settings/Plug-ins and check or uncheck the tick-box for your plugins.

Post

I don't use them, but you may have to use the "Only as Bit Bridge" setting for plugins. Normally I'd advice to use the "Each plugin" setting, so each plugin runs in it's own sandbox and can be recovered individually when crashing. But when they need to talk via in-process communication, "Only as Bit Bridge" runs 64 Bit plugins (if you run a 64 Bit OS) inside the audio engine like most other DAWs. If they crash, the whole audio engine will crash too (not the BWS GUI though, so you can simply restart it).
See if that helps.

Cheers,

Tom
"Out beyond the ideas of wrongdoing and rightdoing, there is a field. I’ll meet you there." · Rumi
UrbanFlow.art · Instagram · YouTube

Post

You can also use the middle option for plugins, which says 32-bit/64-bit or something like that. This puts all the 32-bit plugins in one sandbox, and all the 64-bit plugins in a second sandbox. So if one of your 32-bit plugs crashes, it will only crash the other 32-bit plugs. Same for the 64-bit plugs.

TL;DR - Any plugs that have the ability to talk to multiple instances of itself across a project must all be run together in the same sandbox and shared memory space. So if it’s a 32-bit plug you MUST choose the 32-bit/64-bit middle option. And if it’s a 64-bit plug then you can choose either that middle option or the “bit-bridge” option. And in both cases you must ensure that the plug does not have a check mark in the big list of plugs.

Post

Glad i saw this. Was just lookin at getting captain chords....dont think i will bother now. Scaler it is!
Just doesnt seem to make sense if i have to change a global setting.
Would be intereted to know how you got on, though
Cheers

Post

Captain Chords runs fine in any type of plugin mode. It's when Captain Chords wants to talk to any of the OTHER "Captain" plugins that it needs to share the same plugin host process as the other plugs it's talking to.

It's very simple. ANY plugin that needs to talk to other plugins needs to be set to the middle mode.

Post

Yokai wrote: Fri Jan 04, 2019 11:51 pm Captain Chords runs fine in any type of plugin mode. It's when Captain Chords wants to talk to any of the OTHER "Captain" plugins that it needs to share the same plugin host process as the other plugs it's talking to.

It's very simple. ANY plugin that needs to talk to other plugins needs to be set to the middle mode.
And i suppose i could just change the setting when im using captain plugs and then change back when im done with it.....

I got scaler and honestly, im underwhelmed. What i like about the captain plugs is that you can actually get an idea going and change notes around easily....much more of an integrated songwriting tool.

Post

DavidCarlyon wrote: Sun Jan 06, 2019 3:52 pm
Yokai wrote: Fri Jan 04, 2019 11:51 pm Captain Chords runs fine in any type of plugin mode. It's when Captain Chords wants to talk to any of the OTHER "Captain" plugins that it needs to share the same plugin host process as the other plugs it's talking to.

It's very simple. ANY plugin that needs to talk to other plugins needs to be set to the middle mode.
And i suppose i could just change the setting when im using captain plugs and then change back when im done with it.....

I got scaler and honestly, im underwhelmed. What i like about the captain plugs is that you can actually get an idea going and change notes around easily....much more of an integrated songwriting tool.
No need to change settings back and forth.

Step 1. Choose the middle “32-bit/64-bit” option in Preferences > Plugins.

Step 2. Click the checkbox at the very top left of the long list of plugins to globally select them all for individual sandboxing.

Step 3. Scroll down through the list, and for any plugin you have that you know needs to communicate with other plugins, uncheck them in the list.

With this setup, all your plugins that need to run In the same host process and share memory for inter communication will do so. Everything else will be sandboxed.

Or if you want to keep it simple just pick the middle 32-bit /64-bit option and UNcheck everything in the big list. Problem solved.

Post

Yokai wrote: Tue Jan 08, 2019 5:01 am
DavidCarlyon wrote: Sun Jan 06, 2019 3:52 pm
Yokai wrote: Fri Jan 04, 2019 11:51 pm Captain Chords runs fine in any type of plugin mode. It's when Captain Chords wants to talk to any of the OTHER "Captain" plugins that it needs to share the same plugin host process as the other plugs it's talking to.

It's very simple. ANY plugin that needs to talk to other plugins needs to be set to the middle mode.
And i suppose i could just change the setting when im using captain plugs and then change back when im done with it.....

I got scaler and honestly, im underwhelmed. What i like about the captain plugs is that you can actually get an idea going and change notes around easily....much more of an integrated songwriting tool.
No need to change settings back and forth.

Step 1. Choose the middle “32-bit/64-bit” option in Preferences > Plugins.

Step 2. Click the checkbox at the very top left of the long list of plugins to globally select them all for individual sandboxing.

Step 3. Scroll down through the list, and for any plugin you have that you know needs to communicate with other plugins, uncheck them in the list.

With this setup, all your plugins that need to run In the same host process and share memory for inter communication will do so. Everything else will be sandboxed.

Or if you want to keep it simple just pick the middle 32-bit /64-bit option and UNcheck everything in the big list. Problem solved.

Oh cool! Thats great, thanks a lot for that. Never done this before so that is really useful info.
I moved over from ableton late summer...and I'm still finding out so much with Bitwig.
every time i think 'NOW I'm using it to its fullest' i find out about a whole load more stuff. Awesome

Post Reply

Return to “Bitwig”