# Ainser 64 config. 10..11bit with Traktor PRO pitch fader

**URL:** <https://forum.midibox.org/t/ainser-64-config-10-11bit-with-traktor-pro-pitch-fader/20614>\
**Category:** MIDIbox NG\
**Tags:** pitch-fader, resolution, 10bit, 11bit, traktor-pro, ainser-64, traktor\
**Created:** [September 23, 2019, 8:03am UTC](https://forum.midibox.org/t/ainser-64-config-10-11bit-with-traktor-pro-pitch-fader/20614 "2019-09-23T08:03:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![VNat](https://forum.midibox.org/user_avatar/forum.midibox.org/vnat/32/218_2.png) [@VNat](https://forum.midibox.org/u/VNat)\
**Post date:** [September 23, 2019, 8:03am UTC](https://forum.midibox.org/t/ainser-64-config-10-11bit-with-traktor-pro-pitch-fader/20614/1 "2019-09-23T08:03:13Z")

</div>

Hello Guys!&nbsp;

I read multiple topics here but I did not find answer exactly to that issue what I have and want to solve.

I made a Midibox NG with STM32F4, Ainser64, DINs, etc.

I found how to configure buttons and encoder&nbsp;behaviour, all is working great, but I am stucked with potentiometers, especially how to setup higher resolution and&nbsp;get the correct midi output what Traktor Pro can ‘’eat’’.

In NGC file I made resolution=9..10..11 bit, range=0:511,&nbsp;0:1023, 0:2047, depending on the bit depth setup, but all I got as midi signal is that the former 0…127 range (this was the range in 7 bit from CCW to full CW potentiometer turn)&nbsp;is divided multiple times to 0…127, 0…127, etc. ranges. I tried NRPN and Pitchbend type too, but no success.

Am I doing sthg wrong, or MB NG is not supporting this in that way how&nbsp;I am thinking?

&nbsp;I would to control Traktor Pro pitch fader with a higher resolution, and with the mentioned ‘’divided’’ range, the pitch fader is not becoming&nbsp;more fine, and jumping back when CC changes from 127 to the next 0..127 range.&nbsp;&nbsp;

I am not sure that I wrote it correctly what I want, but hopefully understandable. I would have in a +/- xy % pitch range the finest resolution which is possible to achieve with MB NG and works well with Traktor Pro.&nbsp;Traktor is reacting to CC message, and 7bit resolution gives 64-64 steps from center to negative and to positive pitch range. This coarse resolution I would like to change to more fine steps.

&nbsp;It reacts to NRPN and Pitchbend messages too, but I could not achieve the same behaviour with&nbsp;higher&nbsp;resolution, like when CC is sent (xy steps in both directions from the center)&nbsp;Is it possible to do the a.m higher resolution fader steps&nbsp;with MB NG with CC, or NRPN, or Pitchbend event?&nbsp;

Many thanks for all of you for further help.

Akos

---

<div class="post-metadata">

**Author:** ![FantomXR](https://forum.midibox.org/letter_avatar_proxy/v4/letter/f/3d9bf3/32.png) [@FantomXR](https://forum.midibox.org/u/FantomXR)\
**Post date:** [September 23, 2019, 8:27am UTC](https://forum.midibox.org/t/ainser-64-config-10-11bit-with-traktor-pro-pitch-fader/20614/2 "2019-09-23T08:27:00Z")

</div>

This should totally be possible. Would you please post the related parts of your NGC file?

---

<div class="post-metadata">

**Author:** ![VNat](https://forum.midibox.org/user_avatar/forum.midibox.org/vnat/32/218_2.png) [@VNat](https://forum.midibox.org/u/VNat)\
**Post date:** [September 23, 2019, 9:56am UTC](https://forum.midibox.org/t/ainser-64-config-10-11bit-with-traktor-pro-pitch-fader/20614/3 "2019-09-23T09:56:55Z")

</div>

> 1 hour ago, FantomXR said:
> 
> This should totally be possible. Would you please post the related parts of your NGC file?

Tried to make something understandable, see the pictures.

I made also trial with type=NRPN, range=0:511, then from centre pot position the pitch fader works 2x the whole pitch range when CCW turning, and the same when CW turning (fader jumps when range is ended)&nbsp;Resolution is still coarse.

Many thanks for your reply FantomXR.

 ![CC10bit0to1023.jpg.016d53357edc3f38d1cc11650e9c1365.jpg](https://forum.midibox.org/uploads/default/original/2X/b/b2be75ea594479a03f5e00c3bce820c9bcdfe129.jpeg)

 ![Pitchbend9bit0to511.jpg.df6d60ffe2710903de05b9f370b2c998.jpg](https://forum.midibox.org/uploads/default/original/2X/3/3ecab2abed78bae4215042cd9ef2fa77fa1b7612.jpeg)

---

<div class="post-metadata">

**Author:** ![FantomXR](https://forum.midibox.org/letter_avatar_proxy/v4/letter/f/3d9bf3/32.png) [@FantomXR](https://forum.midibox.org/u/FantomXR)\
**Post date:** [September 24, 2019, 6:20am UTC](https://forum.midibox.org/t/ainser-64-config-10-11bit-with-traktor-pro-pitch-fader/20614/4 "2019-09-24T06:20:53Z")

</div>

If you set type=cc then it’s logical that it only allows values between 0-127. If you want to send highres-midi you have to set the type=pitchbend or type=NRPN.&nbsp;

If you substract 7682 from 8192 you will get 510, which is almost what you set with the range. In this case you have to use MAPs instead of standard ranges.&nbsp;Then it will work. Please refer to the NGC-manual. For testing purposed I’d recommend not to use ranges anyway.&nbsp;

---

<div class="post-metadata">

**Author:** ![VNat](https://forum.midibox.org/user_avatar/forum.midibox.org/vnat/32/218_2.png) [@VNat](https://forum.midibox.org/u/VNat)\
**Post date:** [September 24, 2019, 10:48am UTC](https://forum.midibox.org/t/ainser-64-config-10-11bit-with-traktor-pro-pitch-fader/20614/5 "2019-09-24T10:48:46Z")

</div>

Exactly this was what I was looking for 🙂

I needed to play a bit to find the way to get the values centered, but finally works as it planned.

So the actual data from the related&nbsp;lines are in the NGC file&nbsp;now:

type:Pitchbend&nbsp; &nbsp; &nbsp;range=map1

MAP1/HWORDI&nbsp; &nbsp;0:16383&nbsp; &nbsp; &nbsp;4095:0&nbsp; &nbsp; &nbsp;4095: 16383

This setup gives values from 8192 to -8192 with the chosen&nbsp;resolution. I have chosen 11 bit, in Traktor this gives great resolution to the pitch fader, like in case of any best known CDJ 🙂

Now I need to eliminate the jitter somehow.&nbsp;(I tried the setup on breadboard, and&nbsp;just wired up everything in village style…)

As advised on ucapps site, better wiring, shielded cables, and maybe external PSU will solve this.

Many thanks for your help FantomXR!
