… I am using an MC3 and I have the CC#21 – value:0 on Release and CC#21 – value:127 on a Long Hold. The repeat is engaging on the Long Hold, so the 127 doing the toggle state is consistent with that…
Yeah, you have to be careful those Long Press / Long Release commands on the Mornigstars to avoid some puzzling results. My long-term suggestion is to establish some kind of generalized template for the H90 MIDI CCs. There’s a huge number of controls that can be MIDI-mapped, and they can all be saved ‘underneath’ a Program (whether or not they’re in active use inside that Program). Then you can source that H90 map from purpose-built MCx templates for specific applications or H90 algorithms.
Most of the H90 MIDI CC Implementation is fairly consistent [v64-127=ON; v0-63=OFF]. You’ve run into one exception with REPEAT, but [v64-127=ON] also logically applies to parameters like TAP. With momentary functions, [v64-127=ON] on Press, and [v0-63=OFF] on Release.
Other than Repeat and Slow/Fast/Brake what other goodies are out there beyond the basics?
Oh, now you’ve opened up Pandora’s Box. At least a few Performance options in every algorithm. The ‘lowly’ Retrigger can be mapped to the same CC in two mod effects, for synchronizing LFOs. Extra pages for Looper transport controls. The newer Harmonizer algos [Polyphony, PolyFlex, Prism Shift] and PolySynth have FREEZE & pitch shifting toggles to explore. The newest Harmonizer+ have the deepest toolkits of Performance parameters.
My more recent PatchStorage uploads have become overloaded with MIDI mappings, so I can point you to an example. The MIDI Implementation is buried under the comments, as is a direct download to a modified sample of that Program.
