Open up the Midihub editor for public contributions

Midihub Feature Requests
5

Oh yeah, that was us last year returning to a 2020 discussion about Pitch bend to note

What I meant would be covered by @davidpower’s idea of a Script pipe, but I think that approach would be a bit of a “sledgehammer-nut” for what I was hinting at:

TLDR

“arithmetic pipes”

is the term I use for a very small collection of pipes that would do rudimentary arithmetic with defined inputs:

  • Midihub is, IMO, very neatly designed to do a bunch of “musical” things very well.
    As a result if offers functionality like Rescale off the bat…

  • but, when you start to want to do something like general† addition, then you need to consider work-arounds like “convert → note, transpose by mapped amount, convert → CC”
    ( † specific addition shifts might just use Rescale)

  • These “easy” workarounds become quite standard, but getting Midihub to do, say, modulos is really quite tricky.
    (as is doing a ratio-sum, ie µA+(“1”-µ)B, of two inputs)

So each time one of these operations is needed, being able to reach into the Midihub toolbox for that simple pipe would save between 3 and 30+ pipes (and a lot of head-scratching!)


What unites my (tentative) request with the OP’s is that balance between extra functionality and accessibility:

at what point does adding (more “abstract”) functionality…
…that might be a game changer for some users…

…just end up making the Editor less accessible for many others!?

As such, I would almost want such improvements separated in the Pipes panel so that new users know to leave them alone until they’re more familiar!

“Script” Pipe considerations

I think @jboyd’s idea adds to previous discussions in that it hints at two notions that are crucial for the majority of users who would like the extra functionality “off the peg”:

  1. a bank of well written pipe “presets” :asterisk: which would do new weird and wonderful things easily

  2. confidence (or at least knowledge) about latency effects

I would love to see this but I think it’s no mean feat:

I sense that it would take a lot of clever thinking from @Blokas to make the interface really accessible to a variety of coding inputs and a community of willing helpers to make each scripted preset optimised and well documented

:asterisk: I’m picturing a single Script pipe which, like Micro Scale, has a drop-down for a small collection of user-loaded scripts. The number available might depend on the aggregate byte-space used