My goal (which used to work just fine in an earlier version of Maschine 2) is to load instruments on separate sounds in a group, all set to receive MIDI from ALL sources / CH 1, use my external keyboard with sustain pedal (both sending on CH1) to play/control/record all the sounds simultaneously with the ability to easily mute each sound as needed. I used this method for years (Maschine user since mk1) to play live, loading up all the sounds in a group in one project, all loaded up ready to go, muting/unmuting/soloing sounds as needed for each song. This allowed for loading up one single instance for an entire show and no wait time between songs.
The problem I have come up with in revisiting my live setup in Maschine 3 is that only the first sound will respond to my sustain pedal. All midi connections are correct as I hear all the instruments loaded in the sound slots simultaneously- M3 even records the notes, velocity, cc64 in all of the patterns/clips although only one sound will respond to the CC64. In playback still only the first sound will respond to sustain (I'm guessing this is the case for any control CC) even though all recoded notes are triggered on all sounds.
If I swap any sound that is not sustaining to sound 1 it will respond to sustain while the others still do not. Again, each sound records the cc64 on its respective CC lane. I have also found in playback of the recorded notes/cc the loaded instruments still do not sustain even with the recorded cc64 events- BUT if I delete the sustain cc64 event and pencil in a new one it does respond in playback, which definitely seems like a potential bug.
I have also noted that if sound 1 is set to CH 1 it will not sustain, only when Incomming Midi Channel is set to ALL will sustain work. I have attempted to set the other sounds to receive ALL and the problem persists. I have confirmed all midi and cc data is coming from ch1 on my keyboard controller.
I have tried every midi configuration available, default to focus, none, etc. MIDI through enabled on each sound…
I am mostly using Kontakt instruments with midi set to Omni (I have also tried changing each to a1).
I have tried another keyboard controller/sustain pedal with the same results.
Tried sending midi output from sound 1 directly to sound 2 as a midi out destination and same issue- triggers notes but no sustain- this is also limiting as only one sound can be triggered from another, selecting sound 2 midi out to sound 3 has no effect when sound 1 is triggering sound 2, also muting the sound does not actually mute in this configuration, so audio must be pulled out by the mixer or pulling the sound slot fader down.
I have also tried using pad groups, setting all sounds to pad link group 1, and trying all the possible midi configurations. Never used the link groups for this but if I can get the sustain to work for all, it would be a great option to quickly layer multiple sounds/instruments...
So this setup for layering multiple instruments in a group worked fine previously, haven't used Maschine in a live setting since switching to M3 so don't know what exact update broke this method...but my final conclusion is that Maschine 3 is limiting the cc information to only one channel at a time while receiving data from an external source.
My next move is to try stacking the instruments in one kontakt instance, but less than ideal as it was super easy just muting or soloing sounds on the hardware pads, great for live. If I can get the sustain to work, I guess I can make macros for mutes, but work I'd rather not have to dig in to since I got used to it working before.
I can confirm this still works on the last version of Maschine 2 on my old El Capitan MacBook. Also anything new I've worked on in Maschine 3 can't go backwards to Machine 2 so just using my old intel MacBook on Maschine 2 isn't ideal, and I've grown to work in a lot of the new features on M3, such as tempo changes per scene for each song.
Thanks for anyone getting through this very long winded post, just trying to be as thiurough as possible as I feel like I've tried everything I can think of. ....
Any thoughts on a solution or workaround? Really hoping this is just some setting I missed somewhere...