Device panel sharing thread

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

Post

I worked out how to share device panels for third party plugins. Normally, on Mac at least, they are in an invisible folder so you need to make folders visible to see it - paths are:

\Users\username\Documents\Bitwig Studio\Library\.settings\devices (Mac)

or

\Bitwig Studio\Library\.settings\devices (Win)

(NB The 'devices' folder is automatically created when you save your first panel, if you have not done that then create the 'devices' folder too in the above paths)

Update - Might be an idea to collect these in one thread. Just choose what you want from the shared Dropbox repository below:

https://www.dropbox.com/sh/ie17173tybqd ... tzeUa?dl=0

they need to go inside the above folders - you must copy over both the 'Default.bwremotecontrols' file and the folder it is in (named vst-xxxxxxxx) as this enables BWS to know the plugin ID. I have zipped them up so that they extract the folder and file as they should be copied.

this will be updated as more get added

Additional device maps posted in this thread -

All device panels by Ixegs can be downloaded from here:

https://github.com/lxegs/bitwig

Device Panels by GoatGirl here:

https://drive.google.com/open?id=0Bz8QI ... kRzcS13VjQ

Device panels by strovoknights here:

https://www.dropbox.com/sh/yapbd3588kyn ... OxVSa?dl=0

--------------------------------------------------------------------------------
Old post

First up is Repro1 VST2 (the VST3 is automapped but currently there is a bug in Bitwig 2 which means you can't browse its presets so I still prefer the VST2, but that had no device pages)

https://dl.dropboxusercontent.com/u/564 ... 525f31.zip

Unzip it and put the device mappings file and the folder it is in inside one of those folders above. Unfortunately these are saved by VST ID not plugin name so although I have some more I need to figure out which is which.

Note this is for device level mappings that will autoload with the device every time it is opened, and, if you have setup an appropriate controller, also automap to that controller. Not the same as preset level mappings which are saved within each preset.
Last edited by aMUSEd on Sat Jul 27, 2019 10:45 pm, edited 11 times in total.

Post

"Where we're workarounding, we don't NEED features." - powermat

Post

I might put them all together when I have some more

Here's one for Zebra 2 - not mapped everything as there's potentially too many user pages for usability, so I have gone for a compromise to reflect the most typical uses - but people can easily add more if they need

https://dl.dropboxusercontent.com/u/564 ... 4d4432.zip

Post

Here's one for ACE - doing u-he plugins first because we can browse them all in Bitwig so having instant access to mapped controls as well make this very convenient.

https://dl.dropboxusercontent.com/u/564 ... 634555.zip

Post


Post

Thanks for sharing! BTW, the path is the same for both Mac and PC. :tu:

Post

So it is - it's just it took me so long to find because it's invisible on Mac

Post

Working on Bazille and Uhbiks but won't be ready till tomorrow some time.

Post


Post


Post

First non u-he plugin - Waldorf Largo

https://dl.dropboxusercontent.com/u/564 ... 453830.zip

Still prioritising plugins that have browser compatibility with Bitwig.

Post

thanks for the effort! really nice..

Post

Last edited by aMUSEd on Tue Mar 14, 2017 12:02 am, edited 1 time in total.

Post

Suloo wrote:thanks for the effort! really nice..
No problem - I find it is always worth investing time to create controller mappings for my most used instruments so as soon as I load them up I can instantly play them with my controller.

Post

Are you only using kore?

Post Reply

Return to “Bitwig”