Bc2000 (for the BCF2000 & BCR2000) group photo

Yahoo Groups archive

Bc2000 (for the BCF2000 & BCR2000)

Index last updated: 2026-04-28 23:16 UTC

Message

Re: Major issues with new BCF2000 - lots of lag and a broken button

2013-02-20 by bconfused2000

Would I do this inside, or just from the outside? I'm not familiar with doing much of that type of thing but I can give it a shot. Is WD-40 similar?

I also tried connecting with MIDI to my audio interface which didnt seem to help the lag at all

--- In bc2000@yahoogroups.com, Joey Robinson <jsrobinson@...> wrote:
>
> Hi all,
> 
> I bought a new BCF 2000 off eBay, (in new condition), and am in need of
> some serious help.
> 
> The rotary knobs themselves have a fair bit of jumpiness or lag compared to
> the BCR I just hooked up. The BCR feels fantastic, with a nice resolution
> to the knobs. The BCF feels jumpy. I've tried everything I can think of and
> have researched on google. I've ran the unit in every emulation mode, I've
> tried straight midi mapping a knob to pan or a send, and also have tried
> using Learn. The Learn button on the BCF seems to not work for mapping most
> of the knobs.
> 
> I am using Win7 x64 and have the latest x64 drivers from the Behringer site
> installed. I've tried with every manner of "Mackie" or "BCF" control
> surface mode in Ableton, as well as tried disabling/enabling the different
> MIDI track options below. I've tried switching USB cables between the BCF
> and BCR, nothing seems to make a difference. The knobs in general are much
> looser on the BCF2000 than the BCR. They have a much worse resolution and
> laggy feel than the BCR. I have no idea what else to try. Oh, and yes I'm
> using the latest 1.10 firmware.
> 
> I am also having an issue where the "left preset" browse button only works
> half the time if in B-Control mode. The button is obviously dying, fresh
> out of box. Are these buttons fixable?
> 
> Thanks immensely for any help.
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.