Hi All,

For issues #201[1] and #206[2], we've added plugin libraries for the
scanned synthesis and OSC opcodes for Android.  I have placed a zip of
binaries available at:

http://www.kunstmusik.com/android_osc_scanned.zip

Could someone volunteer to try these with your Android application?
The libraries are located in the libs folders of the two projects in
the zip.

Thanks!
steven


[1] - https://github.com/csound/csound/issues/201
[2] - https://github.com/csound/csound/issues/206

Exciting!

Is it so that to test I should copy the libraries (like libOSC.so) to the 
libraries folder of my android porject (or include it other way) and see if I 
can use OSC opcodes in my csound code of an android app?

tarmo


On Friday 09 May 2014 20:46:54 Steven Yi wrote:
> Hi All,
> 
> For issues #201[1] and #206[2], we've added plugin libraries for the
> scanned synthesis and OSC opcodes for Android.  I have placed a zip of
> binaries available at:
> 
> http://www.kunstmusik.com/android_osc_scanned.zip
> 
> Could someone volunteer to try these with your Android application?
> The libraries are located in the libs folders of the two projects in
> the zip.
> 
> Thanks!
> steven
> 
> 
> [1] - https://github.com/csound/csound/issues/201
> [2] - https://github.com/csound/csound/issues/206
> 
> 
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"

Hi Tarmo,

The mechanism for loading opcode libs should be done in the same way
as the CSDPlayer application that comes with the Csound for Android
download.  Maybe the easiest way to test is put the libs from my zip
into the CSDPlayer/lib folder, then build and install to device and
give it a try.  You *should* then be able to use the scanned synthesis
and OSC opcodes from a CSD.

Let me know if you have further questions!
steven

On Fri, May 9, 2014 at 10:13 PM, Tarmo Johannes
 wrote:
> Exciting!
>
> Is it so that to test I should copy the libraries (like libOSC.so) to the
> libraries folder of my android porject (or include it other way) and see if I
> can use OSC opcodes in my csound code of an android app?
>
> tarmo
>
>
> On Friday 09 May 2014 20:46:54 Steven Yi wrote:
>> Hi All,
>>
>> For issues #201[1] and #206[2], we've added plugin libraries for the
>> scanned synthesis and OSC opcodes for Android.  I have placed a zip of
>> binaries available at:
>>
>> http://www.kunstmusik.com/android_osc_scanned.zip
>>
>> Could someone volunteer to try these with your Android application?
>> The libraries are located in the libs folders of the two projects in
>> the zip.
>>
>> Thanks!
>> steven
>>
>>
>> [1] - https://github.com/csound/csound/issues/201
>> [2] - https://github.com/csound/csound/issues/206
>>
>>
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>
>
>
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
>

Hi,

I added the libraries to CsoundAppActivity project and loaded a csd that uses 
OSClisten and OSCsend, pressing on Start crashed the application:

Output from LogCat:

05-10 02:11:55.583: I/ActivityManager(504): Process com.csounds.Csound6 (pid 
2658) has died.
05-10 02:11:55.583: I/WindowState(504): WIN DEATH: Window{425d47e8 u0 
com.csounds.Csound6/com.csounds.Csound6.CsoundAppActivity}
05-10 02:11:55.583: W/ActivityManager(504): Force removing 
ActivityRecord{4268f8c0 u0 com.csounds.Csound6/.CsoundAppActivity t5}: app 
died, no saved state
05-10 02:11:55.633: D/Zygote(123): Process 2658 exited cleanly (1)
05-10 02:11:55.643: W/Binder(714): Caught a RuntimeException from the binder 
stub implementation.
05-10 02:11:55.643: W/Binder(714): java.lang.NullPointerException
05-10 02:11:55.643: W/Binder(714): 	at 
android.inputmethodservice.IInputMethodWrapper.setSessionEnabled(IInputMethodWrapper.java:280)
05-10 02:11:55.643: W/Binder(714): 	at 
com.android.internal.view.IInputMethod$Stub.onTransact(IInputMethod.java:129)
05-10 02:11:55.643: W/Binder(714): 	at 
android.os.Binder.execTransact(Binder.java:404)
05-10 02:11:55.643: W/Binder(714): 	at dalvik.system.NativeStart.run(Native 
Method)
05-10 02:11:55.643: W/InputMethodManagerService(504): Got RemoteException 
sending setActive(false) notification to pid 2658 uid 10155
05-10 02:13:12.313: D/dalvikvm(916): GC_CONCURRENT freed 429K, 6% free 
8900K/9372K, paused 1ms+2ms, total 28ms

