Arrays are actually a quite simple concept, and as long as we're just dealing with one-dimensional arrays (which are what we normally would within Usine), you can just look on them as "tables" of data where each element or index contains one piece of data. The index numbers in Usine (and indeed in most programming languages) start counting the index at 0, not 1. And a lot (most?) of the Usine modules with array in- or outputs have separate in-/outputs for the first 16 indexes - if you want to access single elements above 16 you would need to the Get/Set Array Element modules. With a couple of exceptions, when you connect something to an array input it "inherits" both the array size and the data within. There's plenty to write about arrays - anything in particular you had in mind?
Statistics: Posted by bsork — 01 Nov 2008, 00:27
]]>
To my point of view, concerning patching and jamming in a band, faster is better. If i need to hit my drumpad one more time in a song, while composing it, it could have been usefull tohad an automatically created output when you change your array lenght.
P.S: i'm begginig to understand arrays, so sorry if i have some stupid questions
Statistics: Posted by ethnix73 — 31 Oct 2008, 11:35
]]>
If the idea is to simplify the patching process when creating similar subpatches with different number of steps, you can send the whole trigger array out as one output no matter what length.
Statistics: Posted by bsork — 31 Oct 2008, 06:25
]]>
I'm working on some kind of step sequenced trigger patch...For exemple, you have a step sequencer of 8 steps. Each one sends a trigger message to a separate output. I would like to be able to have automaticaly inserted or deleted outputs, corresponding to the number of steps.
Statistics: Posted by ethnix73 — 30 Oct 2008, 23:19
]]>