Re: Android and OSClisten

Date	2015-05-13 03:38
From	"Art Hunkins"
Subject	Re: Android and OSClisten
	Unfortunately, it doesn't. No difference from what reported. One confusing thing about the TouchOSC Editor, is that whatever you do, the editor automatically adds "/" to all widget names - e.g., "fader1" becomes "/fader1". And if you set the Page to anything, such as "1", fader1 becomes "/1/fader1". No way of getting rid of the slash that I see (the same with Auto mode). Of course, I'm using the Windows TouchOSC Editor. Is the action perhaps different for the Mac? (I understand there is no Linux editor.) I note that all the default Layouts (in the Windows editor) use Auto mode for both Pages and widgets. As Page 1 is always named "1" (which causes it to be sent as "/1"), fader1 will be sent as "/1/fader1". So I assume this is what happens even if you are not using a TouchOSC Editor. Or am I wrong? Art Hunkins ----- Original Message ----- From: "Justin Smith" To: "Art Hunkins" ; "csound users' discussions" Sent: Tuesday, May 12, 2015 8:45 PM Subject: Re: [Csnd] Android and OSClisten > if the slider is set to send "fader1", this should be working as written > > On 5/12/15, Art Hunkins wrote: >> In Mike's latest Csound6 for Android (6.05), I've been having a difficult >> time getting OSClisten to receive OSC messages sent from a TouchOSC >> Layout, >> >> all on my Android device (Samsung Galaxy Tab 2, Android OS 4.2.2). >> >> Here's my simple test.csd: >> ---------------------------------- >> >> >> >> -odac -d >> >> >> >> >> sr = 44100 >> ksmps = 100 >> nchnls = 2 >> >> gichan OSCinit 8000 >> >> instr 1 >> >> gkamp init 0 >> kans OSClisten gichan, "/1/fader1", "f", gkamp >> aout lfo gkamp * 12000, 440, 1 >> outs aout, aout >> >> endin >> >> >> >> >> i1 0 3600 >> >> >> >> --------------------- >> The TouchOSC Host is set to 127.0.0.1 >> Its outgoing port to 8000 >> Its slider is identified as /1/fader1 >> Slider range: 0 - 1 >> >> Even with a -v flag set in CsOptions, the .csd runs with no errors, Only >> WARNING: OSC listener #0 started at port 8000. Stops normally. There is >> no >> output amplitude. >> The only negative hint is a single console message: handle=0 - which to >> me >> indicates that no OSC message has been received. >> >> I've the definite impression that the OSClisten destination address >> "/1/fader1" is wrong (or its corresponding identification in TouchOSC, or >> maybe both). >> >> Can anyone shed any light? >> >> Art Hunkins >> >> >> ------------------------------------------------------------------------------ >> One dashboard for servers and applications across Physical-Virtual-Cloud >> Widest out-of-the-box monitoring support with 50+ applications >> Performance metrics, stats and reports that give you Actionable Insights >> Deep dive visibility with transaction tracing using APM Insight. >> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >> _______________________________________________ >> Csound-users mailing list >> Csound-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/csound-users >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here >> ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Csound-users mailing list Csound-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-users Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2015-05-13 05:14
From	Macciza Macpherson
Subject	Re: Android and OSClisten
	Hi Those /'s are part of the OSC standard. Sent from my iPhone > On 13 May 2015, at 12:38 pm, Art Hunkins wrote: > > Unfortunately, it doesn't. No difference from what reported. > > One confusing thing about the TouchOSC Editor, is that whatever you do, the > editor automatically adds "/" to all widget names - e.g., "fader1" becomes > "/fader1". And if you set the Page to anything, such as "1", fader1 becomes > "/1/fader1". No way of getting rid of the slash that I see (the same with > Auto mode). > > Of course, I'm using the Windows TouchOSC Editor. Is the action perhaps > different for the Mac? (I understand there is no Linux editor.) > > I note that all the default Layouts (in the Windows editor) use Auto mode > for both Pages and widgets. As Page 1 is always named "1" (which causes it > to be sent as "/1"), fader1 will be sent as "/1/fader1". So I assume this is > what happens even if you are not using a TouchOSC Editor. Or am I wrong? > > Art Hunkins > > ----- Original Message ----- > From: "Justin Smith" > To: "Art Hunkins" ; "csound users' discussions" > > Sent: Tuesday, May 12, 2015 8:45 PM > Subject: Re: [Csnd] Android and OSClisten > > >> if the slider is set to send "fader1", this should be working as written >> >>> On 5/12/15, Art Hunkins wrote: >>> In Mike's latest Csound6 for Android (6.05), I've been having a difficult >>> time getting OSClisten to receive OSC messages sent from a TouchOSC >>> Layout, >>> >>> all on my Android device (Samsung Galaxy Tab 2, Android OS 4.2.2). >>> >>> Here's my simple test.csd: >>> ---------------------------------- >>> >>> >>> >>> -odac -d >>> >>> >>> >>> >>> sr = 44100 >>> ksmps = 100 >>> nchnls = 2 >>> >>> gichan OSCinit 8000 >>> >>> instr 1 >>> >>> gkamp init 0 >>> kans OSClisten gichan, "/1/fader1", "f", gkamp >>> aout lfo gkamp * 12000, 440, 1 >>> outs aout, aout >>> >>> endin >>> >>> >>> >>> >>> i1 0 3600 >>> >>> >>> >>> --------------------- >>> The TouchOSC Host is set to 127.0.0.1 >>> Its outgoing port to 8000 >>> Its slider is identified as /1/fader1 >>> Slider range: 0 - 1 >>> >>> Even with a -v flag set in CsOptions, the .csd runs with no errors, Only >>> WARNING: OSC listener #0 started at port 8000. Stops normally. There is >>> no >>> output amplitude. >>> The only negative hint is a single console message: handle=0 - which to >>> me >>> indicates that no OSC message has been received. >>> >>> I've the definite impression that the OSClisten destination address >>> "/1/fader1" is wrong (or its corresponding identification in TouchOSC, or >>> maybe both). >>> >>> Can anyone shed any light? >>> >>> Art Hunkins >>> >>> >>> ------------------------------------------------------------------------------ >>> One dashboard for servers and applications across Physical-Virtual-Cloud >>> Widest out-of-the-box monitoring support with 50+ applications >>> Performance metrics, stats and reports that give you Actionable Insights >>> Deep dive visibility with transaction tracing using APM Insight. >>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >>> _______________________________________________ >>> Csound-users mailing list >>> Csound-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/csound-users >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here > > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > Csound-users mailing list > Csound-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-users > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Csound-users mailing list Csound-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-users Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here