Cool petec - fingers crossed it was:)

Turn off the automation read for the offending track as a test?

My issue happens with no populated tracks in the project. Just press play and it happens. Post #10 outlines this.

Guitarmech111
My issue happens with no populated tracks in the project. Just press play and it happens. Post #10 outlines this.

In the empty project did you try disabling zero all controllers on stop and  the controller searchback function? If memory serves they are under the preferences/project menu in advanced view.

Guitarmech111
My issue happens with no populated tracks in the project. Just press play and it happens. Post #10 outlines this.

You should localize problematic component. So:
1) remove Mackie Control Surface from Sonar configuration, remove X32 MIDI from Sonar Configuration. Do you still see the effect? If not, that has nothing to do with Sonar (do you have something connected to X32 MIDI input? do you use some MIDI translator?)
2) add X32 MIDI To Sonar Configuration. Do not add Control Surface yet. Restart Sonar (!), create new test project. Do you see the effect? If yes, this MIDI is implicitly used as output for something. We should find where and why.
3) if the effect is there only when you have Mackie Control Surface configured, what exactly is "the movement"? The source is open, I can have a look what can trigger it.

Mackie control is the interface to control the DAW for the X32. The midi is setup correctly via a USB interface from the X32. The midi is already defined to SONAR.
 
As far as restarting new project, step #10 was a brand new project with everything correctly setup. 
 
What is the reasoning for removing the Mackie control instance from SONAR and if no problems, then no SONAR issue? Don't quite understand that logic. Can you please elaborate?

Guitarmech111
What is the reasoning for removing the Mackie control instance from SONAR and if no problems, then no SONAR issue? Don't quite understand that logic. Can you please elaborate?

I just try to help you find problematic component. It can be in Sonar (most probable in your configuration settings), in Control Surface plug-in (less probable, but who knows) or outside Sonar (probable if you have some other MIDI equipment and/or software).
 
All tests I have asked your to make take less time then typing that reply. But if you think it make no sense, I stop my attempt here and will no longer bother you.

I asked you to elaborate so I can understand. I am open to learn something new. Please do not take offense. 
 
There are no additional midi devices in play here, just the X32. No other outboard equipment. The X32 is the sound and midi interface. The environment is pretty isolated to SONAR and the X32. 
 
edit - I think I know where some of the confusion is coming. The X32 uses the Mackie protocol for the setup in SONAR. The X32 emulates the Mackie device. 

Guitarmech111
I asked you to elaborate so I can understand. I am open to learn something new. Please do not take offense. 

I am not offensive, I simply can not explain the reason for the tests in one post. It will be long even in my native language and hard to understand in my English
 

There are no additional midi devices in play here, just the X32. No other outboard equipment. The X32 is the sound and midi interface. The environment is pretty isolated to SONAR and the X32. 

That excludes 1/3 from possible origins I have asked you to do the test (1)
 

edit - I think I know where some of the confusion is coming. The X32 uses the Mackie protocol for the setup in SONAR. The X32 emulates the Mackie device.

No confusion here, at least on my side. I have developed universal CS Plug-in and LC preset which close to completely imitate MCU plug-in from CakeWalk (but with working EQ and ACT mode). In case after all 3 tests we conclude the problem is somehow MCU plug-in related (so, no movements without MCU plug-in configured) next step can be an attempt to reproduce the problem with my plug-in (I can modify the preset so you can see why it moves the fader, that in turn can identify the problem as really Sonar internal). When my plug-in produce no movements while the original does, I can try to understand from where it comes (I know the source code, I have used its logic to create my preset).
 
It could be simpler in case some other user already new the reason or CW has helped you. Note that CW normally starts troubleshooting sending like 10 links to MS RunTime installers, without any explanation why you should reinstall all of them. It took me like an hour to do this, while I was sure that is not going to help. I still have done that because I was asked to do so. What I have asked you will take less then 5 minutes and we are still at test (1)...

I use Azslow3's plugin - dude knows his stuff on remote issues. He's the best help you could get. If it was my issue I would certainly do the tests before he moves on. Just sayin:)