Add a "Preset" pipe? and/or add a "Preset” consumer?

[sdellap]

MH preset changes must arrive through a physical input (MIDI or USB).

So, a programmatically triggered preset change requires to physically patch an Output to an Input, therefor consuming 25% of the ports!

Would it make sense to add a “Preset change” pipe?

It would probably look a lot like a “Transform” pipe (including the filtering of incoming PC, CC or notes; CC/note values…) and generate a preset change event [1…8].

Yes, it might interrupt a processing midway, but it could actually be a feature of the processing, not a bug! depending on the user requirements.

Alternatively (or as a complement :-), could a “Preset” Consumer/Sink/Output be added?

The generated PCs [1…8] would be injected on the Channel and into the Input defined in the settings.

To see the details of the reasoning, please follow:

Programmatically change presets without a physical cable

Hi all! Been using MidiHub to operate a guitar amp/cab selector and the one selected amp. Each one of the 8 presets handles the specifics of one of the 8 amps, providing an “on the fly” uniformity of the diverse amps controls, ironing out the differences from the MIDI controllers point of view. So far, so good. As the amp selector has more than 8 presets. I programmed MH to watch for (and transform) the PC changes addressed to the amp selector, such that PC=11,12,13,14 correspond to MH preset…

Please let me know if my short description lacks details…

[sdellap]

I guess, instead of a “Preset” Output, a “Preset” Consumer or Sink (the counterpart to a Generator?) would be a more appropriate label.