New controller

[KrisH]

Up until recently I've been using an older Yamaha "home" keyboard to control my softsynths, unless I was layering sounds with my D-50 or DX11. Problem was, the action wasn't very nice, no control over parameters, and the keys were not even velocity sensitive. So I took advantage of a sale at an online music retailer and bought a CME VX5. Not that I was crazy about the red color, but it's actually not as offensive as I feared, being finished in brushed aluminum. It seems solid as a rock, about 30 lbs. and made of metal all around. Lots of buttons, knobs and sliders to map to my vst host and softsynth controls, and a dozen trigger pads for other assignable functions, like percussion. I can also control my recording software (Logic 8) with the transport and faders at the same time I play the parts I'm recording, all from one panel. It has motorized faders on playback, which is kinda funky. I don't know if that's a real useful feature though, but it looks cool! And the keys feel great, not sloppy or too stiff or spongy, with 10 different velocity and aftertouch curves.

I've read a lot of reviews from 2007-08 about the series describing bad firmware problems, but nothing more recent. I don't know if this one is a "version 2" that's been out since about 2009, but it seems to be operating fine for me so far. Except for one problem -- it doesn't send aftertouch messages that my hardware/softsynths recognize. The board seems to generate the signal as an assignable parameter, but it either doesn't send the signal or sends something my devices don't recognize. Not that I actually use aftertouch when playing, but I'd like to have the option if it's supposed to be available. Maybe I'll try mapping it directly into my softsynths.

Anyhow, I'm hoping the worst doesn't happen with this controller, given some of the old reviews I've read. Right now I'm happy with it. I'll have to post and update pic of the setup once I decide the VX stays.

[KrisH]

The aftertouch problem is resolved. It involved a firmware update. Despite what the retailer claims on its website, the unit did not ship with firmware version 1.10 -- a diagnostic check showed version 1.05 installed. Anyway, version 2.1 was available on the manufacturer's site, so I downloaded it and installed it. I figured if the upgrade goes bad and bricks the machine, better to do it while the return period is still in place. But it went just fine. And the first time I tested the aftertouch function, it took me by surprise. It was so sensitive that I had to dial the response down! It also seems to latch on to my Logic controls and some of my softsynths more seemlessly, too. The firmware upgrade is a double-plus good thing.

So, I'm thinking this may be a keeper. It's a whole lot of midi controller for $299: http://www.cme-pro.com/en/product-detai ... oduct_id=9 (the v2 version of what I paid for).

[krushing]

CME's support seems to be rather slow, non-existant or just generally flaky, but hey - if it works, all good. I have a CME UF5 from a few years back, and the USB drivers for it never worked - until OSX moved into the Snow Leopard age, and then they suddenly did (the drivers are from 2007 or so). The keyboards themselves are ok for the price (although mine's developed one faulty key apparently from just sitting in one place), but the support is so random that I'm in the "never again" category with this.

[KrisH]

I know what you mean -- I'm still waiting to hear from CME as to whether it would be alright for me to install v2.1 in my older model board. I'm also disappointed with the retailer, too, for misleading buyers with its promotional copy. Oh, the humanity!