Posted: 18 Jun 2010, 06:15
..for easier manipulations of lot or all params, would allow to ie know nb of params, track changes, store/manipulate sets of values..
Page 1 of 1
Posted: 18 Jun 2010, 08:16
+1
Posted: 18 Jun 2010, 09:39
interesting suggestion.
normally should easy to implement.
I'll take a look
normally should easy to implement.
I'll take a look
Posted: 18 Jun 2010, 10:51
whaoo, could be really great...!
Posted: 18 Jun 2010, 11:17
if you can't wait, create an IML/script for that?
Posted: 18 Jun 2010, 12:43
i t's done already 
IML is perfect for setting, for getting pb is ie 300 wires slow down a lot, but still usuable.. i can wait..
IML is perfect for setting, for getting pb is ie 300 wires slow down a lot, but still usuable.. i can wait..Posted: 23 Jun 2010, 23:22
will be implemented in the 5.18
Posted: 24 Jun 2010, 02:12
Not quite certain what this is all about, but it sounds interesting if it does what I think it does...
Posted: 24 Jun 2010, 09:31
great news !
Posted: 24 Jun 2010, 18:14
yeah excellent!
Posted: 24 Jun 2010, 21:52
@ clearscreen:
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!!
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!!