Dyonight
I need to setup a Mackie and an extender in order to have all 16 to work with the current mcu implementation. I guess I will need two instance of your plugin to have all channels recognized?

Yes, at least at the moment.  That is why I have asked about some other ("native") mode, in which the whole device is represented as one communication destination.
 

Depending on which template I use (Logic, cubase, protools, live, Studio One... well every existing daw but NOT Sonar...) I have access to different software commands, which trigger different functions.

In AZC you see near complete set of all possible commands which can be triggered. Each DAW has it's own set. Note that the set in SONAR is not Control Surface dependent. I mean SSL can not do more then other Surfaces, while the set can be smaller than in other DAWs (SONAR API for surfaces is almost unchanged since last 10 years, so most new features are not controllable).
 

And what is the "scientific" name of a "native mode"? I will ask SSL since they are very helpful with these kind of questions.

I have "scanned" the documentation, to understand what this device is. It does not look like they have some other mode or have plans to implement it. But that is not a limitation since they have no functions which can not be exposed throw Mackie protocols.
 

Do you know which approach would be best?

I still have not decided what I do with MCU preset within AZC... The last idea is just to implement everything the original plug-in has, may be untested.
 
But the first movement I recommend you is to understand what exactly you miss when using normal plug-in. For example SSL has less buttons then MCU, but they can be arbitrary assigned to any MCU buttons. It can be that the initial assignment is not optimal: check the help file for Mackie Control (XT) Plug-in.
 
You can spot some problems with "labels". The documentation mention the original MC layout, which is different from MCU layout (most probably imitated by SSL). Also the plug-in use special "SONAR" layout. The images in documentation are too small to be readable, but I have already constructed high resolution schema for all 3 (MC, MCU pro, SONAR). I can send the files to you (not sure I am allowed to make them public).
 
Plug-in mapping is configurable in text files (and it is not ACT). So in case you just miss some V-Pot mapping in "Plug-in" mode, you can fix that on per VST basis.
 
There is MC plug-in modification (not from me). While not targeting SSL, from what I could see in screen shots, it can help fixing quite some compatibility problems in case you observe them.
 
Finally, once you really know what you what and you are sure that is not achievable with CW usual methods, it can be time to dive into AZC configuration (may be my preset is ready by then).

For now I don't have  lot of time to program all this, but I want to get back some of the functionnalities I had with the VS700.
 
I would like to configure the button over the jogwheel as a main modifier to allow zooming with the Jog and accessing secondary functions on labeled keys, as well as complimentary ones like undo/redo, activate/set loop/punch.
 
Also, is it possible to dedicate (permanently tie) prochannel function to some knobs? Like the eq which is always avalaible and the selected compressor for exemple?
 
I am very interested in your high resolution schema, that could help at least match the names in the Nucleus editor with what sonar see.... For exemple:
Fader Group 5 -> Enter
Fader Group 6 -> Cancel
Add -> Activate Loop
Next -> Return to Zero
Etc
 
Not very intuitive...
 
Thanks!

Dyonight
For now I don't have  lot of time to program all this, but I want to get back some of the functionnalities I had with the VS700.
 
I would like to configure the button over the jogwheel as a main modifier to allow zooming with the Jog and accessing secondary functions on labeled keys, as well as complimentary ones like undo/redo, activate/set loop/punch.

I think you should  be able to reconfigure nucleus so it sends the codes you want and MCU plug-in expect
 

Also, is it possible to dedicate (permanently tie) prochannel function to some knobs? Like the eq which is always avalaible and the selected compressor for exemple?

Not with MCU plug-in. The code for EQ/Compressor is outdated there (till you have EQ as the first PC module in the chain).
 

I am very interested in your high resolution schema, that could help at least match the names in the Nucleus editor with what sonar see....

I will send you the image in PM in a minute. It show SONAR labels for MCU controls and MIDI (Note) IDs SONAR is expecting from that controls. For example, "Undo" is Note 82. Note, it is not the same labelling as on original devices ( MC has "Undo" label on 75, MCU Pro on 81 ). Also note that I do not have any of these devices... there can be some errors.

