samson7842
As much as I hate to admit it. The number of Cakewalk users, who also use an NI controller, may not be enough to justify a "must fix quickly" call to action from them.

You're right
even if its a quick fix, would they be able to release a temporary patch for the Users affected, or do we wait for the next release 
pity there's not enough of us to exert more pressure

Glad I checked in here, because I thought I was the only one.
Mk3 controller, CbB (latest), and no other changes.
I'm having this exact same issue, white pads, trigger MIDI, works in standalone and other instantiations.
 
I've removed drivers, re-installed, etc., but nothings worked.
Haven't found a fix, yet.
MIGHT be a Microsoft patch that's at fault, but i'll continue to check here for fixes.

I'm having the same issues, with Mk II Maschine Mikro and Mk1 Kontrol S61
Simon

Yeah. It help to get the troups together in formation.

Everyone else with this problem should contact Native Instruments and Bandlab as soon as possible. They will fix it quicker if they know it's not just an isolated problem.

Yeah, I've raised it with NI, no response yet, beyond the acknowledgement email, and just raised it with BL.
 
Cheers

Has everyone complained to Bandlab, also?

Im Also having the same issue.  I have the S61mk1 and mk2.  Both keybaords are not working with the Komplete VST inside of Sonar (Platinum or Cbb) but are working correctly with Ableton and Komplete standalone.  The issues i have is it works fine as a midi controler but when opening Komplete VST the keybaords display goes blank (does not display "browse" and the browse button doesnt work.  the Light guide on keybed stays blue.  when i manually load an instrument via the mouse, the keyboards light bed doesnt change and key swaps arent visually shown along with the keyboard screen still blank and not mapped as it usually is with parmeters from the instrument.    i have rest the pc, reinstalled all programs from fresh. This doesnt work.  I have contacted NI with a full explanation of the issue and scenarios, to which they replied "i'd like some more info on the issue, so your saying the lights arnt working"? frustrating to have to basocally send the original email yet again with the explanation of what the issue is.  Anyways, no reply back yet.  Cbb support replied back to me and suggested it may be due to a windows update.  All i know is its not working. 

azslow3

godino
So currently it is in the developers backlog.  Unfortunately that means we must wait.  It´s not high on the priority list unfortunately as it´s not even defined if the problem is the controller or Cakewalk.  I could not even guess how long it might take.

Its pretty defined... since the communication between the controller and VST is done COMPLETELY APART FROM THE DAW (unlike f.e. MIDI learn, played keys in other VSTs with other controllers), the problem is inside NI world for sure (on the controller, on the VST side or on both).
Yes, it seems like Cakewalk influence NI internal communication some way it stop working. Can be whatever, from MS Runtimes till the method (time/count) of VST instantiation. But NI part should be fault tolerant to that and only they can debug what is going on.
 
If 30-100 people buy NI keyboards and send them back as BROKEN ("display goes black when I try to control VST"), I guess that can raise the priority. That is not going to work for Bandlab, since it is free 
 
Do not forget to make bigger "noise" on other forums: "NI hardware??? My device is a door stopper now... support say they have no idea why and no willing to fix...", "AKAI rules, NI sucks!", "Light guide? My exemplar produce no lights at all!", etc.

But what if Cakewalk has a sandbox way of handling VSTs? They deny al access outside of Cakewalk? I have a feeling that is the problem! 

scook

Jarsve
But what if Cakewalk has a sandbox way of handling VSTs?

They do not in any sense that I know. Otherwise, badly behaved plug-ins would not bring down the DAW as they do. There would be no need for special plug-in handling during safe mode. Noel has mentioned on more than one occasions they do not because of the overhead involved.

ok

Just now from Bandlab:
 
Hi James,

Thanks for reaching out. We're sorry for the frustration. Our engineers are aware of this issue and are working on a fix at the moment.
 
And then some email template stuff, sounds positive though

But if this came with the Windows 10 April update?
I mean. It might not be that Cakewalk has made a sandbox feature. But that they use something that is now hindered by the new Windows 10 April update. I don’t think it had this problem before that.
And trying to protect one part in this over the others, is not constructive, while most of us just want to think out loud so we might find some new info that can bring a solution.
I don’t care who is to blame or win and argument without any real progress. Only that we find a solution for this, and maybe make BandLab and Native Instruments make some bonds.

Did anyone of you have this problem before Windows 10 April update?
I have heard some complaints of this update, that it is breaking things like this.

Here is a video, one of many, explaining issues and concern of the Microsoft community.

Here is from NI...


Marcel S. @ NI (Native Instruments)

Jun 25, 13:08 CEST

Could you please send me the forum-link in question? In the meantime I shall notify our development about your assumption.
Best regards,
Marcel S. @ NI