BCR2000 led indicator problem

LLR3 · Joined: Sep 10, 2004 Posts: 41 Location: Helsinki Finland

I decided to go with the flow and got myself a Behringer BCR2000.

I´ve now allocated the topmost eight buttons to send variation change commands on CC #70. For some reason the led indicators on the buttons start acting in a very peculiar manner if I set the second value to OFF position. If both values are the same (0,0; 16,16; 32,32; ...) the leds work correctly, but naturally not in a "radio button fashion" as would be desirable.

The firmware I´m using is 1.10., but I also tried 1.07 and results were identical.

Is this sort of behaviour common to all units running this firmware revision or is this particular unit defective?

*LLR3

PS. If the CC bulk send from BCR works the way I expect it to, I think I´ll be able to construct a reasonably elegant system for copying variations on the fly without the need to use the editor!

cappy2112

mosc

LLR3 · Joined: Sep 10, 2004 Posts: 41 Location: Helsinki Finland

I noticed that the leds are actually monitoring what´s going out i.e. if several encoders have been set on the same CC#, all led collars will react when only one of the knobs is being twiddled.

That might somehow explain the strange behaviour of the button leds when all of the buttons have been set on the same CC# (in this case #70).

*LLR3

cappy2112 · Posted: Fri Jun 10, 2005 2:20 pm Post subject:

Afro88 · Posted: Fri Jun 10, 2005 4:20 pm Post subject:

cappy2112 · Posted: Fri Jun 10, 2005 5:09 pm Post subject:

cappy2112 · Posted: Fri Jun 10, 2005 5:15 pm Post subject:

cappy2112 · Posted: Fri Jun 10, 2005 5:21 pm Post subject:

sheridan · Posted: Sun Jun 12, 2005 8:33 am Post subject:

Hi there.

I have recently been creating a monster patch for the G2 with almost every parameter set up on the BCR2000, which I'll post when complete, so look out for that. (sorry, not trying to sound arrogant).
Anyway, if you want a different button for each variation, you need to divide 127 by 8 and add this number to each consequetive button. The thing is that you need to set BOTH max and min values to each button's 'unique' number.
Still, it's much quicker to use the BCR2000's learn function, and even better still to (as someone said earlier) just use one knob instead.
Seriously though, I have literally spent days sorting out this patch and arranging the knobs and buttons in 'logical' positions that mirror the on screen modules' knobs. The G2 patch is a 3 Osc, 3 Env, 3 LFO, 2 Filter, with saturation and multiple modulation choices virtually ALL UNDER CONTROL FROM THE BCR2000!!

Anyway, I hope that first bit helped you out.

Kind regards,

Sheridan

sheridan · Posted: Sun Jun 12, 2005 8:46 am Post subject:

Oops. Divide 128 by 8, I meant. Still it might not be that exact. I've noticed that you need to set a knob to INC 64 for 2 places, 42 for 3, 31 for 4 and 24 for 5, ie. 5 shape selections in an Osc. So it may well not be 8, 16, 24, 32, etc. for the variations, but it's still quicker to use the learn function.

Kind regards,

Sheridan

sheridan · Posted: Sun Jun 12, 2005 9:13 am Post subject:

I just tried it. You need to use 16,32,48, etc. if your still interested.

Sheridan

cappy2112

sheridan · Posted: Mon Jun 13, 2005 6:48 am Post subject:

Upgrading the firmware always restores the factory presets, so you need to save/dump them to a P.C. first.
I know this won't actually help you, but 1.10 works ok on my BCR. Interestingly, I can't get the BCedit app to send data to my BCR, no matter which firmware it was running! Can you?

Kind regards,

Sheridan

cappy2112 · Posted: Mon Jun 13, 2005 8:53 am Post subject: