Hallo, Mathieu Bouchard hat gesagt: // Mathieu Bouchard wrote:
valve1: type bool, default 1 valve2: type bool, default 1 valve3: type bool, default 1 breath_pressure: type float, default 0, range 0 1 lip tightness: type float, default 0.5, range -1 1 mute position: type float, default 1, range 0 1
Right now the most 'elegant' way of doing that I know of is using [route]. I often find myself making a "wrapper" for a instrument that goes through a familiar pattern. First scale all the values or normalise them as required, bound the ranges with [min] and [max]
Btw: [min]---[max] can also be shortened as [clip].
weed out any coupling or collapse groups of them, and present a nice shiny named list. This list, usually gets appended to the end of a [poly] list for routing individual poly voices etc. That seems te established method for making polysynths. But it seems fiddly and difficult because the only mapping between a parameter and its purpose is in the ordering of the list passed. Is there a better way to do this? Better than using routes and unpacks?
You maybe could use [pointer]s for this as well. I played a bit with that idea and attached is what I came up with so far. I omited the scaling part, which could maybe even go into the data structure itself.
There is a bug with note-offs sending the wrong pointer, but that bug also occurs if you pack parameter into plain lists, IIR.
Frank Barknecht _ ______footils.org_ __goto10.org__