Behringer CMD Series - Page 209
Page 209 of 218 FirstFirst ... 109159199205206207208209210211212213 ... LastLast
Results 2,081 to 2,090 of 2174
  1. #2081
    Tech Wizard
    Join Date
    Jun 2011
    Posts
    25

    Default

    I have now submitted my 2nd warranty claim today for the same paint issue they denied to warrant in my first claim. I also am making it public knowledge they refuse to honor warranty on Facebook and Twitter with daily posts about this issue. I will not let this go now as I feel decieved and ripped off by this company. It's pretty low of them to shit on their customers especially the ones don't have the means or funds to afford industry standard equipment. If this warranty wasn't offered I would still be pissed about the paint coming off after a few months of light use but wouldn't be going to this extent to get resolution. Sure it was only a $200 item but when you are on a tight budget like I am $200 is a lot of money to spend. It took me months of saving whatever I could for this unit. The 3 year warranty was insurance to me I would have a functional unit until I was able to get back on my feet again. So now I am in fear the unit wont last 3 years and they will never honor the warranty anyways. Now that I shed light here I hope people understand why I am pissed off

  2. #2082
    Tech Mentor
    Join Date
    Jan 2014
    Posts
    475

    Default

    I seriously advise you not to lose too much sleep over this. Sure you can claim warranty again, but posting on twitter and facebook daily won't do squat. I hate to break it to you, but people in general don't give a damn about your issue. Not even a little. They will think you're being pedantic.
    What I would do is seek out consumer organisations and name them in your claim. That has a much bigger effect in general.

  3. #2083
    Tech Convert
    Join Date
    Mar 2014
    Posts
    11

    Default

    can anyone help me to map CMD Studio 4a to iMect's DJ Player?
    I'm having trubles with setting the LEDs to react somehow and change it's colors, maybe owners of other CMD series controllers managed to solve this issue?

  4. #2084
    Tech Convert
    Join Date
    Mar 2014
    Posts
    11

    Default

    So i figured out that I need to set the out values to change the LED colours, can anyone help me with that?image.jpg

  5. #2085
    Tech Wizard
    Join Date
    Jun 2011
    Posts
    25

    Default

    Update on Behringer "Warranty" ... my 2nd claim was put in a week ago without any reply back. They say 24-48 hours you will be contacted. I did get a reply quickly to my first claim. Now thier answer to fix my machine is to ignore me and dishonor ther warranty period completly. It appears they voided my warranty after owning my unit less than 6 months

  6. #2086
    Tech Guru
    Join Date
    Mar 2008
    Location
    Seattle, WA
    Posts
    1,471

    Default

    Quote Originally Posted by bzcxp View Post
    So i figured out that I need to set the out values to change the LED colours, can anyone help me with that?image.jpg
    The LED feedback is the same message as the control output message. The last byte of the message changes the color. So 00 is usually off, 01 is first indicator color, 02 is first indicator blinking, etc.

  7. #2087
    Tech Convert
    Join Date
    Mar 2014
    Posts
    11

    Default

    Hi Craig! Thanks for your responce, can you explain it a bit wider for me cause I'm total noob in mapping...how do i set the last byte value?

  8. #2088
    Tech Guru
    Join Date
    Mar 2008
    Location
    Seattle, WA
    Posts
    1,471

    Default

    In a MIDI message there are generally 3 bytes. The first byte tells what kind and channel the message is. The second gives the specific control number. The third byte is the actual data for that control. So for example, a PLAY button might send the message 90 01 7f when pressed. 90 means it's a note on sent on CH1. 01 is the specific control - in this case the PLAY button. 7f is the message the PLAY button is sending - in this case a full on message.

    The CMD controllers have same input message as their output message. So that means if our PLAY button in the earlier example is sending the message 90 01 7f, then to drive the LED for that button we would send it 90 01 **. ** is variable. 00 is the "off" message (which for CMD usually means no indicator and just the orange backlight). 01 turns on the primary indicator on solid. 02 is the primary indicator color blinking. Some controls have more options available (more colors, etc).

    I cant tell you how to map specifically to DJ Player because all my stuff is in boxes and I'm driving across the country right now. But hopefully this explains it in a way that makes sense. I'll check this thread tomorrow about this time and follow up with anything you add.

  9. #2089
    Tech Convert
    Join Date
    Mar 2014
    Posts
    11

    Default

    Thanks for the explanation, I think I finally got it now. Here's what the CEO of iMect told me at the support forum, so I guess I have wait for the update

    Screen Shot 2014-03-29 at 17.11.29.pngScreen Shot 2014-03-29 at 17.11.48.png

  10. #2090
    Tech Wizard
    Join Date
    May 2012
    Posts
    87

    Default

    Finally got my CMD MM-1 from Amazon. I have to say i'm very very impressed with the hardware, built quality, design etc. Anyway i'm unable to download the official traktor mapping from the behringer website so downloaded Stewe's mapping. For some weird reason its not working. Have imported the tsi to traktor, selected the in & out ports but no response. Anyone ? Using it on Mac with the latest version of traktor.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •