My son and I are doing a joint Android app. My .csd portion of it is working 
file, but my son has to use the output once written (here, soundtrack.wav; 
my CsOptions currently simply specifies: -o soundtrack.wav.)

David writes:

"I'm having trouble getting it [.csd's output file] to sit in the 
appropriate directory. It seems that if I specify anything but a full path 
to the output file I get a Csound error like


02-04 15:06:08.024: I/AndroidCsound(28653): sfinit: cannot open 
soundtrack.wav


It seems that relative paths typically work when you use the command line. 
Perhaps there is a context missing when the execution is programmatic such 
that it doesn't know where it's trying to put the file? For now, I'm going 
to just construct the csound file and copy it to a directory each time a mix 
must be made, so that the specific output file location can be added (it's 
bound to be different on each device). But if you know of a better way, I 
would try that first."

Suggestions anyone? (TIA)

Art Hunkins 

Hello Art,

Have you specified the write permissions in the manifest? If you're trying 
to write to an sdcard location, then that needs to be set.
A bit of a hack for specifying a fixed path that works on all devices is to 
use "/mnt/sdcard". I have found it to work on devices that don't have an sd 
card as well as those that do.

I do wonder though if there isn't a more elegant way of doing this by 
passing values to CSound that it can pick up when executing a score. A bit 
like envrionment variables? You could use such a mechanism to pass a path to 
the csd.

All the best,

Jacques

----- Original Message ----- 
From: "Art Hunkins" 
To: 
Sent: Tuesday, February 05, 2013 1:11 AM
Subject: [Csnd] Android Csound Output File Location


> My son and I are doing a joint Android app. My .csd portion of it is 
> working file, but my son has to use the output once written (here, 
> soundtrack.wav; my CsOptions currently simply specifies: -o 
> soundtrack.wav.)
>
> David writes:
>
> "I'm having trouble getting it [.csd's output file] to sit in the 
> appropriate directory. It seems that if I specify anything but a full path 
> to the output file I get a Csound error like
>
>
> 02-04 15:06:08.024: I/AndroidCsound(28653): sfinit: cannot open 
> soundtrack.wav
>
>
> It seems that relative paths typically work when you use the command line. 
> Perhaps there is a context missing when the execution is programmatic such 
> that it doesn't know where it's trying to put the file? For now, I'm going 
> to just construct the csound file and copy it to a directory each time a 
> mix must be made, so that the specific output file location can be added 
> (it's bound to be different on each device). But if you know of a better 
> way, I would try that first."
>
> Suggestions anyone? (TIA)
>
> Art Hunkins
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
> csound"
>