There are many things that maybe I did wrong, 

I will try to work on it, probably in a fresh app project in coming days.

thanks!
tarmo



On Friday 09 May 2014 22:37:35 Steven Yi wrote:
> Hi Tarmo,
> 
> The mechanism for loading opcode libs should be done in the same way
> as the CSDPlayer application that comes with the Csound for Android
> download.  Maybe the easiest way to test is put the libs from my zip
> into the CSDPlayer/lib folder, then build and install to device and
> give it a try.  You *should* then be able to use the scanned synthesis
> and OSC opcodes from a CSD.
> 
> Let me know if you have further questions!
> steven
> 
> On Fri, May 9, 2014 at 10:13 PM, Tarmo Johannes
> 
>  wrote:
> > Exciting!
> > 
> > Is it so that to test I should copy the libraries (like libOSC.so) to the
> > libraries folder of my android porject (or include it other way) and see
> > if I can use OSC opcodes in my csound code of an android app?
> > 
> > tarmo
> > 
> > On Friday 09 May 2014 20:46:54 Steven Yi wrote:
> >> Hi All,
> >> 
> >> For issues #201[1] and #206[2], we've added plugin libraries for the
> >> scanned synthesis and OSC opcodes for Android.  I have placed a zip of
> >> binaries available at:
> >> 
> >> http://www.kunstmusik.com/android_osc_scanned.zip
> >> 
> >> Could someone volunteer to try these with your Android application?
> >> The libraries are located in the libs folders of the two projects in
> >> the zip.
> >> 
> >> Thanks!
> >> steven
> >> 
> >> 
> >> [1] - https://github.com/csound/csound/issues/201
> >> [2] - https://github.com/csound/csound/issues/206
> >> 
> >> 
> >> Send bugs reports to
> >> 
> >>         https://github.com/csound/csound/issues
> >> 
> >> Discussions of bugs and features can be posted here
> >> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> >> csound"
> > 
> > Send bugs reports to
> > 
> >         https://github.com/csound/csound/issues
> > 
> > Discussions of bugs and features can be posted here
> > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> > csound"
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"

Oh, 

I realized that I needed to give the app internet permissions in order to let 
any network operations work

I added

to AndroidManifest.xml

and osc worked like charm - both receiving and sending! I attach a csd that I 
used for testing

This is fantastic - no more need to use javaOSC or anything to communicate 
with otehr devices!

I did not try scanned syntehsis yet.

tarmo
 
On Friday 09 May 2014 22:37:35 Steven Yi wrote:
> Hi Tarmo,
> 
> The mechanism for loading opcode libs should be done in the same way
> as the CSDPlayer application that comes with the Csound for Android
> download.  Maybe the easiest way to test is put the libs from my zip
> into the CSDPlayer/lib folder, then build and install to device and
> give it a try.  You *should* then be able to use the scanned synthesis
> and OSC opcodes from a CSD.
> 
> Let me know if you have further questions!
> steven
> 
> On Fri, May 9, 2014 at 10:13 PM, Tarmo Johannes
> 
>  wrote:
> > Exciting!
> > 
> > Is it so that to test I should copy the libraries (like libOSC.so) to the
> > libraries folder of my android porject (or include it other way) and see
> > if I can use OSC opcodes in my csound code of an android app?
> > 
> > tarmo
> > 
> > On Friday 09 May 2014 20:46:54 Steven Yi wrote:
> >> Hi All,
> >> 
> >> For issues #201[1] and #206[2], we've added plugin libraries for the
> >> scanned synthesis and OSC opcodes for Android.  I have placed a zip of
> >> binaries available at:
> >> 
> >> http://www.kunstmusik.com/android_osc_scanned.zip
> >> 
> >> Could someone volunteer to try these with your Android application?
> >> The libraries are located in the libs folders of the two projects in
> >> the zip.
> >> 
> >> Thanks!
> >> steven
> >> 
> >> 
> >> [1] - https://github.com/csound/csound/issues/201
> >> [2] - https://github.com/csound/csound/issues/206
> >> 
> >> 
> >> Send bugs reports to
> >> 
> >>         https://github.com/csound/csound/issues
> >> 
> >> Discussions of bugs and features can be posted here
> >> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> >> csound"
> > 
> > Send bugs reports to
> > 
> >         https://github.com/csound/csound/issues
> > 
> > Discussions of bugs and features can be posted here
> > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> > csound"
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"

Great, I am very pleased. Now I can close the issue in github.
========================
Dr Victor Lazzarini
Senior Lecturer
NUI Maynooth, Ireland
victor dot lazzarini at nuim dot ie




