Hello,<br><br>Wouldn&#39;t it be easier to make a Android for RtAudio, which is already available on multiple platforms and multiple back ends? I don&#39;t know enough about the inner workings of ChucK ouput, I was just wondering why it isn&#39;t possible, if you already looked into this I&#39;m interested.<br>

<br>Rémi Gillig.<br><br><div class="gmail_quote">On 12 March 2012 15:15, Kenneth Stewart <span dir="ltr">&lt;<a href="mailto:kstewartgt@gmail.com">kstewartgt@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

Hi,<br>
<br>
I&#39;m working on a senior design project where we&#39;re trying to explore<br>
porting ChucK to work on Android devices using the Android NDK.<br>
Currently we&#39;re working on rewriting some of the digiio_rtaudio<br>
wrapper to use OpenSL ES instead of the rtaudio functions. I was<br>
wondering if anyone could provide any advice or tips for doing this,<br>
or just let us know if we&#39;re heading down the wrong path.<br>
<br>
We think we&#39;ve isolated the areas where rtaudio functions are used and<br>
want to substitute those calls for the right series of OpenSL<br>
functions, but figuring out what the appropriate mappings are between<br>
what OpenSL needs and what ChucK expects to connect to is taking a<br>
good bit of research. Are there any obvious pitfalls we should be<br>
aware of?<br>
<br>
Thank you for any advice in this area.<br>
Kenneth<br>
_______________________________________________<br>
chuck-dev mailing list<br>
<a href="mailto:chuck-dev@lists.cs.princeton.edu">chuck-dev@lists.cs.princeton.edu</a><br>
<a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev</a><br>
</blockquote></div><br>