Mixer blocks UI

[jamesholdenmusic]

mute+solo:

• eq graphs, mute, solo done, just faders and meters to go for the bus plugin

meters: either:

• need a way to request another 2d meter or
  • every frame, draw meters, using your own read of the buffer that the other meters read

channel names

midi control

• on screen indication + control over what it's mapped to
• actually the existing way i do mixer is kind of nicer, but a bit weird for most people (and still available i guess..)
• so it needs soft pickup
• smart soft pickup:
• • if stored is close to midi value, just move it. if not, consider the direction of motion
• • if moving towards the value, do soft pickup (ie ignore values until it gets close)
• • if moving away from the value work out an increment such that it'll catch up when it reaches the end? that's the least extreme change of gradient

at the moment: too many initialisations appearing in console! doesn't work first time! smart soft pickup is ok but has glitches? mute and solo only half working

MIXER CAN HAVE LATENCY COMPENSATION SLIDERS AND SET THEM AUTOMATICALLY (by tracing back how many steps of each kind it is up to a 'clock source' block (what to do in case of conflicts?)

[jamesholdenmusic]

use the new js controller manager instead, it works good now.

todos: force the param (per block) for mute and solo to 0, so the static mod is an absolute val mute/solo buttons an eq graph above them make that eq graph work in the main view

a json key that means the edit button takes you to the mix bus fullscreen edit not fullscreen of this editor.

implement buttons properly for ui patchers - a custom_button that they request that has button drawn and updated on click by main code?

ctrl-click mute and solo to turn them all off

bus to only show things actually connected to it