midi indicators in blocks page

[jamesholdenmusic]

just like audio blocks have meters, we need midi ones.

• standard, perhaps a vu meter kind of thing,
• or a square that shows max/min pitch and vel?
• which output do we meter? all? the first? first unless defined in json?
• some blocks would it make sense to have custom metering? eg a sequencer playhead pointer? though tbh you still want to see if notes are coming out even in that case.
• if you were able to choose which midi out to view, you could chose between pointer/notes that way..

at the moment we're only equipped to capture one midi meter. this overlaps with the new midi-router - it needs to keep track of stuff for every voice not just one.

• ape the audio section - two levels of capture: a min/max vel, and a whole buffer of what notes are on etc.

[jamesholdenmusic]

allow voices/blocks to request a colour for their midi meters? allow voices to specify a range for the x axis of the midi meter? eg midi lfo - only one possible x value, etc held note count -> z axis

[jamesholdenmusic]

todo:

• use new buffer for midi scopes
• ability to select which output a meter points at
• do some blocks (eg) keyboard, midi control, where they have multi outs but are never polyphonic, have multiple cuboids and meters - eg thin ones for 1d controls like modulation/pitch bend, big square ones for midi notes?

[jamesholdenmusic]

in a block's .json we should be able to define default meter target, this also set in settings page currently set to 0. -1 is all outputs. also, the x and y range for each output if nonstandard. this way we can say eg x-range = 1 for 1d type outputs, or y-range = (sequence length) for a clock pointer?

[jamesholdenmusic]

the basic workings of this are all done, midi meters on blocks work, scopes work for blocks and voices and connections. further enhancements are in a new issue