Hi,

since more than a year I'm programming Apps on Android for my multimedia installations. For a possible future project I had the idea to include Csound for realtime sound generation in an app. To start with I downloaded yesterday the Csound App from Google Play, just to check if the processors on the device are powerful enough for the application I have in mind.

1.) The first problem I encountered with a simple example is that the performance does not stop normally (see 1st attached file). The instrument stopped as given by the score section after 5 seconds. Then the normal printout for ending the performance appears. But then it is looping (without restarting the instrument) producing output to the screen until the stop button is pressed.

2.) The second problem I realised, when trying to play the csd file, I'm currently working on. The parser stopped reported an error with the readfi opcode and stopped. The printout can be seen on the second attached file. A simple csd-file  the problem (3rd file) and some simple input file (4th file) for verifying and debugging the problem are attached.

In addition: if I interpret the printout correctly: The Csound app is 32 bit. If so is the also a 64 bit version? 

Cheers,

Karin 

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound App is a frontend developed by Michael Gogins, maybe he will be able to answer your questions in 
relation to it (you can think of it as the CsoundQT or Cabbage equivalent for Android).

The Csound for Android we release as part of the Csound project is an SDK for developing Android apps, 

https://github.com/csound/csound/releases/download/6.12.2/Csound6.12.0-Android.zip

which may be what you’d ultimately might want to to use. Currently, we release a floats version (32bit), 
but we may consider releasing a doubles (64bit) if there is a need. Note this is not to do with the processor/OS 
platform being 32 or 64bit.
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 21 Nov 2018, at 09:01, Karin Daum  wrote:
> 
> Hi,
> 
> since more than a year I'm programming Apps on Android for my multimedia installations. For a possible future project I had the idea to include Csound for realtime sound generation in an app. To start with I downloaded yesterday the Csound App from Google Play, just to check if the processors on the device are powerful enough for the application I have in mind.
> 
> 1.) The first problem I encountered with a simple example is that the performance does not stop normally (see 1st attached file). The instrument stopped as given by the score section after 5 seconds. Then the normal printout for ending the performance appears. But then it is looping (without restarting the instrument) producing output to the screen until the stop button is pressed.
> 
> 2.) The second problem I realised, when trying to play the csd file, I'm currently working on. The parser stopped reported an error with the readfi opcode and stopped. The printout can be seen on the second attached file. A simple csd-file  the problem (3rd file) and some simple input file (4th file) for verifying and debugging the problem are attached.
> 
> In addition: if I interpret the printout correctly: The Csound app is 32 bit. If so is the also a 64 bit version? 
> 
> Cheers,
> 
> Karin 
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
> 


Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Hi Victor,

thanks for your explanation. Indeed, finally I will have to use Csound6.12.0-Android.zip you mentioned. For the moment I wanted to get a feeling on how it behaves, especially concerning CPU time, and to see if my csd works at all.

cheers,

Karin

> On 21 Nov 2018, at 10:29, Victor Lazzarini  wrote:
> 
> Csound App is a frontend developed by Michael Gogins, maybe he will be able to answer your questions in 
> relation to it (you can think of it as the CsoundQT or Cabbage equivalent for Android).
> 
> The Csound for Android we release as part of the Csound project is an SDK for developing Android apps, 
> 
> https://github.com/csound/csound/releases/download/6.12.2/Csound6.12.0-Android.zip
> 
> which may be what you’d ultimately might want to to use. Currently, we release a floats version (32bit), 
> but we may consider releasing a doubles (64bit) if there is a need. Note this is not to do with the processor/OS 
> platform being 32 or 64bit.
> ========================
> Prof. Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952 
> 
>> On 21 Nov 2018, at 09:01, Karin Daum  wrote:
>> 
>> Hi,
>> 
>> since more than a year I'm programming Apps on Android for my multimedia installations. For a possible future project I had the idea to include Csound for realtime sound generation in an app. To start with I downloaded yesterday the Csound App from Google Play, just to check if the processors on the device are powerful enough for the application I have in mind.
>> 
>> 1.) The first problem I encountered with a simple example is that the performance does not stop normally (see 1st attached file). The instrument stopped as given by the score section after 5 seconds. Then the normal printout for ending the performance appears. But then it is looping (without restarting the instrument) producing output to the screen until the stop button is pressed.
>> 
>> 2.) The second problem I realised, when trying to play the csd file, I'm currently working on. The parser stopped reported an error with the readfi opcode and stopped. The printout can be seen on the second attached file. A simple csd-file  the problem (3rd file) and some simple input file (4th file) for verifying and debugging the problem are attached.
>> 
>> In addition: if I interpret the printout correctly: The Csound app is 32 bit. If so is the also a 64 bit version? 
>> 
>> Cheers,
>> 
>> Karin 
>> 
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>       https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>> 
> 
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

