I have to ask. I've read through this posts and see you are all getting into the X-Touch and integrating it well with Sonar Platinum. My question is to the Tascam FW-1884 users. What does the X-Touch do that the 1884 couldn't do? I understand that the 1884 is old tech but I also hear it works fine still with Windows 10 64bit. In other words it ain't broke so why fix it, and spending another $6 bills for the privilege? What am I missing? The X-Touch uses USB and the 1884 uses Firewire. Is that it? Is there some problem using the 1884 with your hardware or software? I still use Windows 7 as I've been nervous to upgrade my DAW to Windows 10 for fear of drivers issues. Thanks for the postings on this, it's really helpful.

In my case, Windows 8 64-bit broke my FW-1884.  Tascam gave up on the driver.  Microsoft abandoned Firewire.  It's more complicated than that, with workarounds that might work, but that's my reason. 
 

Results have been "hit and miss" getting the 1884 to work in Win 8 and 10.
I failed miserably when I tried to get it going in Win 8, just as Matt did.
Staying with Win 7 on my current rig, I'll cross the Win 10 bridge only when I'm forced to...
 
T

Bought an X-Touch about a week ago. Pretty snazzy. I found out about azslow's SDK fork and downloaded. Many thanks for the 'filter' fix. It works great, although you have to get used to the way the driver 'modes' behave.  I'd prefer that Sonar's mackie control driver work more inline with what the standard button labels imply, rather than the old overlay - but I realize that's a lost cause. For now, I'm using it as is and it's acceptable.
 
I suppose the question is if Cakewalk is going to retain the control surface COM interface, or are they going to go with something different now that they are going to be supporting Mac?
 
 
 
 

I also got the Behringer x-touch, works fine so far..
I upgraded the firmware with bome sendsx as someone told it worked for them here (thanks btw), while upgrading as told on behringer firmware upgrade tutorial on youtube, he said it should go to 100% although his went to 98, and my x touch went to 56, and stood still there for a while...I waited like 5 min, still 56, so I rebooted and the firmware seemed to be upgraded from 1.13 to 1.15, seems to work as normal but I still wonder if it got upgraded for real?!..should I be worried about this?

And also, does anybody know if there is a way to change Mute, Solo, Select colors on the x-touch? I thought standard color coding for mute and solo was:
Mute = yellow
Solo = green
But on x touch Mute is red, Solo is yellow, channel select is green :/ uhh...

This is maybe something I will get over time but for now it is kind of challanging since these colors is not like in sonar mute and solo colors...have to look twice when pushing buttons on x touch if I pushed the "right" buttons since Im use to sonars mute/solo colors...

orhanproject
I also got the Behringer x-touch, works fine so far..
I upgraded the firmware with bome sendsx as someone told it worked for them here (thanks btw), while upgrading as told on behringer firmware upgrade tutorial on youtube, he said it should go to 100% although his went to 98, and my x touch went to 56, and stood still there for a while...I waited like 5 min, still 56, so I rebooted and the firmware seemed to be upgraded from 1.13 to 1.15, seems to work as normal but I still wonder if it got upgraded for real?!..should I be worried about this?

And also, does anybody know if there is a way to change Mute, Solo, Select colors on the x-touch? I thought standard color coding for mute and solo was:
Mute = yellow
Solo = green
But on x touch Mute is red, Solo is yellow, channel select is green :/ uhh...

This is maybe something I will get over time but for now it is kind of challanging since these colors is not like in sonar mute and solo colors...have to look twice when pushing buttons on x touch if I pushed the "right" buttons since Im use to sonars mute/solo colors...

I get the impression that the X-touch is capable of way more than what it supports via the MCU protocol. Supposedly, the scribble strip LCD's are capable of changing color and so on, but there's no standard way to address that functionality. Maybe in the future Behringer, with enough user interest, will publish some extensions to the MCU protocol to allow it. Who knows?

FYI - I don't think you need a separate sysex player, SONAR has sysex management and it should work. I use it to store sysex data from external hardware as part of a project. Go to Views > Sysx or type Alt+Shift+7.

Anderton
FYI - I don't think you need a separate sysex player, SONAR has sysex management and it should work. I use it to store sysex data from external hardware as part of a project. Go to Views > Sysx or type Alt+Shift+7.

 
Didn't think about that, but yeah, one could easily load up a sysx file and have Sonar send it to the controller.
 
Overall, I'm happy with the Sysx view in Sonar.
I have an old Yamaha MU100 that I use and I often tweak it a bit. It's really nice in that you can modify a parameter from the front panel, and then have it display the exact byte sequence needed. This way I don't need to dump the entire setup, just the parameters I'm tweaking vs the XG reset state.

I am considering getting an X-Touch. Can anyone confirm or deny if the X-touch can control EQ and compression? Especially from SONAR's Pro Channel? What about send levels and panning?
 
Any help/info would be very much appreciated.
Thank you,
-Charles

Sylvan
I am considering getting an X-Touch.

X-Touch (full version) is exact replication of Mackie Control. Everything written about Mackie Control also apply to X-Touch, including...

Can anyone confirm or deny if the X-touch can control EQ and compression? Especially from SONAR's Pro Channel?

Till EQ is the first in ProChannel and compressor is the second, standard plug-in will not control it. You will need my mod (a derivation from the original, open source on GitHub, NOT my own AZ Controller). With that mod, you can control standard (but not other!) ProChannel EQ and Track/Bus compressors.

What about send levels and panning?

That is supported in the original version. For Sends there are 2 modes: you can control the same parameter for 8 strips (f.e. Send 1 Level from each strip) or several parameters from focused strip.
 
What is NOT possible to control (at the moment): Soft. Synth, ProChannel modules (other then EQ and Comp).