> i find the knob > layout a bit weird though; i'd expect the top left knob to be #1 and > the bottom right to be #32. The knob numbering is what's used internally by P3. Paul N suggested the events could be hard-coded to use the upper and lower knobs for the track the pattern is on. That makes sense, although it means you only get two knobs, or 4, if I included the upper and lower knobs above the parts. It would mean that the event value could be used for other things though - such as a scale factor or offset, or even another event - so you could configure multiple different events to happen, all grabbing their value from the current knob position. Too many possibilities... > also, the knob values are grabbed when in > playlist edit as well as in play mode, which is annoying if you're > setting transpose & repeats for a playlist step. Indeed. I'll need to add some code so the events are only active in playmode - not hard. > i'd also like to see > a definable range on the knobs, but i guess that's gonna be a hard > one..but it would open up the possiblity of adding a 'grab note-value > from knob N' event, which i can also see as being pretty cool; > transposing a pattern up an octave on the fly... Grabbing the note accumulator value from a knob will allow this - you could already grab aux C from a knob and assign aux C to offsel note abs. I'll add a direct event for this though. > another weirdness going on with these functions is that in playlist > mode the knob values also appear to be scanned & translated to > transpose & repeat values. not quite what's supposed to happen i > assume? It is just a test build Chiel - thrown together quickly just to generate ideas. I'll slickify it in the next builds ;-) Cheers, Colin f
Message
RE: [analogue-sequencer] Re: Test build for grabbing your knobs
2004-09-11 by Colin f
Attachments
- No local attachments were found for this message.