This is a NuVJ, my second choice MIDI controller from Numark

As a class-compliant USB MIDI device it installed fine. I loaded my VJ software of choice, Resolume, mapped the jog wheels to scratch video, and scratched.

The video went bonkers.

A couple of moments looking at the MIDI messages in MIDI-OX told me why – the Total Control jogwheels use a bizarre schema for their endless encoder messages. All the MIDI controllers I’ve encountered in the past have used the same format for endless encoders, rotating clockwise will send out a stream of, (to paraphrase the machines) “+1″ messages. Counterclockwise gives “-1″. Spin your jogwheel or knob faster, and it sends out more messages per second. The Total Control, however, changes its message depending on how fast the wheel is spinning, so an increasingly quick movement would look like “+1 +1 +2 +3 +5 +7 +7 +8″ etc. Even more bizarrely, the values seem the reverse of what they should be, so a clockwise movement gives negative values.

So I took the controller back to the store, along with my Macbook to road test any alternatives. The guys were happy to swap my Total Control for a NuVJ, whose jogwheel behaved much better when tested with Resolume. It was still backwards, but it wasn’t causing the playhead to jitter all over the place.

I should have done a little more testing though, because it turns out that all of the knobs on this device work the same way. The only piece of software which recognizes them correctly is the version of Arkaos bundled with the NuVJ. Ableton Live does an ok job with the general knobs, and the jog wheels work ok moving clockwise, but counterclockwise has the live controls snapping backwards at 5 times the speed of forward movements.

So, sadly, I’m back at the same position I was in 17 months ago, sitting with a well made and reasonably priced controller, which will require hours of hacking and re-mapping to complete simple tasks.

Is anyone else in CDMLand in a similar situation? Or better still, have been in a similar situation and discovered a quick and elegant solution?

There is time, however. You can save yourselves from utter scumbagdom (at least in my eyes). This thing is obviously the same hardware as the BCD2000, so you can do it. Update the BCD2000 drivers and firmware and we’ll never speak of this again.

The alternative is to get crushed by Numark’s NuVJ and Total Control/ION’s iCue, Vestax’ VCI-100, MAudio’s Xponent… Seriously people, when the BCD2000 was announced it was basically the only kid on the block at the price point, 18 months later there are similarly functioned devices from all of the major players, and all you’ve managed is a coat of paint and platform support which was put together by a hacker sniffing USB packets?

Dude, ouch.

Evinyatar has commented on our early BCD2000 Not Mac Compatible post to announce that he – sick of waiting for Behringer to actually do something useful with their gear – has written and released OSX Universal drivers (MIDI only so far):

My first subject is Behringer’s BCD2000. When it was released about two years ago it was rumored that MacOS X drivers would be released by the end of 2005. Rather than waiting for those to appear (which they probably won’t) I decided to have a go myself. The result is quite good, if I say so myself. It works, which is more than I expected.

Currently only MIDI in and output works. Audio does not. That means you can control Traktor the way you would on a Windows computer, but you won’t hear anything through the BCD2000’s audio ports or record anything trough them. You can still, of course, use other audio outputs, built-in or external, that do work with MacOS X.

Right now the MIDI input and output are should be identical to the Windows driver in B-DJ mode. Which means a reasonable amount of pain is implied when trying to configure Traktor for the BCD2000. Basically, the same hack that works for Windows (using MIDI-Rules and a loopback device, in our case Apple’s built-in IAC) is also required for Mac. I hope to incorporate similar functionality inside the driver in the future, eliminating the need for the hack. For now, this will have to do. A more detailed guide to setting this up will be posted sometime later this week.

3 days later there’s a release, and he’s gone further: Working on a system which will allow OSX users to actually customize mappings on their BCD:

I have just finished building and testing the Universal Binary driver for the BCD2000. So now you should be able to use the BCD2000 on your PowerBook, iBook, iMac and PowerMac, as well as your MacBook, MacBook Pro, or Mac Pro. As always, you can find the download link over at the “Links” box on the right.

On other news, I’ve been working on a GUI for MIDI Rules, which should make setting up Traktor a bit easier. After that’s done being polished, I’ll release it and write up the HOW-TO for getting Traktor up and running with the BCD2000 on Mac OS X.

Right now, though, I’m being rather intrigued by how audio works on the BCD2000. My pleas for documentation have fallen on deaf ears at Behringer (you’d think they’d be a bit more supportive when you’re doing them a favor like this one), so I’m staring at hex dumps from USB Snoop on my Windows machine trying to figure this stuff out.

