I have gone back to preferences and made sure the X-touch is assigned to the right ins outs.  I cannot get it to respond. I have rebooted.  I rebooted then power cycled X Touch.  I Power cycled X touch, then rebooted.  Opened old projects where it was working.  Opened new projects.  NADA.  No faders moving in SOnar.  No transport control....
 
Anyone using X Touch having an issue?  
 
Thanks

space_cowboy
I have gone back to preferences and made sure the X-touch is assigned to the right ins outs.  I cannot get it to respond. I have rebooted.  I rebooted then power cycled X Touch.  I Power cycled X touch, then rebooted.  Opened old projects where it was working.  Opened new projects.  NADA.  No faders moving in SOnar.  No transport control....
 
Anyone using X Touch having an issue?  
 
Thanks

I'm seeing some unusual behavior lately. It was working fine most of the day, but late this afternoon it stopped working. I checked preferences and found that the control surface input had changed from X-Touch to MIDI2 X-Touch. I changed it back and it worked fine. Gremlins...
 
Walt

Walt
I deleted and recreated the control surface setup in Sonar and now it works.  But there were no changes (ins outs, MC...) from the prior setup I had.  
 
Odd

space_cowboy
Walt
I deleted and recreated the control surface setup in Sonar and now it works.  But there were no changes (ins outs, MC...) from the prior setup I had.  
 
Odd

I opened up SPLAT this morning and X-Touch was non-responsive . I opened up preferences and once again the input port was showing that one of my synthesizers was selected. I changed it back to X-Touch and it was good to go. I guess this is going to be part of my workflow until Cakewalk fixes this.
 
Walt
 
 

Puzzle.  My X-Touch survived just fine through not only the March SONAR Platinum update, but also the most recent Windows 10 update.
 
I'm not certain that Cakewalk can fix the problem you are experiencing.  It might be that the device is becoming unrecognized by Windows, so SONAR doesn't see the device and thus substitutes useless I/O devices for the control surface.  Are you certain your Control Panel, Power Settings are set to keep USB devices from disconnecting to save power?  A Windows update could have reset them.

UPDATE: For giggles, once I had X-Touch set up okay, I saved my default lens. Ever since then X-Touch is working just dandy.
 
Walt

Glad to hear this. 
 
Could you please tell me, for next time, what does this mean: "I saved my default lens"?

+1 no problem with my X-Touch with the 2017-03 update or the Windows 10 Creator's Upgrade. 

riojazz
Glad to hear this. 
 
Could you please tell me, for next time, what does this mean: "I saved my default lens"?

You can save several lens with unique names for different scenarios. I have one that is my normal workflow that I call "Walts Default" for lack of a better name.
 
Walt

Thanks.  Now I have to ask, what does 'lens' mean?