I tried a fresh install of CbB on my Surface Pro (I dont use it for music Production.And the Windows 10 is latest). It has the same problems as my Studio Machine. So it is no use ut reinstall to fix this.

Saw it. Will test it. I bet it is the same problem, as Machine and Kk S61 users the same tech to comunicate tith the NI VST.

I have the same problem with Kontakt 5. My keyboard controller will only work if I use the omni setting on Sonars track and on the Kontakt instrument. Individual Channels will not work. All other VST's work normally.
 
In Studio one 3 Pro, Kontakt 5 works fine and as it should. I presume this is a Cakewalk problem. I am running Sonar Platinum.

samson7842
Yeah, uninstalled and re-installed both, CxB and Maschine. No luck. So, I guess we wait.

But, I'm thinking the problem lies with Maschine. If it were just CxB, then my old Sonar Platinum instal should still work fine Maschine.

Roll back to the Sonar Newburyport release and it will work. The error came in the next update, and are still in CbB.
 
You roll back in Command Center by right click the Sonar Install in CC and choose "Rollback". Then pick Newburyport (21.13.0.32)

godino

Jarsve
The error came in the next update, and are still in CbB.

The Newburyport release was a couple of years ago, and Maschine has been working as a vst within Platinum until quite recently - So not sure where this bug came from

As I have written in another thread, most probably the problem is in MS runtime (VS version) incompatibilities. At some points (do not remember when) Sonar was switching to newer versions (like 2012 to 2014, I repeat that is runtime and NOT Sonar version). Sonar also installs many MS runtimes (for plug-ins and other components which are not re-compiled).
 
Probably NI has also switched from one runtime to another at some point. And correct combination produce not working environment. Only NI can find what exactly is wrong there...

So, I followed the directions sent to me. Still not fixed. Damn.

Yeah, I've been using Studio One 4 for that very reason. So I can use Maschine inside my DAW as I've grown accustomed to working.

But, honestly, this makes no sense. A few weeks ago (about 3) everything worked fine. I had zero problems and Cakewalk was running smoother than ever. This has to be something on NI's side of things.

Studio One has some cool features. I bought a license back when it didn't look like there'd be a future for Sonar and I needed an easy to learn, full featured, DAW just in case things went south. I never registered the license until last week. So, I ended up getting the big upgrade to Studio One 4 for free (hell, got the original license on a too good to pass up cross-grade offer). But, as much as I'm loving S1, I'm ready to come home to Cakewalk (CxB).

I'll finish production in Studio One, then mix in Cakewalk(CxB). That's going to be the way I'll have to work until this mess gets cleared up. Unless, I work on a song that I'm not using Maschine in. Then I'll do the whole thing in Cake.

They have me running the NI Support Tool, now. Ugh ...

What is the status of this case now. There is some people on this forum struggling with this. It affects KK S keyboards and other NI hardware with VST plugin information on the hardware.

Nothing new from Bandlab
I initially got a quick response, saying that as X1 X2 and X3 worked with maschine - that if I configure CbB similarly 
it should work - (doh! hadn't thought of that)
when I explained that the problem was a bit more complicated - it went very quiet
and despite contacting them again I have had no response!

maybe they haven't aquired the hardware to test with yet?

azslow3
And may be they just see the same as other users: this VST(s) silently does not work with own hardware

You may be correct, and if that's the case it wouldn't hurt Bandlab to reply to their users stating this as a fact 

Got an email from NI, today. The tech was able to reproduce the problem. But, can't fix it. So, he's elevated it up to development. NI will contact me when they have a fix.

At least they've acknowledged the problem and are able to reproduce it. That's a good thing. Now we wait.

Just wish we'd hear something from Bandlab. That's a little disheartening. Hope this isn't the kind of support we can expect going forward.

samson7842
Got an email from NI, today. The tech was able to reproduce the problem. But, can't fix it. So, he's elevated it up to development. NI will contact me when they have a fix.

At least they've acknowledged the problem and are able to reproduce it. That's a good thing. Now we wait.

Just wish we'd hear something from Bandlab. That's a little disheartening. Hope this isn't the kind of support we can expect going forward.

Great news!

Yeah, it's great news if they're making it a priority. Not so great if we have to wait until the next Maschine update for a fix.

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.