This is absolutely stellar news for users, and shockingly poor form from Behringer. That they had both an obvious demand and a 2 year head start and were still beaten to OSX compatibility by a hacker with hex dumps is a pretty apt reflection on their pathetic attitude to customer support.

I’ll be picking up a Macbook (my first) in the coming month or so, but until then I’d love to hear from anyone who’s been able to give this a spin on their Mac. I’ve emailed Evinyatar to get some further information on his process, and I’m thinking of propositioning him to work on an updated Windows driver. Any other frustrated BCD2000 owners out there willing to chip in to fund work on this?

In the meantime, lucky Mac-based BCD2000 owners can download Version 0.0.1 Universal Binary and give them a go.

Update 2007-01-13: We have learned that a BCD2000 user, Evinyatar has released an OSX compatible driver (Universal Binary, MIDI functions only), and has plans for more customizations. -JL

After waiting over a year, I finally have it. The Behringer BCD2000 was announced in January 2005, initially shipped small numbers in August, and then incessantly delayed until finally being delivered worldwide in late April 2006. Considering that the device has been in the wild for over a year there is a surprising lack of information online. Not that it was a nerve-wracking purchase decision at AU$265 street (US$200), but I couldn’t do the usual review harvest before picking it up. I was looking for a midi controller to compliment my BCR2000 and bridge the VJ/DJ divide. I think I may have found it.

What you get

The official Behringer “B-Control Deejay” page is heavy on marketing, so here’s the executive summary:

USB Audio Interface:

• 4 Channel USB audio interface (2 master out, 2 1/4″ headphone out)
• 2 Phono preamps (one switchable to line)
• Mic preamp

USB midi interface:

• Crossfader
• 2 upfaders
• 2 pitch controls
• 2 jog wheels
• 13 assignable rotary controllers (18 total)
• 37 assignable buttons (37 total)

Initial Impressions

If you’ve used a Behringer MIDI controller such as a BCR before, then this will be very familiar. The plastic BCD knobs and sliders aren’t as silky smooth as higher-end offerings, but they are rather chunky, which is great for a live performance environment. As the BCD rotaries aren’t endless, Behringer haven’t included the excellent LED rings seen on the light-tastic BCR. Instead, they’ve opted for a more traditional bump and a normalling detent on those controllers that need to be zeroed, such as EQ and gain. The cross- and upfaders are smooth and move quite freely, not as quick as a real DJ mixer, but definitely faster than the BCD’s main rival in the price range, the M-audio X-session. I was pleasantly surprised by the pitch controls which have a firm, precise action and “quartz lock” style detent. The buttons are ok; they’re not velocity-sensitive, but do have a good solid click when pressed.

Jog wheels: Now I haven’t spent any significant time using CD turntables, nor the similarly priced Hercules DJ Control, so I can’t currently compare these to any of the major competition. I’ve DJ’d enough with vinyl though to be able to confidently say “these ain’t no 1200s”. They’re comfortable enough, but definitely part of a cheap piece of gear. Ed: Note that the high-end scratch controllers, as found on products like Pioneer’s CD turntables, feel quite different because they add weight and a drive mechanism to provide the resistance of a real vinyl turntable. It’s simply not possible to get this same response without a huge jump in price. I did get to try the scratch controllers on the Behringer gear at NAMM, and they did feel reasonably good to me for a basic, rotating plastic controller; in my opinion, better than the Hercules device in both build quality and response. -PK

Overall, though, build quality is good. The steel chassis of the B-control series lends a hefty, solid feel, so you’re not afraid to bang away at them if the mood takes you. My BCR2000 is over a year old and has been lugged around the world in suitcases and backpacks to little ill-effect. I expect the BCD to be similarly robust.

One small but frustrating issue for the whole range is the included, pathetically tiny rubber feet. These adhere to the device’s own small plastic “legs” and it should take around 1-3 gigs before they’re knocked off through enthusiastic use and the controller starts to slide away from you. This isn’t a worry if it will be spending its life on a desk, but if you’re going to venture out of your studio with it eventually you’ll need to replace those feet with something more robust. The legs stand out by 5mm, but don’t have enough space to stick on a standard adhesive rubber dot, so I’m still looking for a suitable replacement.

Plugging It In

