than mean collecting all in/outs to an array. this will open lot of applications. we ll be able then as examples:
_know nb of params (via get arrayLength) usefull for iml to wireless access a param, being sure it exist.
_analyse changes in the array, so we can know "cutoff param 74" is moving, to ie autowire it to a fader or make an automation,
ask it's name via iml as knowing it's id and name the fader according if wireless.
_randomize all params in one shot via randomize the whole array.
_duplicate some params from a vst to another while keeping ie an independant pitch bend/midi sequence for each voice.
_apply some subbtle changes to all values.
_store them all to some arrays we can later recall ect...
one situation i imagine is a "learn", moving a pot on vst would bring a quad menu to easy apply it a fader, automation, random of lfo, rather than searching the correct pin. this will be possible theorically thanks to that implement. but there are lot's of other applications im sure i didn't thought about yet.
thanks a lot olivier!!Statistics: Posted by 23fx23 — 24 Jun 2010, 21:52
]]>