If you install my controller: http://www.azslow.com/index.php/topic,163.0.html , I can assist you to find the reason of your problem (may be solve it, even in case it is your specific device bug).
 
Note, it is not that I ask you to install "add-ware" for help Unlike with original plug-in, it will be possible to see what exactly is going on in respect to MIDI messages exchange and logic. From your description, I can guess that "Touch" signal is "unstable". Even if you see the light is always "on" while you are touching the fader, it can happened that it periodically sends "off/on", too fast for led flickering but sufficient to instruct Sonar to reset the value.
 
(do not forget to remove FaderPort plug-in from Sonar Control Surfaced when using my plug-in and remove my plug-in before inserting FaderPort back, they do not work in parallel. Also I remember that fader port power cycling is may be required when changing plug-ins).

azslow3
If you install my controller: http://www.azslow.com/index.php/topic,163.0.html , I can assist you to find the reason of your problem (may be solve it, even in case it is your specific device bug).
 
Note, it is not that I ask you to install "add-ware" for help Unlike with original plug-in, it will be possible to see what exactly is going on in respect to MIDI messages exchange and logic. From your description, I can guess that "Touch" signal is "unstable". Even if you see the light is always "on" while you are touching the fader, it can happened that it periodically sends "off/on", too fast for led flickering but sufficient to instruct Sonar to reset the value.
 
(do not forget to remove FaderPort plug-in from Sonar Control Surfaced when using my plug-in and remove my plug-in before inserting FaderPort back, they do not work in parallel. Also I remember that fader port power cycling is may be required when changing plug-ins).

I checked out the page but I am a little confused about the actual installation process....do I still go through the command prompt/setup as recommended by SONAR documentation? It's my understanding that those steps are necessary for the Faderport to even be recognized in SONAR.
 
(I actually uninstalled Faderport recently so I'd be starting from scratch...there are currently no drivers installed.)
 
What you're describing sounds accurate...that the Faderport is sending on/off information even if it's indicating that it's still writing Touch automation.
 
I didn't mention this earlier, but there doesn't appear to be a problem with SONAR itself in regards to writing automation. If I record an automation pass using my mouse, then record another pass, SONAR maintains my automation value until I release the mouse, then it jumps back to the previously existing level, just as it should.
 
I'm thinking about picking up the X Touch (even though it's frustrating that one has to ignore the button labels printed on the unit since they execute other commands within SONAR), but the main purpose would be to write multiple lanes of automation simultaneously, so I'm trying to determine if there's just something wrong with my Faderport, if there are things I'm not doing right in regards to setup, or if this type of behavior is to be expected with control surfaces within SONAR.  I've seen some grumbling about limited support for control surfaces on this forum so wanting to figure out what's realistic before potentially dropping $600 on the unit!
 
Anyway, thanks for the info...we'll see what happens.

azslow3
If you install my controller: http://www.azslow.com/index.php/topic,163.0.html , I can assist you to find the reason of your problem (may be solve it, even in case it is your specific device bug).
 
Note, it is not that I ask you to install "add-ware" for help Unlike with original plug-in, it will be possible to see what exactly is going on in respect to MIDI messages exchange and logic. From your description, I can guess that "Touch" signal is "unstable". Even if you see the light is always "on" while you are touching the fader, it can happened that it periodically sends "off/on", too fast for led flickering but sufficient to instruct Sonar to reset the value.
 
(do not forget to remove FaderPort plug-in from Sonar Control Surfaced when using my plug-in and remove my plug-in before inserting FaderPort back, they do not work in parallel. Also I remember that fader port power cycling is may be required when changing plug-ins).

Wow! Is this still in development? I had no idea it existed.
 
EDIT: This is awesome! Thank you! I've got it installed and working :-)

streckfus

azslow3
If you install my controller: http://www.azslow.com/index.php/topic,163.0.html , I can assist you to find the reason of your problem (may be solve it, even in case it is your specific device bug).

I checked out the page but I am a little confused about the actual installation process....do I still go through the command prompt/setup as recommended by SONAR documentation? It's my understanding that those steps are necessary for the Faderport to even be recognized in SONAR.

1) From Faderport manual http://www-media-presonus...rt_OwnersManual_EN.pdf follow 2.2.1 (Quick Start up)
2) From 2.2.8 (Sonar Setup), follow 1, then 5 and 9 (which is really 6). DO NOT follow 2-4.
3) Then follow AZCtrl general installation instructions. In video form: https://www.youtube.com/watch?v=Baoo0-CysSI , follow till "Startup" preset selection in AZCtrl (you need "Faderport" preset)
4) After "Faderport" is selected, click "Create preset" in the dialog and the installation is complete (Faderport should work with Sonar).
 

PilotGav
Wow! Is this still in development? I had no idea it existed.

As you can see, I am still alive and active

Below are the steps that were not in the Presonus documentation, but were necessary in order for SONAR to recognize the device. Are those steps still required? 
 
https://www.cakewalk.com/...-SONAR-Control-Surface

Another great alternative - and seldom mentioned anymore - is the Roland VS-100 (Discontinued, but shows up on Ebay now and then.  I just snagged one in "like new" condition last week for $100).
 
In addition to the usual DAW controller functionality (100mm motorized fader, transport, etc), the other half of the unit is a full-fledged audio interface.  It can serve as a backup interface -- or your main one if you don't require a lot of I/O -- and since it's from Roland, it supports ACT, for tight integration with Sonar.
 
Finally, and this sets it apart from the others.... Official Windows 10 support!  (Oddly, none of the rest of the VS-family got the same treatment - as you VS700 owners are well-aware!).  This seems to suggest that they view this unit as more in line with their popular Quad/Octa-Capture interfaces which, of course, also have Win 10 support. 
 
So far I'm having a lot of fun with this baby.  The sound and the low-latency of the interface is fantastic -- so much so, that I'm now looking strongly at the Octa-Capture.... 
 
Darn, I knew that $100 was just a bait and switch! 

streckfus
Below are the steps that were not in the Presonus documentation, but were necessary in order for SONAR to recognize the device. Are those steps still required? 
 
https://www.cakewalk.com/...-SONAR-Control-Surface

No. These instructions are for updated version of "native" plug-in. AZ Controller is working instead of it.

streckfus
That would be great, thanks!

So I finally tested this out and I experienced the same problem in "Touch" mode. However I can successfully make new passes and overwrite new automation without things going crazy while in "Latch" mode.
 
I open up the "Inspector" view by pressing "I". Then I select "Tracks". Down a little ways under "Automation" you can switch the mode to "Latch".

Sylvan

streckfus
That would be great, thanks!

So I finally tested this out and I experienced the same problem in "Touch" mode. However I can successfully make new passes and overwrite new automation without things going crazy while in "Latch" mode.

Latch mode exists for using not touch sensitive controls for overwriting automations. In such case "Touch sensitivity" of the fader is more or less ignored (except it does not "fight" with the finger).