double post

Great news Noel.   Please keep us posted.  Thanks

Using MCU with Sonar X2 and it is able to connect without any problems.  I connect using MIDI only not USB. I can operate a lot of my Sonar functions using the MCU, however,  not as much as I used to when I had Sonar 8.5.  I do believe there was a change in the Mackie.ini file at some point.
 
Peace

Is is possible (and legal) for someone to send the MackieControl.dll from X3c to me?  I'd like to try it in my Sonar X1d to see if it'll enable proper function of my X32 (running 1.15). Right now, it's a disappointing situation.
 
I'm excited to hear that the DLL will eventually be Open Sourced, but until then, I'd like to do this test. At some point I expect to upgrade to X3.
 
This is unrelated, but can someone confirm that, in X3, transport position is driven out to VST's (to enable manual pitch correction within Izotope Nectar).  The Mackie Control and Transport VST issues are two must-haves that would keep me in the Sonar camp. 

Transport VST what is that?

John
Transport VST what is that?

does the host send the position of the playhead/now time/transport to the VST plugin?

I believe so. At least, even in previous version, when using Melodyne, it would follow the playhead.

Pardon me for making up the term Transport VST. The function that I need is as Sanderxpander described. The playhead position is given to the VST plugin so it can create a replica of the audio that matches the position of the original. Obviously v-Vocal does this, and I just realized that the Melodyne Essential in X3 has that manual editing function. 
 
I think this puts me over the goal line. The Melodyne Essential provides the manual vocal editing function that I need, and the apparently fixed MackieControl.DLL in X3c (hopefully unchanged in X3d) gives me what I need.  
 
As I have played with Studio One (Windows and OSX), Logic and Pro Tools, I am ever more impressed with the usability and layout of Sonar…and that's why I am upgrading from X1 to X3 this week. 
 
That's enough thread-jacking for one day.  

To share the benefit of my rainy day progress on this issue, I am pleased to announce that in Sonar X1, I've gotten past the 'Connecting' hang, with my Behringer X32, and have made some baby steps toward useful function. I am running on the Firewire interface of the X_UF through a PCI Texas Instruments adapter. 
 
In the Behringer X32, the 'Setup>>Remote' screen has...
Protocol = Mackie Ctrl
Interface = Card MIDI
MIDI In/Out = Card MIDI
Remote Button = Enable {toggled orange}
 
In Sonar X1d, the 'Edit>>Preferences>>MIDI>>Control Surfaces>>Connected Control Surfaces/Controllers'...
The 'Mackie Control-1' selected and X_UF MIDI for both 'In Port' and 'Out Port'.  
WAI is checked, and I picked yellow for my color.  
Under  'WAI Display', 'Track View' and 'Console View' are both checked.
 
I opened a 30-track project, and under 'Utilities>>'Mackie Control-1', there is an utility edit dialog box. This utility seems to be a holdover from a Sonar 8.5 installation. It says Chris Boucher [chris at sorted dot org] copyright 2002-2006 along the footer of the dialog box.  In the bottom right-hand corner of the box, I picked 'Fader touch selects channel' and 'Select highlights track'. 
The biggest leap forward was choosing 'Meters // Signal LEDs + Meters. That made the meters work in the X32 bus faders.  
 
Back in the X32, I tapped the 'View' button in the 'Assignable Controls' area.  
Within Set-B, I chose...
Select Control Button 5 /// Remote /// < Bank
Select Control Button 6 /// Remote /// > Bank
Select Control Button 7 /// Remote /// UP
Select Control Button 8 /// Remote /// DOWN
Select Control Button 9 /// Remote /// REW
Select Control Button 10 /// Remote /// STOP
Select Control Button 11 /// Remote /// PLAY
Select Control Button 12 /// Remote /// FF
 
I put some other stuff in Set-A and Set-C as an experiment, (for example, RIGHT and LEFT moves between markers), but you get the idea.  The faders work, but their current position value in dB isn't displayed in the little display window for each bus on the X32 as Studio One does; I only get a sequential number 1-thru-8 in that field. Fader responsiveness also seems a bit sluggish compared to Studio One, but for now, I'm overjoyed to have gotten this far past 'Connecting...'.
 
The Studio One 2.6 support of the Mackie Control emulation in the X32 is my benchmark for function; although I haven't figured out the equivalent of WAI marking in that DAW. Conversely, Logic in OSX does the WAI very well on the X32, but defaults the fader position value to zero after you stop moving the fader. 
 
That's the extent of my baby steps.  I'd still like to see what differences there would be with the MackieControl.dll from X3c, but at least there's marginal function at this point.  
 
I hope these "instructions" are helpful to someone. 
 
 
 

any updates? Any estimation possible?  I have a Nucleus here that seriously need to be healed....