mapping midi controller to vst params

[ioscommuter]

I have used instrument racks with push to control 8 parameters on a vst plugin, but I want to use a contoller with more knobs and assign them to more than 8 parameters in a vst. I recently purchased a Behringer bcr2000 which has 24 knobs, but am having trouble with mapping it to the vst controls on an ableton plugin. I detailed my issues with that here: viewtopic.php?f=1&t=166562&p=1543471&hi ... 0#p1543471

Does anyone have experience accessing controls on vst plugins in ableton outside of using instrument racks? Are there any tutorials on this subject?

[yur2die4]

Sometimes that 'most recently selected parameter being controlled' thing happens when you use a remote script which allows instant control of the first 8 parameters. But, only have one knob.

However, your particular case seems really odd.

Which controls are you mapping? The ones on the very top of the controller?

I wish I could be helpful, but I haven't used that device before.

[ioscommuter]

I am using regular rotary encoders on the bcr2000, not the top row, but the second. I have tried using two vsts: massive and sylenth, both with the same result. In the bcr2000's learn mode you first set the knob on the device, then turn a virtual knob on the vst to map it. Im wondering if the vsts are not sending different cc numbers for their different parameters?

[revoltcrew]

this may be of help. if you have maxforlive.....
http://www.maxforlive.com/library/devic ... 00-control

i have a bcr2000. my workflow:
expand the plugin parameter configure panel,
put what i want to map there,
and simply map from that...
this way i don't have to continue mousing all over the vst..
and then there's the Options.txt file, wherein you can add this:

"PluginAutoPopulateThreshold"

Auto-populates the plugin parameter list if a plugin has a number of less or equal than X parameters

Default = 32
Min = 1
Max = 128

"-1" will always populate the list with max. 128 parameters, regardless how many parameters the plugin has (= similar to Live 7 behaviour)

Supported since: 8.1.1

Example: -_PluginAutoPopulateThreshold=32
https://www.ableton.com/en/articles/opt ... file-live/

seen here is my options.txt file in action on aalto, listing all the available parameters to map instantly. without a mouse click.

[ioscommuter]

Thank you revoltcrew. can you give me some detail on mapping the bcr2000 encoders to the parameter configure panel? Are you using the "learn mode" in bcr2000, or manual mapping? is it on the u1 setting for use with usb? I am just getting started with the bcr2000, so the more detail the better. thanks.

[revoltcrew]

Thank you revoltcrew. can you give me some detail on mapping the bcr2000 encoders to the parameter configure panel? Are you using the "learn mode" in bcr2000, or manual mapping? is it on the u1 setting for use with usb? I am just getting started with the bcr2000, so the more detail the better. thanks.

right..
the only time i use "learn Mode" is when a vst's parameters don't automatically show up in the Configure panel when expanded, thus forcing me to right click on a paramter and "midi-learn" it.

once the plugin configure panel is filled with the parameters of the vst i want to map.
i manually map from there. this way, i have total control of selected parameters, without clicking on the vst unless necessary.

as in the case of the arp2600v, its parameters don't show up for me automatically like Aalto's do.,
so i set up a bcr2000 preset (with every button/knob set as a CC) specifically for that vst,
so i have to click around the plugin to get things mapped- 1st clicking on the plugin, and then turning the bcr2000 knob.

U-1 should suit you fine, if you're simply controlling software vst's, via usb yes.
that should get you started fine.

some folks use Automap. i haven't done that.
i chose a preset, say P-16, go through each knob/button and make sure they are simple CC's. save it. and then its a blank template to which i can apply to any plugin, rack, etc.

[revoltcrew]

make your own presets. they will save with the set you build in Live.
thus with each set, the plugins/mappings will load.
i use it conjunction with an APC40, so my instrument racks always have a automatic blue-hand for their macros,
thus leaving the bcr2000 for all the fun stuff!

cheers
off to work for the day.
i'll check in again after to assist you further.
i recommend you do Not use the built bcr2000 template for Live. its shite.

just in case, bookmark this-http://www.behringer.com/EN/downloads/p ... 6_M_EN.pdf

[ioscommuter]

I am having trouble with getting my mappings to save. I use the config in the instrument rack, and then midi map it, but the mappings dont save. I have also tried saving a preset in massive (the plug-in i'm mapping at the moment) but even after opening that preset in the instrument rack, the mappings are not there.

[broose masterwerk]

I have the same problem it wont save that... have 2 map it again and again... did u guys found a answer 2 this? G

[yur2die4]

They don't save except within an actual set.

The closest you can get to saving a Configured layout is to group the instrument into a Rack and save the rack into your user presets.

You won't have actual midi mappings saved. But it will retain the configure faders.

After that it really comes down to your controller method. Unfortunately midi mapping can't be saved in one moment and loaded into another set.

This is where the blue hand comes in handy. Generally you could either assign things to macro knobs, or just be on the vst itself to be able to control it if you have control surface support on your device. (Some people have even made scripts that support this beyond 8 knobs!)

Otherwise you'll pretty much always have to remap every time you load it.

Edit: there actually is one more option. Instead of mapping within Live, some vst's let you map within the vst itself. This is very different from mapping within Live. It takes some experience understanding the different results you'll get in this case. But it is actually very flexible of you begin implementing it!

[aspsa]

yur2die4,

> Otherwise you'll pretty much always have to remap every time you load it.
Is this still the case with Ableton Live 9.1.7?

I just discovered your post. Here is my related post: viewtopic.php?f=1&t=210133.