Another quick note:

You wrote
"The same doesn't happen if you have an incorrect path for your .wav output. Everything seems fine until you want to listen to your music, and it's nowhere to be found (apparently unwritten)."

The console should report both if written or not as well as where it is saved to. It does for me.

Again I can't speak for Chromebooks, but on my phone and tablet if you output to -o/sdcard/filename.wav the the audio is written to the root directory, underneath where the folders are.

FWIW to anyone using Android devices,  I find having a good file manager (I personally like Astro) can be really helpful. MyFiles, the included manager, is functional but not great.

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, Scott -

Thanks for all your helpful observations. They led me to further insights and discoveries:

1) As a closer reading of our docs explain, the filepath for output files does not need double quotes, but such (as for samples) in the orch and sco *do* need quotes.

2) The filepath "/storage/emulated/0/Music/filename" is identical to "/sdcard/Music/filename". This is true for smartphones as well as Chromebooks.

3) Your observation that on phones, output files may be saved to any valid folder - which is true, does not apply to Chromebooks. The only folder that can be opened or saved to by Csound is the Music folder. So, not only does a full path have to be specified, on Chromebooks this must be the Music folder.

In sum, all the procedures detailed in the Csound manual and Mike's Csound for Android .pdf apply to all Android devices including Chromebooks. For the Chromebook alone, all reference to soundfiles must be to the Music folder, and you need to know that the Music folder is a subdirectory of the Play Files directory.

Thanks again, Scott.

Art Hunkins

http://www.arthunkins.com

On Tue, Dec 13, 2022 at 9:33 PM Scott Daughtrey <stunes6556@gmail.com> wrote:

Another quick note:

You wrote
"The same doesn't happen if you have an incorrect path for your .wav output. Everything seems fine until you want to listen to your music, and it's nowhere to be found (apparently unwritten)."

The console should report both if written or not as well as where it is saved to. It does for me.

Again I can't speak for Chromebooks, but on my phone and tablet if you output to -o/sdcard/filename.wav the the audio is written to the root directory, underneath where the folders are.

FWIW to anyone using Android devices,  I find having a good file manager (I personally like Astro) can be really helpful. MyFiles, the included manager, is functional but not great.

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