Android Csound question
| Date | 2016-08-27 16:56 |
| From | Dave Seidel |
| Subject | Android Csound question |
I am trying to build a Csound app using HTML5 for use on Android. My CSD is still a work in progress. When I load it in the app, the UI displays, but when I start it, I see a quick flash of some text in the app console, then the app dies. Is there any way to see what made Csound crash, such as a log file somewhere on the Android system?
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
Related question: can I use #include with files in the same location as the .csd file, in both orchestra and the score section? Just in case this is what's blowing up. - Dave |
| Date | 2016-08-27 17:03 |
| From | Dave Seidel |
| Subject | Re: Android Csound question |
It's no longer crashing, bit I imagine I will crash it again eventually, so the question is still valid, if less urgent. On Sat, Aug 27, 2016 at 11:56 AM, Dave Seidel <dave.seidel@gmail.com> wrote:
|
| Date | 2016-08-27 17:05 |
| From | Michael Gogins |
| Subject | Re: Android Csound question |
The developers of Android deliberately made it hard to see the system level logs. You can do it with an Android debugger though. I don't recall what happened when I tried using #include on Android but I can think of some complications. You would need appropriate Android permissions, and then the files would have to be accessible to the app itself. I will try an experiment with the Android for Csound app and let you know what happens. Are you using this app as a basis for your application, or are you developing something from scratch using the Android Developer Kit? Regards, Mike ----------------------------------------------------- Michael GoginsIrreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Sat, Aug 27, 2016 at 11:56 AM, Dave Seidel <dave.seidel@gmail.com> wrote:
|
| Date | 2016-08-27 17:09 |
| From | Dave Seidel |
| Subject | Re: Android Csound question |
Thanks, Mike. To be clear, when I say "app", I simply mean a Csound .csd loaded and running in the official Csound6 app. That is what is crashing (and it just happened again. The #nclude files are in the same filesystem location as the csd. On Sat, Aug 27, 2016 at 12:05 PM, Michael Gogins <michael.gogins@gmail.com> wrote:
|
| Date | 2016-08-27 17:17 |
| From | Dave Seidel |
| Subject | Re: Android Csound question |
In the meantime, I'm editing the file under Linux and using scp to sync it to the Android table, and if I validate my syntax running it under csound on Linux first, then it runs within the Android app. (I know I can edit on the tablet, and I have a good editor -- DroidEdit -- but I'm much more productive with a physical keyboard and a normal-sized screen. Once I get to the tweaking stage, then I'll probably just do it all on Android.) On Sat, Aug 27, 2016 at 12:09 PM, Dave Seidel <dave.seidel@gmail.com> wrote:
|
| Date | 2016-08-27 17:37 |
| From | Steven Yi |
| Subject | Re: Android Csound question |
Crashes are never good and Csound should exit gracefully. Perhaps there's a bug somewhere. That said, you can view logs with adb (I think "adb logcat" is the command). On Sat, Aug 27, 2016, 12:17 PM Dave Seidel <dave.seidel@gmail.com> wrote:
|
| Date | 2016-08-27 18:06 |
| From | Michael Gogins |
| Subject | Re: Android Csound question |
OK, as I said I will test this myself in an hour or so. Regards, Mike ----------------------------------------------------- Michael GoginsIrreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Sat, Aug 27, 2016 at 12:09 PM, Dave Seidel <dave.seidel@gmail.com> wrote:
|
| Date | 2016-08-27 18:33 |
| From | Dave Seidel |
| Subject | Re: Android Csound question |
The Csound6 app seems to crash when it tries to run a .csd with a syntax error. For example, when I run my script under csound and get an error such as this: error: syntax error, unexpected NUMBER_TOKEN, expecting T_IDENT (token ".5") from file shim-tet-organ.csd (1) line 192: >>> ktrig8, .5 <<< Parsing failed due to invalid input! Stopping on parser failure cannot compile orchestra then it will crash the Android app when I click the Start button. So I am now using csound on my laptop to "lint" the csd before I try to run it on the tablet. On Sat, Aug 27, 2016 at 1:06 PM, Michael Gogins <michael.gogins@gmail.com> wrote:
|