Azslow3,
This really looks amazing. How well does your plugin work with the Mackie C4? I would love to be able to fully utilize that CS's potential in Sonar X3(e) and/or Platinum. I don't mind hard work, as long as it has a good chance to pay off.
 
Thanks.
 

I'm interested - just noticing this thread for the first time. I have an NI Kore (first gen) here which I've used to some extent with ACT before, it's not perfect but it can be made to do useful things with a little effort. No sliders but hi-res touch-sensitive endless rotaries and a bunch of buttons. And a jog wheel, which I could never get to work perfectly with ACT. Maybe this will raise the bar! I'll have a go at it in the next few days...

Earwax
This really looks amazing. How well does your plugin work with the Mackie C4? I would love to be able to fully utilize that CS's potential in Sonar X3(e) and/or Platinum. I don't mind hard work, as long as it has a good chance to pay off.

I do not have any real Mackie device. While MCU itself is close to (documented!) Mackie LC and has at least some emulation with TouchDAW I can use, I do not know any emulator for C4 (may be BCR, but I do not have it either).
C4 and MCU are normally working together. That imply I have to finish MCU preset first.
At the same time, it should be possible to configure C4 as a separate controller with 32 encoders plus buttons (I mean now, with my current version). Something like ACT MIDI, with LED rings and display support. You can start with that, it should not take more than several hours for you. Just follow ACT MIDI Explained tutorial (after Mackie initialization procedure, send "'Hello", wait for "Ehlo" and may be send "Connect" to let C4 trust you). In case you need some tips/hints or complete initialization example, please contact me on my forum (I will send you the corresponding part of my not yet finished MCU Explained tutorial).
 

subtlearts
Maybe this will raise the bar! I'll have a go at it in the next few days...

I believe AZ Controller can be useful with any controller. Unfortunately after I have seen several such statements, there was no real feedback...
 

Thank you! I have been following the development for some months and aside from being quite generous in providing your solution for free, your site provides the most lucid and in-depth information I have seen on the subject.  I am an obsessive collector of defunct controllers and you have made it much more likely I will get to use them in my dream studio.  Now if we can crack the elusive HUI code...
 
PS I do feel bad that the response you have received is somewhat underwhelming and I am no better than anyone in not providing the requests for feedback or features.  Errr...aah...if you put up a Paypal button I would gladly donate $$ :p

DoctorCalabria
Thank you! I have been following the development for some months and aside from being quite generous in providing your solution for free, your site provides the most lucid and in-depth information I have seen on the subject.  I am an obsessive collector of defunct controllers and you have made it much more likely I will get to use them in my dream studio.  Now if we can crack the elusive HUI code...
 
PS I do feel bad that the response you have received is somewhat underwhelming and I am no better than anyone in not providing the requests for feedback or features.  Errr...aah...if you put up a Paypal button I would gladly donate $$ :p

Ditto! azslow3, you should definitely get paid for a finished product. I anxiously await your Mackie preset. And, thanks for answering my question. And, finally, I do have both the MCU and the C4.
Ciao

DoctorCalabria
Thank you! I have been following the development for some months and aside from being quite generous in providing your solution for free
...
if you put up a Paypal button I would gladly donate $$ :p

The situation is the following. While the project is just a hobby, the codebase is big. The real price of that plug-in (development time divided by my usual salary, plus innovations value, financial support, taxes) is outside of any imaginable limit. I guess the reason why we do not see many SONAR aware controllers is the price/interest ratio.
 
So I decide to provide it for free, pay the web site costs myself and do not put donation button. In principal I am ready to accept targeted donations, for some particular device. But only after I get request about that device and understand the development is hard/not possible without it.
 
HUI is not "magical". It is just several commands, quite close to the LC/MCU set. From what I know, TouchDAW support the set (I have never tried it), so I have some kind of test environment.
 
As you have noticed already, the feedback I get is close to zero. In such conditions, I can not justify the time I need for some new features I personally will never use.

Will give this test with my M-Audio Key-station Pro 88 and my Peavey 1600x controllers later today.
 
Cheers Alexey