Hi Christopher,

I'm not sure about #1, but if that's not working, you could try using:

        csoundInputMessage([csoundObj getCsound], (char*)[score
cStringUsingEncoding:NSASCIIStringEncoding]);

It might be a bug in csoundReadScore.  If the above works, then please
file a bug as that'd be an issue for all API users.

For #2, csoundObj does it's own setting of CoreAudio callbacks and
things.  I'm not sure exactly but I think we had put together the API
with the assumption that one would be rendering to realtime audio out
(and optionally recording), or rendering to disk in non-realtime. The
scenario of render but not to audio out but to disk in realtime hasn't
been covered.  One option might be to try writing to an audio file
within csound code and not using any outs opcodes, but then you'd have
to make sure you pass in a file location you could write to.  Other
than that, you should probably file a request in the sourceforge
tracker and hopefully someone will get to it soon.  (If anyone has
code already for this use case, please do consider contributing!)

Thanks,
steven

On Mon, Jul 29, 2013 at 3:44 PM, Christopher Saunders
 wrote:
> I have 2 questions about the Csound6 iOS SDK
>
>
> 1. Does the method sendScore: accept f statements?
>
> I've been trying something like this
>
> [self.csound sendScore:@"f1 0 128 10 1"];
>
> and nothing happens.
>
> I've gotten the same functionality by creating  an instrument solely
> dedicated to replacing a table, but I'd rather use f-statements.
>
>
> 2. Do the option flags work the same as command line csound?
>
> In the Csound-iOS-6.00.0 project, I want to modify the RecordTest example so
> that it doesn't howl with feedback.
>
> My assumption is that I would remove the -o dac flag, the csd would record
> to a file without monitoring.
>
> But with the flag removed, the csd still outputs audio to the dac, is there
> something I'm missing here?
>
>
>