ADVANCED FUNCTIONALITY IN THE FOLLOWING HOSTS

Logic X 10.3.1 or higher
GarageBand 10.2.0 or higher
Ableton Live 9.2.3 or higher
Cubase Pro / Artist 9.0.20 or higher
Nuendo 7.1.35 or higher
 
https://www.youtube.com/w...=122&v=-ECBgxAowig

Hi, Øivind.
Not by default, I think.
But if you ask Aleksey (AZController), he might have/make a preset for it, if asked nicely  
All the best.

Or if he's made one already..
http://www.azslow.com/index.php/board,10.0.html
 

I think this is more a question for NI. Will their Komplete Kontrol MKII support Sonar? The integration is down to them. I would hope NI will add more DAW integration but knowing them, they'll probably launch MK3 before then. They have a bad record with their hardware and I got bit by the Kore fiasco years ago.

In the Hardware section there's a thread on this new version. I am super pleased with the original version. For me, the MKII has drawbacks. If I were to buy one today I'd hunt for another MKI (1) version of this keyboard rather than the new one.

The original Komplete Kontrol keyboard generally speaking works great with Sonar. If you're focusing on those new monitor screens in the MKII I would suspect a good long wait for Native Instruments to get them wired up for Sonar.

Zargg
Hi, Øivind.
Not by default, I think.
But if you ask Aleksey (AZController), he might have/make a preset for it, if asked nicely  
All the best.

 
Note that I can not speak for NI nor for Cakewalk, only for myself. But the situation is the following:
 
* for original version (MK1), native DAW integration has 2 parts:
1) transport control. It is available for all DAWs, including Sonar. In Sonar can be "simple" (Modified Mackie or VS100 plug-ins) or more flexible (Generic Control/ACT Controller without LED light, AZ controller with)
2) changing tracks with switching mode for the corresponding NI plug-in. Only native way it possible, "compatible" plug-ins can not do the trick. Unfortunately, Sonar does not have required functionality on API level. What is required is known from reverse engineered original Ableton script. Theoretically, I can try to check some workarounds, but the keyboard and the software is required. I do not have any. I can try remotely, but I need time, the willing and a volunteer. All 3 aspects are not there at the moment...
 
* MK2, from ad videos, has somehow extended DAW integration. At least volume/pan controls with track name and level indications are added. Does that works (or can at least partially work) throw Mackie (the same ways as with transport) is unclear before the documentation is released. If that works throw proprietary protocol only, Ableton scripts will show the way and something can be done with AZ Controller (in the range of Sonar API, volume/pan/level and track names are supported). If Mackie is supported, Modified Mackie plug-in for Sonar should do the trick.
 
In other words, what can be done with MK2 without NI and CW can be clear only once it is released.
 

So, I just got an s88 MK2 and wanted to make transport, etc working.
Is there anyway I can help?
Maybe gathering info?
Thanks!

Bad and good news:
Good. Since MK2 was released quite some time ago, it is more or less known how it communicates.
Bad. No one has done anything for Sonar/CbB support for it.
 
What can you do depends on your programming skills and/or willing to invest time or money:
1) if your are somehow experienced  in programming, using the information from f.e. https://github.com/git-moss/DrivenByMoss you can check the communication yourself. You will just need to understand what/where to send using any OSC client. Then check it works using AZController OSC or not. If yes, you will get transport working. If not, I will need to adjust the code so it works.
2) if your can not do (1) yourself, but is ready to invest some time. We will need to organize online session, with TeamViewer+Skype installed on your DAW computer (where MK2 is connected and NI driver installed). So I can do (1) remotely
3) if your do not have time, but have money. You can buy another controller for me, so I can do (1) locally.
 
While (3) may sound crazy at first, think about reversed approach: should I, not working for NI nor BandLab, spend not only my time but also my money to make transport buttons working on your controller?
 
Note that it is unlikely you/we can achieve much more then just transport within short time.