Launchpad mapping strange bug
Launchpad mapping strange bug Posted on: 04.10.2010 by Ignacio Rutner I have been mapping my launchpad to Traktor and have been really happy with what I have produced. All the midi out is working nicely.I just have one issue I cant solve.... I have buttons mapped to Loop Move on Deck A and no matter what I do those buttons to BeatJump instead of LoopMove. The same setup works on Deck B just fine. I have checked over and over that there are no conflicting mappings or midi messages. Just wondering if anybody has any suggestions on debugging this kind of thing??? | |
| Ignacio Rutner 04.10.2010 | I have been mapping my launchpad to Traktor and have been really happy with what I have produced. All the midi out is working nicely. I just have one issue I cant solve.... I have buttons mapped to Loop Move on Deck A and no matter what I do those buttons to BeatJump instead of LoopMove. The same setup works on Deck B just fine. I have checked over and over that there are no conflicting mappings or midi messages. Just wondering if anybody has any suggestions on debugging this kind of thing??? |
| Ignacio Rutner 04.10.2010 | Finally found it!! Move section was on Beatjump for some reason even though it showed as loop changing it away and back to Loop makes my LoopMove buttons work!! |
<< Back to Post and find Controller MappingsReply