The problem is that Opcodes/date.c, which contains the readfi opcode,
is not included in the Android build of Csound. That is true of the
Csound for Android app, and it also appears to be true for the Android
SDK build of Csound mentioned by Victor.

I am trying to correct this omission now. If I do, I will post a new
release of the Csound for Android app immediately.

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Wed, Nov 21, 2018 at 6:39 AM Karin Daum  wrote:
>
> Hi Victor,
>
> thanks for your explanation. Indeed, finally I will have to use Csound6.12.0-Android.zip you mentioned. For the moment I wanted to get a feeling on how it behaves, especially concerning CPU time, and to see if my csd works at all.
>
> cheers,
>
> Karin
>
> > On 21 Nov 2018, at 10:29, Victor Lazzarini  wrote:
> >
> > Csound App is a frontend developed by Michael Gogins, maybe he will be able to answer your questions in
> > relation to it (you can think of it as the CsoundQT or Cabbage equivalent for Android).
> >
> > The Csound for Android we release as part of the Csound project is an SDK for developing Android apps,
> >
> > https://github.com/csound/csound/releases/download/6.12.2/Csound6.12.0-Android.zip
> >
> > which may be what you’d ultimately might want to to use. Currently, we release a floats version (32bit),
> > but we may consider releasing a doubles (64bit) if there is a need. Note this is not to do with the processor/OS
> > platform being 32 or 64bit.
> > ========================
> > Prof. Victor Lazzarini
> > Dean of Arts, Celtic Studies, and Philosophy,
> > Maynooth University,
> > Maynooth, Co Kildare, Ireland
> > Tel: 00 353 7086936
> > Fax: 00 353 1 7086952
> >
> >> On 21 Nov 2018, at 09:01, Karin Daum  wrote:
> >>
> >> Hi,
> >>
> >> since more than a year I'm programming Apps on Android for my multimedia installations. For a possible future project I had the idea to include Csound for realtime sound generation in an app. To start with I downloaded yesterday the Csound App from Google Play, just to check if the processors on the device are powerful enough for the application I have in mind.
> >>
> >> 1.) The first problem I encountered with a simple example is that the performance does not stop normally (see 1st attached file). The instrument stopped as given by the score section after 5 seconds. Then the normal printout for ending the performance appears. But then it is looping (without restarting the instrument) producing output to the screen until the stop button is pressed.
> >>
> >> 2.) The second problem I realised, when trying to play the csd file, I'm currently working on. The parser stopped reported an error with the readfi opcode and stopped. The printout can be seen on the second attached file. A simple csd-file  the problem (3rd file) and some simple input file (4th file) for verifying and debugging the problem are attached.
> >>
> >> In addition: if I interpret the printout correctly: The Csound app is 32 bit. If so is the also a 64 bit version?
> >>
> >> Cheers,
> >>
> >> Karin
> >>
> >> Csound mailing list
> >> Csound@listserv.heanet.ie
> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >> Send bugs reports to
> >>       https://github.com/csound/csound/issues
> >> Discussions of bugs and features can be posted here
> >> 
> >
> >
> > Csound mailing list
> > Csound@listserv.heanet.ie
> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> > Send bugs reports to
> >        https://github.com/csound/csound/issues
> > Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Thanks for reporting this. We will check.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 21 Nov 2018, at 15:54, Michael Gogins  wrote:
> 
> The problem is that Opcodes/date.c, which contains the readfi opcode,
> is not included in the Android build of Csound. That is true of the
> Csound for Android app, and it also appears to be true for the Android
> SDK build of Csound mentioned by Victor.
> 
> I am trying to correct this omission now. If I do, I will post a new
> release of the Csound for Android app immediately.
> 
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
> 
>> On Wed, Nov 21, 2018 at 6:39 AM Karin Daum  wrote:
>> 
>> Hi Victor,
>> 
>> thanks for your explanation. Indeed, finally I will have to use Csound6.12.0-Android.zip you mentioned. For the moment I wanted to get a feeling on how it behaves, especially concerning CPU time, and to see if my csd works at all.
>> 
>> cheers,
>> 
>> Karin
>> 
>>> On 21 Nov 2018, at 10:29, Victor Lazzarini  wrote:
>>> 
>>> Csound App is a frontend developed by Michael Gogins, maybe he will be able to answer your questions in
>>> relation to it (you can think of it as the CsoundQT or Cabbage equivalent for Android).
>>> 
>>> The Csound for Android we release as part of the Csound project is an SDK for developing Android apps,
>>> 
>>> https://github.com/csound/csound/releases/download/6.12.2/Csound6.12.0-Android.zip
>>> 
>>> which may be what you’d ultimately might want to to use. Currently, we release a floats version (32bit),
>>> but we may consider releasing a doubles (64bit) if there is a need. Note this is not to do with the processor/OS
>>> platform being 32 or 64bit.
>>> ========================
>>> Prof. Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>> 
>>>> On 21 Nov 2018, at 09:01, Karin Daum  wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> since more than a year I'm programming Apps on Android for my multimedia installations. For a possible future project I had the idea to include Csound for realtime sound generation in an app. To start with I downloaded yesterday the Csound App from Google Play, just to check if the processors on the device are powerful enough for the application I have in mind.
>>>> 
>>>> 1.) The first problem I encountered with a simple example is that the performance does not stop normally (see 1st attached file). The instrument stopped as given by the score section after 5 seconds. Then the normal printout for ending the performance appears. But then it is looping (without restarting the instrument) producing output to the screen until the stop button is pressed.
>>>> 
>>>> 2.) The second problem I realised, when trying to play the csd file, I'm currently working on. The parser stopped reported an error with the readfi opcode and stopped. The printout can be seen on the second attached file. A simple csd-file  the problem (3rd file) and some simple input file (4th file) for verifying and debugging the problem are attached.
>>>> 
>>>> In addition: if I interpret the printout correctly: The Csound app is 32 bit. If so is the also a 64 bit version?
>>>> 
>>>> Cheers,
>>>> 
>>>> Karin
>>>> 
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>      https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>> 
>>> 
>>> 
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>       https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>> 
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>        https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

