Filtering out unwanted MIDI CC's
Sep 16 2021 | 5:34 pm
I'm building a Max for Live device and to control a hardware synth that uses NRPN's for parameter controls and I'm hitting a roadblock with the way Ableton natively (miss)interprets NRPN's.
Right now I'm using 2 separate midiin objects in my device, one bringing midi in from recorded clip data, and one purely to communicate with the synth. The midi in from the synth goes to nrpnin objects and are tied to knob and buttons, then get sent through nrpnout objects to the max for live device's midiout object. Communication with the synth itself is flawless until I record something. When parameters are changed on the synth, automation is written correctly through the max for live device, but midi CC's are ALSO recorded onto the clip itself under Live's midi control section, causing the midi control data live recorded to interfere with the max device's NRPN controls. How do I filter out unwanted midi cc's so the garbage that Live records in doesn't conflict with the NRPN data? Currently, I'm trying to take the max for live device's built-in midiin object and i have that sending to a midiparse object, when sends note/velocity, aftertouch, pitchbend, and program change data to separate note out, bendout, touchout, and pgmout objects, and i have the midiparse's CC outlet sending to a ctlin object set to CC64 for sustain sending to a sustain object, which goes to the noteout object.
What is the proper way to get this max device to ignore all MIDI CC's except for this CC64 for sustain? I'm new to max, so don't roast me too bad. ; )