Well, some success! I copied the values for the 4 encoder groups directly from my BCR over to my BCF - saved the changes, and presto, the encoder knobs seem to respond a lot better. I still have no idea what value actually was causing the problem - as the resolutions were set to 96 by default, but if you look at that screenshot, other values seemed to not be consistent. Before I go tearing into this thing I thought I'd ask - does anyone have experience with if the encoder knobs themselves can be physically tightened? (I've seen discussion on how to fix the faders around the net, but no one has mentioned the knobs.) If anyone has experience with the inside of these units, can the knob "tightness" actually be adjusted? Does anyone have any template setup files for Ableton already cooked up? My ultimate goal is to control faders, panning, and sends, with one column controlling a channel. Figure I'd like to do sends with the BCR and faders/panning with the BCF. Thanks so much for all the help guys, seems like I'm getting closer. --- In bc2000@yahoogroups.com, "bconfused2000" <jsrobinson@...> wrote: > > Hm. I noticed something odd. Even though the resolutions on both B-Controls show up as 96 in that screenshot I posted, the BCF turns "faster" (with less resolution) than the BCR knobs. I have to turn a knob on my BCR a good bit farther (which I don't mind) to reach the same point that the BCF reaches with less of a turn. > > Not sure what might be affecting that. > > --- In bc2000@yahoogroups.com, "bconfused2000" <jsrobinson@> wrote: > > > > Hi all, > > > > Thanks for the replies. I think I have successfully downloaded my presets into BCManager. I've looked over the resolution setting, and both are set to 96 from what I can see. The "defaults" and "LEDs" settings aren't the same betwee the two, would that be a concern? > > > > I took a screenshot in case that might make it easier to diagnose. I tried changing my global ID to 1 and 2, as I noticed they were set to 1 and 8. > > > > Just wanted to see if anyone notices anything I should try changing in this screenshot (or otherwise.) The seller has offered to refund me for the unit, but I just wanted to give the software end of troubleshooting some due diligence to save us both some hassle if possible. > > > > I was hopeful for that resolution setting, but it does seem that column is identical between the two B-Controls. Anything else look off? > > > > Here's a screenshot link: http://i.imgur.com/s5XWOrQ.png > > > > --- In bc2000@yahoogroups.com, "Royce" <rpcfender@> wrote: > > > > > > Hi Joey > > > I'm afraid that I mainly use my editor which is a bit tech and Mark's is much better for most people, but here goes > > > > > > Start BC Manager > > > Click the left button "Show List of B-controls" > > > If your control isn't there then Menu "B-Control/New BCF2000" > > > This row should be highlighted so click menu 'Midi options" and select the Midi In and Out for your BCF and the program should find it. > > > > > > Click the P button and the preset list comes up > > > On this new window press Menu "Midi / Receive" to download the preset list. > > > Select a preset 0 and press the circle within a circle button "Encoders'. > > > This will show you the details of the encoders > > > > > > The encoders have a physical resolution of 96. > > > This means that there are 96 different spots when you turn the > > > encoder 360 degrees. > > > > > > The software parameter 'Resolutions' has a default 96 which means that each spot puts out a the next incremented value 1,2,3... > > > > > > So if you had a range of 0 to 127 you would have to turn the encoder more than one whole turn to get to 127. > > > > > > If you made the resolution 96 x 2 =192 then at each spot you would put out the old value + 2 eg ... 10,12,14... > > > > > > If you made the resolution 96 / 2 =48 then at each spot you would put out the value twice before incrementing eg ... 10,10,11,11,12,12,... > > > > > > Hope this helps > > > Royce > > > > > > > > > > > > --- In bc2000@yahoogroups.com, Joey Robinson <jsrobinson@> wrote: > > > > > > > > I'd like to learn how to determine what my BCR resolution is set to, at > > > > that, so I can do a comparison. > > > > > > > > On Wed, Feb 20, 2013 at 11:34 AM, Joey Robinson <jsrobinson@>wrote: > > > > > > > > > Hey Royce and all, > > > > > > > > > > Thanks for the tip. I've found BCManager but I must admit I'm really in > > > > > the dark on how to use this. > > > > > > > > > > Is there a preset guide for idiots around? I've read the BCEdit as well as > > > > > the BCManager manual and I'm no less confused yet. > > > > > > > > > > Could anyone outline how to do a very standard edit of one single knob so > > > > > I can get started? I've gotten as far as having BCManager detect my > > > > > hardware, but as far as actually editing one of the presets or creating my > > > > > own, I'm totally not sure what to do. Please be as detailed as possible, > > > > > I'm fairly technically savvy but this has me in the dark. > > > > > > > > > > Thanks! > > > > > > > > > > > > > > > On Wed, Feb 20, 2013 at 2:34 AM, Royce <rpcfender@> wrote: > > > > > > > > > >> ** > > > > >> > > > > >> > > > > >> Before you do anything with the physical encoder try changing the > > > > >> resolution by software. > > > > >> The encoders can have 4 different resolutions depending on what speed you > > > > >> are turning them and you can program this value. > > > > >> > > > > >> Check out my BC guide in the files area - SecretBC.pdf > > > > >> > > > > >> http://f1.grp.yahoofs.com/v1/PHskUZIMDc3g0_s6h1lddgdYgz7k32zhQ1JB32BGbgIlKt6SqffbH0_1EDZqWnO4iFMk9Zc02RRxmE0kSO-EAg/Documentation/SecretBC.pdf > > > > >> > > > > >> Get Mark's PC editor from his web site > > > > >> http://home.kpn.nl/f2hmjvandenberg281/ > > > > >> <http://home.kpn.nl/f2hmjvandenberg281/> > > > > >> > > > > >> Program an encoder with different .resolution values to see if that makes > > > > >> a difference. > > > > >> > > > > >> All the best > > > > >> Royce > > > > >> > > > > >> > > > > >> --- 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. > > > > >> > > > > > >> > > > > >> > > > > >> > > > > > > > > > > > > > > > > > > > >
Message
Re: Major issues with new BCF2000 - lots of lag and a broken button
2013-02-21 by bconfused2000
Attachments
- No local attachments were found for this message.