thanks, for caring about it.

cheers,

Karin


> On 21 Nov 2018, at 16:53, Michael Gogins  wrote:
> 
> The problem is that Opcodes/date.c, which contains the readfi opcode,
> is not included in the Android build of Csound. That is true of the
> Csound for Android app, and it also appears to be true for the Android
> SDK build of Csound mentioned by Victor.
> 
> I am trying to correct this omission now. If I do, I will post a new
> release of the Csound for Android app immediately.
> 
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
> 
> On Wed, Nov 21, 2018 at 6:39 AM Karin Daum  wrote:
>> 
>> Hi Victor,
>> 
>> thanks for your explanation. Indeed, finally I will have to use Csound6.12.0-Android.zip you mentioned. For the moment I wanted to get a feeling on how it behaves, especially concerning CPU time, and to see if my csd works at all.
>> 
>> cheers,
>> 
>> Karin
>> 
>>> On 21 Nov 2018, at 10:29, Victor Lazzarini  wrote:
>>> 
>>> Csound App is a frontend developed by Michael Gogins, maybe he will be able to answer your questions in
>>> relation to it (you can think of it as the CsoundQT or Cabbage equivalent for Android).
>>> 
>>> The Csound for Android we release as part of the Csound project is an SDK for developing Android apps,
>>> 
>>> https://github.com/csound/csound/releases/download/6.12.2/Csound6.12.0-Android.zip
>>> 
>>> which may be what you’d ultimately might want to to use. Currently, we release a floats version (32bit),
>>> but we may consider releasing a doubles (64bit) if there is a need. Note this is not to do with the processor/OS
>>> platform being 32 or 64bit.
>>> ========================
>>> Prof. Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>> 
>>>> On 21 Nov 2018, at 09:01, Karin Daum  wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> since more than a year I'm programming Apps on Android for my multimedia installations. For a possible future project I had the idea to include Csound for realtime sound generation in an app. To start with I downloaded yesterday the Csound App from Google Play, just to check if the processors on the device are powerful enough for the application I have in mind.
>>>> 
>>>> 1.) The first problem I encountered with a simple example is that the performance does not stop normally (see 1st attached file). The instrument stopped as given by the score section after 5 seconds. Then the normal printout for ending the performance appears. But then it is looping (without restarting the instrument) producing output to the screen until the stop button is pressed.
>>>> 
>>>> 2.) The second problem I realised, when trying to play the csd file, I'm currently working on. The parser stopped reported an error with the readfi opcode and stopped. The printout can be seen on the second attached file. A simple csd-file  the problem (3rd file) and some simple input file (4th file) for verifying and debugging the problem are attached.
>>>> 
>>>> In addition: if I interpret the printout correctly: The Csound app is 32 bit. If so is the also a 64 bit version?
>>>> 
>>>> Cheers,
>>>> 
>>>> Karin
>>>> 
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>      https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>> 
>>> 
>>> 
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>       https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>> 
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>        https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

