as part of the MIDI mapping editor, you can specify whether the parameter's current value should push back to the mapped device. this is useful for devices like the MIDI Fighter Twister which have CC-addressable LED's on each encoder. when a PMAP is loaded, any echo-enabled parameter will redraw to the mapped device.
support binary-type parameters in UX/UI
previously, the binary parameter type wouldn't register in the UI and keypresses wouldn't register state changes. this has been addressed (w/ the same qt lil' squares as norns)!
(hihiiii! a lot of small tweaks among the large tweaks, will try to cover everything but please lmk if anything remains opaque!!)
this PR adds:
allow_pmap
flagexamples/hello_pmaps.lua
to demonstrate!MIDI map UI
while in mapping mode, press ENTER on any mapped parameter to open the mapping for editing:
here, you can manually modify:
key nav:
allow_pmap
flagby default, every action-based parameter (except text) is MIDI mappable. this can be changed via the
allow_pmap
flag, eg:or
this flag prohibits mapping in both the map mode:
and the mapping editor, if TAB'd over:
MIDI echo
as part of the MIDI mapping editor, you can specify whether the parameter's current value should push back to the mapped device. this is useful for devices like the MIDI Fighter Twister which have CC-addressable LED's on each encoder. when a PMAP is loaded, any echo-enabled parameter will redraw to the mapped device.
support binary-type parameters in UX/UI
previously, the binary parameter type wouldn't register in the UI and keypresses wouldn't register state changes. this has been addressed (w/ the same qt lil' squares as norns)!
hello_pmaps.lua
it's in there!