+- XOR Userforum (https://forum.xor.eu)
+-- Forum: Products (https://forum.xor.eu/forumdisplay.php?fid=3)
+--- Forum: NerdSEQ (https://forum.xor.eu/forumdisplay.php?fid=6)
+---- Forum: Feature requests (https://forum.xor.eu/forumdisplay.php?fid=12)
+---- Thread: PC for Patch Selection and Current Values for MIDI CC (/showthread.php?tid=2032)
PC for Patch Selection and Current Values for MIDI CC - RMBLRX - 11-30-2025
Hey, I'm loving how robust the MIDI features have become. As I'm experimenting, though, I've realized a few features that would make it that much better for my workflow. Currently I use MIDI CC to essentially create instruments on a particular device for any given song. Patch has been great for accomplishing this, but because I like to use MIDI input to expedite the composition process (recording another sequencer's output into the NerdSEQ), I would have to set the CCs manually, either through running a pattern with a patch in it while running the external sequencer or by setting the CC values externally and trying to later replicate those into a patch.
My request, then, is a little layered:
- I would like to be able to intercept Program Change input and interpret as a patch select (probably through mapping, which I do not believe to currently include Patch as a destination).
- I would like to be able to set CC values through the Current Values screen in order to set something like an initializing patch for a given track.
- Given the first request, I would also like to be able to create a patch from a given set of current values (possibly have that optionally as default behavior when creating a new patch from inside a pattern, wherein the new patch simply clones the current values insofar as possible).
Really, just having the ability to map Program Change to patch selection--whether live or in recording, but preferably both--would mean the world and take me as far as anything else. But I suppose my two requests having to do with Current Values would require some more fundamental changes and would conceivably be more complicated to implement, if at all reasonable.