I have fixed both of these issues in the Csound for Android app, and a
new version is available on the Google Play Store.

I added filein and a number of other plugin opcodes to the Android NDK
build. I did not include serial, system call, the Chua opcodes, or the
linear algebra opcodes, but most of the others are now in.

I changed the Google Oboe audio callback to explicitly close the audio
stream when Csound has finished performing.

Your example now works on my phone.

Thanks for the bug reports!

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Wed, Nov 21, 2018 at 11:15 AM Karin Daum  wrote:
>
> thanks, for caring about it.
>
> cheers,
>
> Karin
>
>
> > On 21 Nov 2018, at 16:53, Michael Gogins  wrote:
> >
> > The problem is that Opcodes/date.c, which contains the readfi opcode,
> > is not included in the Android build of Csound. That is true of the
> > Csound for Android app, and it also appears to be true for the Android
> > SDK build of Csound mentioned by Victor.
> >
> > I am trying to correct this omission now. If I do, I will post a new
> > release of the Csound for Android app immediately.
> >
> > -----------------------------------------------------
> > Michael Gogins
> > Irreducible Productions
> > http://michaelgogins.tumblr.com
> > Michael dot Gogins at gmail dot com
> >
> > On Wed, Nov 21, 2018 at 6:39 AM Karin Daum  wrote:
> >>
> >> Hi Victor,
> >>
> >> thanks for your explanation. Indeed, finally I will have to use Csound6.12.0-Android.zip you mentioned. For the moment I wanted to get a feeling on how it behaves, especially concerning CPU time, and to see if my csd works at all.
> >>
> >> cheers,
> >>
> >> Karin
> >>
> >>> On 21 Nov 2018, at 10:29, Victor Lazzarini  wrote:
> >>>
> >>> Csound App is a frontend developed by Michael Gogins, maybe he will be able to answer your questions in
> >>> relation to it (you can think of it as the CsoundQT or Cabbage equivalent for Android).
> >>>
> >>> The Csound for Android we release as part of the Csound project is an SDK for developing Android apps,
> >>>
> >>> https://github.com/csound/csound/releases/download/6.12.2/Csound6.12.0-Android.zip
> >>>
> >>> which may be what you’d ultimately might want to to use. Currently, we release a floats version (32bit),
> >>> but we may consider releasing a doubles (64bit) if there is a need. Note this is not to do with the processor/OS
> >>> platform being 32 or 64bit.
> >>> ========================
> >>> Prof. Victor Lazzarini
> >>> Dean of Arts, Celtic Studies, and Philosophy,
> >>> Maynooth University,
> >>> Maynooth, Co Kildare, Ireland
> >>> Tel: 00 353 7086936
> >>> Fax: 00 353 1 7086952
> >>>
> >>>> On 21 Nov 2018, at 09:01, Karin Daum  wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> since more than a year I'm programming Apps on Android for my multimedia installations. For a possible future project I had the idea to include Csound for realtime sound generation in an app. To start with I downloaded yesterday the Csound App from Google Play, just to check if the processors on the device are powerful enough for the application I have in mind.
> >>>>
> >>>> 1.) The first problem I encountered with a simple example is that the performance does not stop normally (see 1st attached file). The instrument stopped as given by the score section after 5 seconds. Then the normal printout for ending the performance appears. But then it is looping (without restarting the instrument) producing output to the screen until the stop button is pressed.
> >>>>
> >>>> 2.) The second problem I realised, when trying to play the csd file, I'm currently working on. The parser stopped reported an error with the readfi opcode and stopped. The printout can be seen on the second attached file. A simple csd-file  the problem (3rd file) and some simple input file (4th file) for verifying and debugging the problem are attached.
> >>>>
> >>>> In addition: if I interpret the printout correctly: The Csound app is 32 bit. If so is the also a 64 bit version?
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Karin
> >>>>
> >>>> Csound mailing list
> >>>> Csound@listserv.heanet.ie
> >>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>>> Send bugs reports to
> >>>>      https://github.com/csound/csound/issues
> >>>> Discussions of bugs and features can be posted here
> >>>> 
> >>>
> >>>
> >>> Csound mailing list
> >>> Csound@listserv.heanet.ie
> >>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >>> Send bugs reports to
> >>>       https://github.com/csound/csound/issues
> >>> Discussions of bugs and features can be posted here
> >>
> >> Csound mailing list
> >> Csound@listserv.heanet.ie
> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> >> Send bugs reports to
> >>        https://github.com/csound/csound/issues
> >> Discussions of bugs and features can be posted here
> >
> > Csound mailing list
> > Csound@listserv.heanet.ie
> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> > Send bugs reports to
> >        https://github.com/csound/csound/issues
> > Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Hi Michael,