Interface is via USB1.1, and, happily, the included BCD2000 Control Panel drivers are relatively innocuous. The drivers install easily and without excess baggage. They’re ASIO- and WDM/MME-compliant, and allow you to change ASIO latency and select in/out channels. Ed: Behringer has previously supported Core Audio on the Mac, but doesn’t appear to have any Mac drivers in this release. -PK The device is also switchable between B-DJ mode (for use with the included B-DJ software, put together by xylio) and Advanced mode, for use as a MIDI controller/soundcard with other programs or devices.

I’ve been using the BCD as my primary sound source since I picked it up, and am quite happy. As I’m not a musician or producer by trade, I don’t have a professional soundcard to compare it to, but if you’re used to an on-board or low end card such as Creative or Hercules produce you shouldn’t have any complaints. I’m not going to go all stereophile on anyone; but running through rather nice, vintage NAD amps and Wharfedale speakers gave me plenty of clean, distortion free sound. This thing will be fine for DJing with MP3s, and I’ll venture it will serve well with club soundsystems. One possible issue for gamers: The BCD doesn’t support EAS, so games with hardware accelerated sound may not work properly, causing slowdowns and other unhappiness. I’m quite happy to switch back to on-motherboard sound for the occasional Oblivion session, but if you’re looking for a gaming soundcard, this may not be the product for you.

Headphone output is 1/4″ and drives well past my pain threshold. I can’t be sure that it would be enough if you were wedged between ceiling-high stacks of speakers, but it’s plenty to give you tinnitus in the privacy of your own studio.

Noticeably absent from the connection options are MIDIs In, Out, and Thru. I suppose as it’s designed for soundcard use as well the BCD will generally be plugged into a computer, but it would be nice to have the ability to connect other MIDI devices into it, rather than taking up more USB ports and requiring 3rd-party software to rout MIDI messages.

Bundled Software

I’ve spent enough time in Traktor and Live to know what I like, and B-DJ isn’t it. It is definitely a functioning digital DJ program and compliments the BCD perfectly – not so surprising considering that it was designed especially for this purpose. It works, but it doesn’t have the stability or any of the polish seen in the major DJ software offerings. For a budding DJ who wants to train their ear to beatmatch and find out what all those knobs on the mixer do, it’s excellent. For someone who’s more experienced and has a specific use in mind, well, you’ve got some customization ahead of you. Ed: My guess is anyone serious will skip over this application for tools like Live and Traktor, of course. If anyone comes up with a custom template — especially for Live — do let us know! -PK

One of the great features of the BCR and BCF is the included BCEdit software, which allows you to customize and save presets for every knob, button or fader on the device. You can choose the MIDI data type, send channel, note or controller number, value display, min and max controller value, LED ring display or button LED toggle, and so on. It’s a little clunky, but magnitudes better than the on-board configuration of many MIDI controllers. So you’ll understand my profound disappointment when I discovered that the BCD has none of this customization available. All button and controller assignments are fixed in the device.

So, instead of a happy lovefest of simple customisation, the first thing I encountered online as a new BCD owner was this 14 page thread on the Native Instruments forum about getting the BCD2000 jog wheels to work correctly with Traktor. Some clever types figured out a combination of Bome’s Midi Translator and Midi-yoke to get some useful control out of the jog wheels, and DJ Fresha’s ninja setup with Midi Translator 1.5 beta to use them for scratching in Traktor. Fortunately for me the jog wheels work fine out of the box for scratching in Resolume, but I don’t think VJs are the BCD’s primary target market, so if sound is your thing you might need to do some translating.

Throwing Bome’s Midi Translator or Hubi’s Transformator into the mix opens up a whole world of customisation, which I shall leave for another article. We’ve got a review copy of Midi Translator Pro, which has some very interesting features, so expect a look into that soon. The short version is this: As shipped the jog wheels are infinite rotaries sending CC19 and CC20, velocity 64 (move anticlockwise) velocity 65 (clockwise). If your program of choice can do useful things with this information: Congratulations. If not, get mapping or wait for Part 2 of this article.

So, should you get a BCD2000?

If you’re looking for a cheap entry into digital DJing: What are you waiting for? Go, now.
If you’d like a cheap midi controller/sound card to integrate with your existing software setup: This may be what you’re looking for, but some more research for your particular needs may be in order. I’ll have more to say on advanced uses and midi translation soon.

Updated: We’ve learned the BCD2000 is not Mac-compatible, though it’s possible it might be at a future date; you may also have difficulty acquiring one as it hasn’t yet started shipping in volume. Full details