Sure, no problem.
Sure, no problem.
Here's the link to the audio recording of the Behringer Webinar talking about the CMD line with:
-Craig Reeves aka Nem0nic (DJ Product Manager)
-Gene Lee (Craig's Assistant DJ Product Manager)
-Andrew Luck (DJ & Recording Product Support Specialist)
Sorry about the audio quality it was a last minute thought when i started to tune in to the webinar. I grabbed my h4n zoom last minute, hit record, and pointed it at my speaker. I lost a little bit of the beginning but they were just talking about general CMD things which we already know. The first 3 minutes and the last few minutes have some background noise like my gf talking to her friend and my dog's collar jingling around the house lol sorry bout that, but trust me it goes away after the first few minutes. I lost a little bit of the middle because my h4 ran out of card space so i grabbed an H1 and started recording just fyi. Again sound quality isn't all that great but you can still hear pretty much everything they say. That being said i cannot wait for this CMD line to drop Thanks to craig and everyone at Behringer for giving guys like me wanting to start out DJ'ing a fighting chance by releasing a cost effective controller. Can't wait to start this epic journey. PLURRRR HAHAAH!
https://www.dropbox.com/s/fj5itml0bk...%20Webinar.mp3
Is there a particular reason why the DC-1 does not change with the feedback/receive the MIDI output from Ableton? For instance, the encoders take triple the time turning that a normal encoder would, and the pads act like toggles when mapping them to any other button other than drum rack, but even then the led does not change from orange to blue as mentioned. Is there a way to edit these controls because the only way to really get the controller to work is with Traktor.
15" Macbook Pro (2.0 GHz Core i7, 16 GB) Mac OS X 10.7 Ableton Suite 9. iPad (Liine Lemur).
Well, the BCR2000 has an editor where you can even increase the speed of the encoders depending on how you are moving it: slow, normal, faster and fastest. I think an editor will come out for the CMD line eventually.
MacBook Pro 13 (Q1 2011) | Adam A5X | Akai APC20 | Alesis QX49 | Behringer BCR2000 | NI Komplete Audio 6
Right now, if you have a pre-production DC-1, then the answer is no. The only way that Ableton Live allows you to handle LED feedback messaging is through the API and not through basic mapping. This isn't a problem with the controller - it's the way Live works. Any other controller not directly supported by Ableton works the same way. When the CMD controllers are on store shelves, we plan on having a couple options for Ableton users that will take care of this issue.
The button toggle issue is also something that happens in Live. The default button messaging out of the CMD controller is momentary, but Live changes it to a latching behavior.
Your encoder performance issue can be caused by a couple different things. It's possible that you have the wrong type of encoder data selected in Live. You want to select the binary offset encoder type. If you do that and it's still too slow, you can use a plugin like Mapulator (http://www.bentosan.net/blog/2012/3/22/mapulator.html) to adjust performance (since Live doesn't offer this functionality on it's own). If you're still not happy, it's possible to change the encoder output on the CMD controllers to absolute, via a SYSEX message.
Before I offer that up, though, i would love to know where you got the CMD controller.
|
Bookmarks