thank you for fixing the problems. My main csd I’m currently working on works. Unfortunately CPU power seems to be a limitation, although the smartphone used for testing is quite fast (HTC U11). I hear a lot of interruptions and using top shows me that Csound runs at about 100% of a core. Obviously, there are too many instruments running simultaneously. I have to see, if I find a solution for it.

cheers,

Karin

> On 21 Nov 2018, at 22:41, Michael Gogins  wrote:
> 
> I have fixed both of these issues in the Csound for Android app, and a
> new version is available on the Google Play Store.
> 
> I added filein and a number of other plugin opcodes to the Android NDK
> build. I did not include serial, system call, the Chua opcodes, or the
> linear algebra opcodes, but most of the others are now in.
> 
> I changed the Google Oboe audio callback to explicitly close the audio
> stream when Csound has finished performing.
> 
> Your example now works on my phone.
> 
> Thanks for the bug reports!
> 
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
> 
> On Wed, Nov 21, 2018 at 11:15 AM Karin Daum  wrote:
>> 
>> thanks, for caring about it.
>> 
>> cheers,
>> 
>> Karin
>> 
>> 
>>> On 21 Nov 2018, at 16:53, Michael Gogins  wrote:
>>> 
>>> The problem is that Opcodes/date.c, which contains the readfi opcode,
>>> is not included in the Android build of Csound. That is true of the
>>> Csound for Android app, and it also appears to be true for the Android
>>> SDK build of Csound mentioned by Victor.
>>> 
>>> I am trying to correct this omission now. If I do, I will post a new
>>> release of the Csound for Android app immediately.
>>> 
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>> 
>>> On Wed, Nov 21, 2018 at 6:39 AM Karin Daum  wrote:
>>>> 
>>>> Hi Victor,
>>>> 
>>>> thanks for your explanation. Indeed, finally I will have to use Csound6.12.0-Android.zip you mentioned. For the moment I wanted to get a feeling on how it behaves, especially concerning CPU time, and to see if my csd works at all.
>>>> 
>>>> cheers,
>>>> 
>>>> Karin
>>>> 
>>>>> On 21 Nov 2018, at 10:29, Victor Lazzarini  wrote:
>>>>> 
>>>>> Csound App is a frontend developed by Michael Gogins, maybe he will be able to answer your questions in
>>>>> relation to it (you can think of it as the CsoundQT or Cabbage equivalent for Android).
>>>>> 
>>>>> The Csound for Android we release as part of the Csound project is an SDK for developing Android apps,
>>>>> 
>>>>> https://github.com/csound/csound/releases/download/6.12.2/Csound6.12.0-Android.zip
>>>>> 
>>>>> which may be what you’d ultimately might want to to use. Currently, we release a floats version (32bit),
>>>>> but we may consider releasing a doubles (64bit) if there is a need. Note this is not to do with the processor/OS
>>>>> platform being 32 or 64bit.
>>>>> ========================
>>>>> Prof. Victor Lazzarini
>>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>>> Maynooth University,
>>>>> Maynooth, Co Kildare, Ireland
>>>>> Tel: 00 353 7086936
>>>>> Fax: 00 353 1 7086952
>>>>> 
>>>>>> On 21 Nov 2018, at 09:01, Karin Daum  wrote:
>>>>>> 
>>>>>> Hi,
>>>>>> 
>>>>>> since more than a year I'm programming Apps on Android for my multimedia installations. For a possible future project I had the idea to include Csound for realtime sound generation in an app. To start with I downloaded yesterday the Csound App from Google Play, just to check if the processors on the device are powerful enough for the application I have in mind.
>>>>>> 
>>>>>> 1.) The first problem I encountered with a simple example is that the performance does not stop normally (see 1st attached file). The instrument stopped as given by the score section after 5 seconds. Then the normal printout for ending the performance appears. But then it is looping (without restarting the instrument) producing output to the screen until the stop button is pressed.
>>>>>> 
>>>>>> 2.) The second problem I realised, when trying to play the csd file, I'm currently working on. The parser stopped reported an error with the readfi opcode and stopped. The printout can be seen on the second attached file. A simple csd-file  the problem (3rd file) and some simple input file (4th file) for verifying and debugging the problem are attached.
>>>>>> 
>>>>>> In addition: if I interpret the printout correctly: The Csound app is 32 bit. If so is the also a 64 bit version?
>>>>>> 
>>>>>> Cheers,
>>>>>> 
>>>>>> Karin
>>>>>> 
>>>>>> Csound mailing list
>>>>>> Csound@listserv.heanet.ie
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>     https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>>> 
>>>>> 
>>>>> 
>>>>> Csound mailing list
>>>>> Csound@listserv.heanet.ie
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>      https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>> 
>>>> Csound mailing list
>>>> Csound@listserv.heanet.ie
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>       https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>> 
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>       https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>> 
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>        https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here