posted 04 November 2012 01:01            

I am happily a new owner of an Ipad2 and the Lemur app!

I have discovered an unusual behaviour in with the multiball mapping. In particular with the a template that was part of the tutorials in the lemur manual. The template is a multiball object that has its number of balls controlled by two pads, incrementing and decrementing the number of balls (page 77).

What happens that seems abnormal is if you run the template (project in lemur lingo) with 1 multiball and map that ball's x & y values via the osc pull down menu in the vcs all works fine (In my case /Multiball/x and ../y). When you increase the number of balls the original mapping is lost and it becomes necessary to remap as a result of the OSC multiball object having a new identity, being /Multiball/x//1.

I'm not sure if this is a limitation of the osc protocol in that all singular objects don't require the code "//1 or //0" to be concatenated to designate the first object in an array or if its an implementation oversight on the part of Liine or SSC.

It's not a huge issue but a tedius thing to keep track of with complex mappings particullarly when only one object is required for certain controller mappings and you eventually want to increase the number of objects. What I mean is if i prepare any sounds mapping with the intent to use multiple balls then the first ball will always be an object without any mapping just a place holder to keep all other balls' mappings in place.

Also its such a handy piece of code that i could imagine myself utilizing frequently but having one object always taking up space without any function is counter to the point of the code.

Any suggestions how to circumvent this issue?

Hopefully that's clear.

rafe

kyma latest macpro 10.6.8, kyma connect latest, lemur app latests ios6.01