Device panel sharing thread (Bitwig remote controls for devices)

[aMUSEd]

Here's one for Respiro

https://www.dropbox.com/s/exo1nhzvp40nf ... 8.zip?dl=0

[aMUSEd]

I've made one for Europa now too

https://www.dropbox.com/s/6v7fj86yrf565 ... f.zip?dl=0

tried to keep this simple so focused mainly on the params that really affect the sound when played live as opposed to modulation params

[aMUSEd]

If you have this as well you can basically get control of everything now in Bitwig

[yassinex]

Just wow !!!!
Discovered this thread. I have an NI KK MK2 and these scripts/pannels are just making BWS 3 a breeeze !!!
Thanks Muse !!!! And othrrs for sharing. Can’t wait getting back home (from holidays) to test all these !!!!

[aMUSEd]

Thanks - nice to get some feedback for once. We really think Bitwig should be including these, it does ship with a few built-in scripts for some third party plugins (mainly things like most u-he plugins and a few by NI) but if they added this library it would cover maybe 90% of VSTs.

Bitwig also need to take on board that it could be made easier to import and export them.

[aMUSEd]

However, if there is anyone feels weird my sharing,I'm stop sharing.

Please don't - I noticed strovoknights is continuing to add device maps to his Dropbox (see first post in this thread) so let's continue to support all contributors please. Thanks

[PsYAuM]

Stupid question;
These are to use device panels with controllers?
The reason i ask is because Bitwig already maps controls in the device panel to the 3rd party VST's controls in it's native window

[aMUSEd]

Stupid question;
These are to use device panels with controllers?
The reason i ask is because Bitwig already maps controls in the device panel to the 3rd party VST's controls in it's native window

Not automatically for third party plugins, except for those that it ships with device maps for, such as some NI and u-he plugins. These fill in the rather huge gaps. What it does do is show a list of all params in that device, but the order they are in is only as organised as the plugin dev set them up, in practice most plugins need some editing of a device map to make control order logical and param names usable.

[PsYAuM]

Stupid question;
These are to use device panels with controllers?
The reason i ask is because Bitwig already maps controls in the device panel to the 3rd party VST's controls in it's native window

Not automatically for third party plugins, except for those that it ships with device maps for, such as some NI and u-he plugins. These fill in the rather huge gaps. What it does do is show a list of all params in that device, but the order they are in is only as organised as the plugin dev set them up, in practice most plugins need some editing of a device map to make control order logical and param names usable.

Ah ok.
Thanks for information.
So it's advisable to use these device Panels anyways even if Bitwig has already Mapped the specific VST?

[aMUSEd]

I tend not to create maps for plugins Bitwig have already done, waste of time plus there's a risk an update could overwrite them. As I said this is aiming more to fill in the gaps, unlike native devices, most third party plugins do not have maps already created by Bitwig.

[daily patcher]

I am new to making these and couldn't find the info easily. How does one go about tagging these panels?

Separately, how does one know which vst folder ID correlates with each plugin once you have saved a mapping?

Thanks!

[aMUSEd]

I am new to making these and couldn't find the info easily. How does one go about tagging these panels?

Separately, how does one know which vst folder ID correlates with each plugin once you have saved a mapping?

Thanks!

Tags are added just by going into the device panel editor and clicking in the space underneath the 8 knobs, then typing.

The easiest method I found of working out the VST name of the map is to open the hidden Devices folder and make sure the view is set to 'Date created' so the most recent folder is on top - then when you save one you know that will be it. I then zip the whole folder, and add the plugin name to the ZIP so I can back it up or share it.

[daily patcher]

I am new to making these and couldn't find the info easily. How does one go about tagging these panels?

Separately, how does one know which vst folder ID correlates with each plugin once you have saved a mapping?

Thanks!

Tags are added just by going into the device panel editor and clicking in the space underneath the 8 knobs, then typing.

The easiest method I found of working out the VST name of the map is to open the hidden Devices folder and make sure the view is set to 'Date created' so the most recent folder is on top - then when you save one you know that will be it. I then zip the whole folder, and add the plugin name to the ZIP so I can back it up or share it.

Cheers! Bit of a pain the VST IDs are but ah well. I started out with an easy project:

Kilohearts snapins: https://drive.google.com/open?id=1OeG-5 ... oCTDzfVXxN

Not all of the mappings are particularly useful obviously but now that I am using these mappings extensively with a controller they are nice to have. I included a default preset for each device to open the mappings by default so delete or override as needed.

[aMUSEd]

Thanks - I don't have these. I'd imagine there are extra complications with something like Snapins as they function as independent plugins but are really meant to be used combined. What happens in terms of parameters control when combined, is there some sort of standardised param order (as in SpectrumWorx where the order of params exposed to the host is based on module position in the matrix) or at least macros like in Home, so you can setup consistent mappings?

[aMUSEd]

Also did you map by device or by preset? If the former then you don't really need default presets as the same mapping is auto set up when the same plugin is loaded each time, regardless of preset.