On 10 May 2014, at 00:37, Tarmo Johannes  wrote:

> Oh, 
> 
> I realized that I needed to give the app internet permissions in order to let 
> any network operations work
> 
> I added
> 
> to AndroidManifest.xml
> 
> and osc worked like charm - both receiving and sending! I attach a csd that I 
> used for testing
> 
> This is fantastic - no more need to use javaOSC or anything to communicate 
> with otehr devices!
> 
> I did not try scanned syntehsis yet.
> 
> tarmo
> 
> On Friday 09 May 2014 22:37:35 Steven Yi wrote:
>> Hi Tarmo,
>> 
>> The mechanism for loading opcode libs should be done in the same way
>> as the CSDPlayer application that comes with the Csound for Android
>> download.  Maybe the easiest way to test is put the libs from my zip
>> into the CSDPlayer/lib folder, then build and install to device and
>> give it a try.  You *should* then be able to use the scanned synthesis
>> and OSC opcodes from a CSD.
>> 
>> Let me know if you have further questions!
>> steven
>> 
>> On Fri, May 9, 2014 at 10:13 PM, Tarmo Johannes
>> 
>>  wrote:
>>> Exciting!
>>> 
>>> Is it so that to test I should copy the libraries (like libOSC.so) to the
>>> libraries folder of my android porject (or include it other way) and see
>>> if I can use OSC opcodes in my csound code of an android app?
>>> 
>>> tarmo
>>> 
>>> On Friday 09 May 2014 20:46:54 Steven Yi wrote:
>>>> Hi All,
>>>> 
>>>> For issues #201[1] and #206[2], we've added plugin libraries for the
>>>> scanned synthesis and OSC opcodes for Android.  I have placed a zip of
>>>> binaries available at:
>>>> 
>>>> http://www.kunstmusik.com/android_osc_scanned.zip
>>>> 
>>>> Could someone volunteer to try these with your Android application?
>>>> The libraries are located in the libs folders of the two projects in
>>>> the zip.
>>>> 
>>>> Thanks!
>>>> steven
>>>> 
>>>> 
>>>> [1] - https://github.com/csound/csound/issues/201
>>>> [2] - https://github.com/csound/csound/issues/206
>>>> 
>>>> 
>>>> Send bugs reports to
>>>> 
>>>>        https://github.com/csound/csound/issues
>>>> 
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>> 
>>> Send bugs reports to
>>> 
>>>        https://github.com/csound/csound/issues
>>> 
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>> Send bugs reports to
>>        https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
> 
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 
> 
> 
> 

Hey Victor,

I think one thing left to do is add liblo-android to GitHub and update the downloadDependencies.sh script to clone from there. I can look at that tomorrow if you like.

Steven

Hello Steven,

Regarding loading libs in Android, I have an app that works without any
problems but I'm NOT manually loading the libraries as it's shown in the
CSDPlayer app (doing the calls
java.lang.System.loadLibrary("gnustl_shared"), etc. ). However, I do see in
the logcat that dalvikvm is loading the libraries (Trying to load lib... )
libgnustl_shared, libsndfile and libcsoundandroid when I start my app.

Does this mean that they might not automatically load in other devices and
that a manual request is safer?

Thanks for your help.

Hector




--
View this message in context: http://csound.1045644.n5.nabble.com/Android-testing-requested-scanned-synthesis-and-OSC-opcodes-tp5735071p5735153.html
Sent from the Csound - General mailing list archive at Nabble.com.

Hi Hector,

Yes, I think the library loading isn't really consistent across
implementations.  I think Michael added those in because they were not
getting loaded on his device at the time.  I'm not sure if anything
has changed since then, and I'm not sure we've revisited it to test on
devices, but I'd go with explicit loading of the libs to be safe.

steven

On Mon, May 12, 2014 at 7:23 PM, hcenteno  wrote:
> Hello Steven,
>
> Regarding loading libs in Android, I have an app that works without any
> problems but I'm NOT manually loading the libraries as it's shown in the
> CSDPlayer app (doing the calls
> java.lang.System.loadLibrary("gnustl_shared"), etc. ). However, I do see in
> the logcat that dalvikvm is loading the libraries (Trying to load lib... )
> libgnustl_shared, libsndfile and libcsoundandroid when I start my app.
>
> Does this mean that they might not automatically load in other devices and
> that a manual request is safer?
>
> Thanks for your help.
>
> Hector
>
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Android-testing-requested-scanned-synthesis-and-OSC-opcodes-tp5735071p5735153.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
>