I tried something like that, but ‘inside’ the space of a button. I didn’t think of taking it “full width” like @jasonw22 did. That really uses that space well, and gives suffient weight to that parameter in that it changes the sound of it a lot.
I also welcome any input on how to visualise the data in the MATCH section:
In this section I want to display the incoming audio descriptor stream visually, along with what the parameters are controlling.
There are 5 parameters here, with ‘select’ being the macro version of the individual knobs (as in, turning ‘select’ turns all of the smaller knobs), and what’s being controlled is the weight attached to each parameter for matching. So turning the ‘loud’ knob up, means that that descriptor is given more weight when searching the database.
I’ve tried a few different approaches for how to best visualise this, and thought about a few more, and I don’t necessarily want to add anything flashy that communicates very little (or nothing). Beyond just having the 5 knobs, I want to help communicate what the underlying process of database searching/retrieval is doing.
So I thought about doing a polygon thing where the distance of each point from the centre corresponds to a descriptor, so the ‘shape’ of the polygon would be representative of the incoming descriptors, something like this:
I haven’t tried it context, as I’m not handy with jsui, but this doesn’t really communicate what’s important about this section of the patch. In that it is mainly trying to communicate the state of 4 descriptors, and more importantly, the weight/tolerance of the matching algorithm with respect to those parameters. And ideally, over time.
What could potentially solve the first of those issues is something like this:
Where there’s still the underlying polygon showing the state of the descriptors, but then a separate geometric mesh that gets bigger/smaller around the polygon. That communicates more, but without a time dimension, it would just be a winamp visualiser.
To bring time in, I’d have to devote an axis to it(?), so that brings me back to a scrolling line/multislider type thing:
I could use the center line to show the descriptor value, and then a (lighter) colored bar around that center line, but this get’s a bit noisy…
It’s also not straight forward to implement due pointscroll/linescroll in multislider looking like shit and now allowing for a transparent background.
I can also approach it very differently, and not visually represent the incoming descriptors, and rather show something more lookup/retrieval oriented or something like that.
So yeah, not really sure how to go about displaying this stuff, so any input welcome! (even if it’s just “have only 5 knobs”).