Touch Automation - multiple passes

Looked around and saw that a few people were having some issues with the Presonus Faderport, but thus far I've mainly seen issues with drivers/connectivity as opposed to the actual performance of the device once a connection has been established.  I've run into many of the same bugs other users have reported so I'll simply state that I've found a way to make Faderport usable within Sonar without causing any crashes.
 
However, I'm running into problems with automation and I'm not sure if it's a Sonar problem or a Faderport problem, so maybe those who are using controllers for automation can enlighten me a little bit.
 
As a transport, Faderport works fine.  Although it won't allow me to control buses, I'm able to move from track to track, arm/record/etc without any problems.  However, when I attempt to write fader automation, the problems start.  When I record an initial pass of automation, everything seems to work fine.  The automation gets written into Sonar's volume automation lane without a hitch.  However, if I want to go back and make another pass in touch mode, the automation gets really jumpy, bouncing back and forth between the automation I'm writing and the automation that already exists.
 
Has anyone run into similar issues when writing automation in touch mode?  If so, what control surface are you using?  My guess is that because it's relatively inexpensive, the Faderport "thinks" I've let go of the fader if I'm holding it still, and therefore "tells" Sonar that I've let go of the fader, thus causing the jumpy automation envelope whenever I'm overwriting existing automation.  If the Faderport just isn't sensitive enough to accurately tell if I'm using the fader or not, that explains it.

I can confirm that I experience some weirdness with touch automation. I'm not using a Faderport, but a Novation SLMKII w/ Automap. It seems that either the device isn't reporting that I'm touching the fader (so Sonar thinks I want automation to jump back to the existing value), or Sonar is ignoring it. I'm also not sure that it's Sonar's fault, as the SLMKII does some weird things sometimes. 
 
Can anyone with another device confirm?

mesayre

swamptooth
It seems that what you're after is automation latch mode... Have you tried that?

If I'm understanding OP correctly, he means that touch stops writing when he stops moving the fader (even if he's still touching it), causing jumps in the automation between the new values and the old. That's what I'm experiencing, anyway. This doesn't seem like the way touch should work.

Yep, that's exactly what's happening.  Even if I'm moving the fader very slowly, it'll read as though I'm no longer touching the fader and the automation will jump to the previous value instead of writing the new ones.