Nano Pad Ableton problem
Posted: Tue Feb 07, 2012 12:57 pm
Hey guys, this is not my first post here but it is my first thread. Be4 i start i would like to say i have learned so much from dsf, just going through threads and stuff kuddos to all contributers and mods. Now to my problem. After searching the whole interwebz and not finding a solution i turn to u guys for help.
Yesterday i bought the nano pad 2 and am having big problems mapping it inside Ableton. The pads work fine but the xy thingy doesnt. Ableton does see it but it acts like an on/off buttn, meaning the moment i touch the pad anywhere the value jumps to 100% and when i release it it drops to 0. There is no in between and no finger action. The xy thingy work, cause my synth sees the x axis as modwheel and if i let it to default it runs fine (only in x axes) but as soon as i try to map anything in the synth to xy it starts to act like on/off buttn. I m guessing tehere is something wrong with the script but i have tryed pretty much all options with no effect.
At first the pad worked fine in my synth, i could assign anythingto it, but ableton wouldnt see any of xy, then i "dumped" the microKONTROL script wich is one of nanoPad scripts i think and Ableton was then able to see the xz but only as on/off buttn. Hope i make any sense and someone has some answer for me... thx guys.
Yesterday i bought the nano pad 2 and am having big problems mapping it inside Ableton. The pads work fine but the xy thingy doesnt. Ableton does see it but it acts like an on/off buttn, meaning the moment i touch the pad anywhere the value jumps to 100% and when i release it it drops to 0. There is no in between and no finger action. The xy thingy work, cause my synth sees the x axis as modwheel and if i let it to default it runs fine (only in x axes) but as soon as i try to map anything in the synth to xy it starts to act like on/off buttn. I m guessing tehere is something wrong with the script but i have tryed pretty much all options with no effect.
At first the pad worked fine in my synth, i could assign anythingto it, but ableton wouldnt see any of xy, then i "dumped" the microKONTROL script wich is one of nanoPad scripts i think and Ableton was then able to see the xz but only as on/off buttn. Hope i make any sense and someone has some answer for me... thx guys.