OSC indices
Posted: Tue Dec 13, 2011 19:07
Started messing around Lemur app yesterday and ran into another problem with BeatLoopr.
Creating 8 pads (or switches) it spits out an array ( BeatLoopr[0..7] )
The BeatLoopr "array" in the interface looks like it should be
[0,off][1,4b][2,2b][3,1b][4,1/2b][5,1/4b][6,1/3b][7,1/6b]
But when tapping each pad in order the result in the Arena interface is
0,1,2,3,6,4,7,5
If the indices are reordered shouldn't it at least be
0,1,2,3,4,6,5,7 ?
I've included the components I created. Don't know if this is something related to the new v3 app for iOS, if this can be replicated on an actual Lemur.
beatLoopr is built with switches and labels as it interacts with Arena
padLoopr is built with pads with indices displayed for reference
Creating 8 pads (or switches) it spits out an array ( BeatLoopr[0..7] )
The BeatLoopr "array" in the interface looks like it should be
[0,off][1,4b][2,2b][3,1b][4,1/2b][5,1/4b][6,1/3b][7,1/6b]
But when tapping each pad in order the result in the Arena interface is
0,1,2,3,6,4,7,5
If the indices are reordered shouldn't it at least be
0,1,2,3,4,6,5,7 ?
I've included the components I created. Don't know if this is something related to the new v3 app for iOS, if this can be replicated on an actual Lemur.
beatLoopr is built with switches and labels as it interacts with Arena
padLoopr is built with pads with indices displayed for reference