Ableton Forum

Hi, I recently got myself a behringer bcr2000 to use alongside my notation nocturn25 and launchpad. No problems getting everything hooked up and going. However today I set about mapping the whole thing for a project and came across some problems.

Some of the buttons and knobs have the same midi note name. So when press a button, it effects 2 things... But I have no idea how to sort this??

Also I have some of the buttons set to mute tracks. I hit the button to mute, fine. Hit it to turn back on, and it'll only stay on if I hold the button down? In the midi mappings menu you have the 2 values you can edit. Different combinations make the track stay on, off, or to stay on or off if you hold the button down. No click for on, click again for off. Any suggestions here?

Thanks
Tom

you have two problems.
for the first one, simply change the midi channel the bcr2000 is sending/receiving on.
for the second problem, you have a button set to instance (or whatever it's called). You can change how the button responds but you'll have to read the manual as I forget how to do it off the top of my head.
Both are simple fixes.

Keep in mind that you'll have to remap since you'll be changing the midi chans.

Hi, thanks for the response!

I'll give that a try. But why would some midi channels give buttons the same name, and others not?

The manual came in every language except English.. Sure I'll be able to download though.

Hopefully that'll all work and I'll be done with a big thankyou If not, I'll be back later

wotnwhy wrote:Some of the buttons and knobs have the same midi note name. So when press a button, it effects 2 things... But I have no idea how to sort this??

Live combines MIDI messages together for mapping, so if the Nocturn and BCR send the same message on the same channel, Live won't distinguish between them. C5 on channel 7 is the same mapping regardless of what controller sends it. The simplest way to avoid this is to program one controller to stay on a different channel so they never conflict.

Also, the BCR's MIDI configuration is very flexible and there's nothing stopping you from assigning the same MIDI message to more than one knob or button on its built-in editor. Heads up :)

wotnwhy wrote:Also I have some of the buttons set to mute tracks. I hit the button to mute, fine. Hit it to turn back on, and it'll only stay on if I hold the button down? In the midi mappings menu you have the 2 values you can edit. Different combinations make the track stay on, off, or to stay on or off if you hold the button down. No click for on, click again for off. Any suggestions here?

I forget exactly how the specifics of this work so my explanation might be a bit off, but generally you map either note or CC data, and so the relevant events are note on/off or a CC with either a high or low value (CCs are "continuous" controller message that are sent with a value from 0 to 127).

Live can either have the state of the button match the last message that was sent (note on or high CC means the button is on), or it can toggle the state of the button each time it gets such a message. On top of this, the BCR buttons have more than one mode, which you can change with the "toggle" property in the editor. In one mode (toggle off, I think) they send note on (or CC 127) whenever you push the button, and note off (or CC0) whenever you let go. In another mode (toggle on, I think), every time you push the button, it sends the opposite message. The idea is you can program the controller to match what the software is expecting, but you have to figure that out.

It sounds like your problem is related to this. Check the BCR manual for a good description on how to program this, it's pretty straightforward once you get the hang of it.

Best of luck!