Re: Android and OSClisten
| Date | 2015-05-28 20:46 |
| From | "Art Hunkins" |
| Subject | Re: Android and OSClisten |
| Attachments | None None |
|
Thanks to Justin Smith, Russell Pinkston, Steven Yi and others
who helped me solve the issue of how to get a TouchOSC app to control Android
Csound6 via OSC on the same device. The basic problem was the OS I was working
with: this combination of TouchOSC and Csound6 requires Android 4.4.2 (I
was using 4.2.2; the exact version required has yet to be determined). The other
basic requirement for OSC with Android Csound is to use the version of Csound6
based on Csound6.05, which is the first version that includes the OSC
opcodes.
The specific coding issue I had involves the difference
in how OSClisten handles its input, in contrast both to chnget and to MIDI.
My practical situation was that I was taking a .csd coded for the chngets of
Android Csound6 (the builtin performance GUI), and converting them to
OSClistens, so TouchOSC GUIs (Layouts) could perform the .csd instead.
Indeed this turns out to be quite practical - especially if you prefer a custom
GUI.
As all the controllers for the Android Csound6 GUI operate
from 0 to 1, the widget output will normally be massaged into a range and value
suitable to your .csd. My .csd's typically cope with this simply by redefining
the value of the incoming variable: e.g., kamp=kamp*10000. (Often I do multiple
redefinitions.) This works fine with chnget and MIDI - but not at all with
incoming OSC variables.
The simplest solution I've found is to use a different output
variable instead of redefining the input, e.g., kamp2=kamp*10000. Doing this
insures that kamp2 is properly stored internally, and now can be further
used/redefined just like "normal" (i.e., chnget and MIDI). At any rate, this is
my recommended "workaround," and I thought it worth sharing.
Art Hunkins
|