Noel Borthwick [Cakewalk]
HI guys,
 
We realize that users want periodic updates to the Mackie control dll. To facilitate this we are planning on open sourcing SONAR's mackie control surface. There are several developers in the SONAR community and a few have expressed interest in maintaining and updating this. We're still working through some details but I'll post an update when I have some more details.
Well also be releasing the current version of the control surface API that has access to more SONAR specific parameters, Prochannel etc.
 
thanks,
Noel

Holy smokin' coolness!  I am currently using a Mackie Control Protocol (MCP) emulator (BluAudio D8Bridge) along with the Mackie d8b as a control surface, and I'm reasonably happy with the integration.  Important stuff works as it should - Solo, Mute, Pan, Record Enable, faders, audio level meters, time code display and transport/shuttle/scrub functions.  The channel Selects don't work and I've got the same issues with EQ control that the MCU users have.
 
One of the biggest challenges to the MCP emulator builders is no access to the MCP spec.  The Logic Control spec is close but certainly not identical.  So consequently, some things are just unknown and not everything works as it should.  This idea of publishing Sonar's control surface and API is huge!  Thank you!

I would be happy to donate to such a product as well.

oh to have a fully functioning MCU, now that would make a great xmas, or new year, or just my day.
I hope the guys on here that can make it happen, CAN make it happen.

lawp
after a couple of months, any progress on making it open source?

Kind' wondering the same thing.  Has someone picked this up?
 
Glen

Not codeplex? :) Anyways I'm getting fussy... Good news... thanks...

double post

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

Transport VST what is that?

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

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. 
 
 
 

I vote for a complete revamp/update/scrub of the mackiecontrol.dll in X3e, accompanied by Cakewalk's publication and open sourcing of the MCP / control surface implementation.  Not that my vote counts much, but pretty please...
 
All control surface controls (e.g., mute buttons) written to automation.
 
I'm not whining, really.  I'm fairly happy with X3.  But supertight MCP integration would be the bomb! 

Awesome news, Noel! I miss being able to control EQ parameters with my BCF. Karl (Fast Biker Boy) helped me when X1 came out to get back some of the controls back but by X1c or d it stopped working. 

I doubt you will get it before X3E, and that's late March.

This is epic
 
Thank you Mr Brothwick!

CakeAlexS
I doubt you will get it before X3E, and that's late March.

Oops ;-)

Cheers,
Jerry