Maschine VST scale broken with Komplete Kontrol MK2 Keyboards

So I've been messing with this for years and thought I had it figured out. Most DAWs want allow us to record the output of the scale and arp as straight notes from the feature and instead record whatever keys are actually hit on the keyboard. Fair enough I can just route through another track. Well I did this in Bitwig 3.1.3 with maschine 2.10.0 and while I can track out the midi from the pads just fine there seems to be a bug with the scale mode from my s61MK2. I route the midi from the input track to the track that gas the instrument I want to play to (and it works and records just fine, until I turn on the scale mode. For some reason Maschine then takes it upon itself to transpose all other tracks, including the drum kits. As soon as I turn the scale mode off everything returns to normal (and whatever I just played works just fine and the output is recorded as the scale output) Not sure why it's doing this. Files are included and bitwig is currently routed to maschine group C, which has an analog dreams bass on it. If you load it up and press play groups A and B should play the kick and snare respectively just fine. if you switch to group c and go over to the komplete kontrol keyboard and press scale for something like D dorian on easy mode.... it messes up the two drum tracks while it is on. I can;t fathom why it is doing this since everything is hard routed in the midi unless the VST has some kind of internal midi leak.

 

Same results here, for once I have no idea what's going on... I never use my KKS with Maschine when in Plugin Mode.
Selecting a Scale on a KK keyboard for one sound messed up the other sound in other Groups even though they are on separate channels, like somehow the Scale option on the keyboard is global and channels agnostic. Your routing has a few mistakes but that's not the issue.

In some aspects, Maschine ignores MIDI channels, I think this might be one of those cases... I'll tag Mr36 since he is the most knowledgable person I know with Maschine, maybe he knows something I dont.

 

Thanks for looking. Yeah this is the buttend of like 2 days fiddling with it. Wish ni would just make a midi/audio bridge plugin instead so machine can stay standalone.

 

In what way did it get messed up?

Possibly, though the only case I know for this is for incoming MIDI CCs.

As I don't have Bitwig or a relevant keyboard, this is tricky for me to investigate. How is the MIDI from the keyboard routed to MASCHINE?

 

She has 2 Drum Groups with 'Sounds to MIDI Notes' and then a bunch of Groups with only one Sound meant for instruments, no MIDI in Maschine, it's all on the DAW, all are using different channels.
Everything works fine if the keyboard is not involved but once you activate a Scale on the Keyboard for the separate Instrument Groups Maschine starts intercepting all the MIDI coming from the DAW and transposing it to match the Scale. Scales do work fine if used in a 4x4 controller tho, so I think it's some sort of bug or just incompatibility with the way the software handles the keyboards specifically.

I only have a Bitwig demo, I'll try to recreate this project my DAW of choice later and see if the same happens.

 

Well... I tried on Ableton, same result. I remember seeing people mentioning "SmartPlay" issues with KK + Maschine when in plugin mode, I think this is is exactly it.

If the MIDI is in the Maschine-Plugin (as Patterns) everything works fine but if the MIDI is in the Host DAW and you're sending it to the Maschine plugin then activating any Smart-Play feature on a KK keyboard (other than Scale Guide) will alter the notes the DAW is sending, it will affect all Groups/Sounds across all channels, not just the Instrument we intend to use/record.

Jamie77 You will need to rethink your workflow, either you record everything to Maschine and later on drag and drop the patterns to MIDI tracks when you might no longer need Smart Play or just host the instruments with Komplete Kontrol plugin on DAW Instrument/MIDI tracks... This last suggestion seems more appropriate for your template, it´s what I do aswell, I stumbled on issues like this when using Maschine + KK combo as plugins.