Ripwolf
Make sure you are not "pushing" the fader from the top or bottom of the fader but from inside the indent. I find that the touch sensitivity is jittery when "pushing". Same with the Faderport. Hope this helps.

I tried all possible ways....th jitter does not go...does not follow any pattern either !

While waiting, and in case you know what MIDI-OX is (or have other MIDI sniffer), you can check that you have not problems with touch detection.
 
Connect to X-Touch output (I mean to see what it is sending). For fader 1:
*Movement is PitchBend 1
*Touch is Note 104
Start Sonar. Touch the fader - you should see Note 104 On. Remove finger  - Note 104 Off.
Touch, move the fader, remove the finger. You should get Note 104 On, a set of PitchBend 1 events and then Note 104 Off.
If you do not see Note correctly or you see Note events during the movement - the device is not reacting properly on touch.

As long as I have Automation off, I can freely move the faders on my X-Touch.  Whenever I open a (previously opened) project the faders will go to whatever point they were with that project, but I can still freely move them (with automation off).
 
I used to have a similar issue with a BCF2000 but since replacing it with the X-Touch I haven't noticed that.
 
I also have a copy of Studio One, 3 and it works the same way in that program (which automatically detected and setup the X-Touch - unlike Sonar that required manual setup).

azslow3

RishiS
Btw...while the video I shared above shows automation..I'm moving the fader on XTouch by hand

So, I want formulate critical question to any other X-Touch owner:
 
If your project has 1 track and you start move let say fader 5, do you feel any "feedback" from the fader? And if yes, when exactly you start to feel it: immediately, in short time, after 1-3 seconds?

I don't feel any "feedback" from the fader, I only feel (immediately) a certain steady resistance (against the motor/mechanism) when moving it.
 
 
This resistance feels always the same, it doesn't increase or decrease no matter how slow or fast I move the fader.
 
I use an X-Touch Compact, but I would think the faders are the same.
 

Klaus
I don't feel any "feedback" from the fader, I only feel (immediately) a certain steady resistance (against the motor/mechanism) when moving it.
 
This resistance feels always the same, it doesn't increase or decrease no matter how slow or fast I move the fader.
 
I use an X-Touch Compact, but I would think the faders are the same.

Thank you for checking. Do I understand you correctly that "a certain steady resistance" is the same when you change the volume for existing strip and for not existing strip? So in my example, is there any difference in moving faders 1 and 5?
 
 
 

Yes, the resistance is the same for an existing strip (Track 1/Fader 1) and for a not existing strip (Fader 5).
 

Open this fun little project that exercises the faders with a sine wave, not the straight-line automation curves used.  I didn't write this and I don't know who did; it's been around since the Tascam FW-1884.  Disregard the error messages and select Skip to allow it to create an audio file; it doesn't matter if there is none.  While this gave a nice steady motion on all the faders of the old Tascam, it now plays as a series of short jerky motions on the Behringer.  That may be what you are describing and it may be the best it can do.
 
http://mattfinley.com/promos/fadertest.cwp

azslow3
While waiting, and in case you know what MIDI-OX is (or have other MIDI sniffer), you can check that you have not problems with touch detection.
 
Connect to X-Touch output (I mean to see what it is sending). For fader 1:
*Movement is PitchBend 1
*Touch is Note 104
Start Sonar. Touch the fader - you should see Note 104 On. Remove finger  - Note 104 Off.
Touch, move the fader, remove the finger. You should get Note 104 On, a set of PitchBend 1 events and then Note 104 Off.
If you do not see Note correctly or you see Note events during the movement - the device is not reacting properly on touch.

I am not able to do this, coz when I open MIDI OX with Sonar running, it reports out of memory and hence cannot map the xtouch ports. I get a similar message from Sonar if I open MIDI OX before starting Sonr. Appears like the midi device is locked by the one that opens first. Not sure why tht is reported as out of memory though.

riojazz
Open this fun little project that exercises the faders with a sine wave, not the straight-line automation curves used.  I didn't write this and I don't know who did; it's been around since the Tascam FW-1884.  Disregard the error messages and select Skip to allow it to create an audio file; it doesn't matter if there is none.  While this gave a nice steady motion on all the faders of the old Tascam, it now plays as a series of short jerky motions on the Behringer.  That may be what you are describing and it may be the best it can do.
 
http://mattfinley.com/promos/fadertest.cwp

Tried this...yes this jittery motion is what im referring to.Its annoying when this happens while moving the faders on xtouch by hand.It feels as if the device is forcing me to go slow. Also in automation, this jitter creates a noise.I have a single room for recording and mixing and this noise is going to be a problem while recording. Its much better than the bcf2000 which makes a lot more noise than this though. But I was hoping to get rid of this problem with the Xtouch.
 
On a side note, barring this issue, the Xtouch has been fantastic so far. I am yet to explore the details but switching from bcf2000 this is really intuitive, improves the productivity instantly.

@RishiS: Are faders on existing and not existing tracks have the same "resistance" for you? The same as for Klaus?
I repeat, when you move faders by fingers and when they are steered by Sonar are two unrelated cases.
 

riojazz
http://mattfinley.com/promos/fadertest.cwp

When I observe faders movements on screen, I also see they are not extremely smooth. Can be that X-Touch is "sufficiently fast" to follow this jumping behavior... Technically that will be hard to improve on the DAW level, that is firmware business. It can be that Tascam has done that right for FW-1884. Interesting what the original MCU Pro does in that case.