yes, that is expected. f0 is only allowed in the first score loaded before first compilation.
========================
Dr 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 6 Nov 2015, at 10:38, Rory Walsh  wrote:
> 
> The following results in a Csound illegal RT scoreline
> 
> csound->InputMessage("f0 1000")
> 
> Is this expected? I've attached a test program. 

Off the top of my head, the boundary is csoundStart(). A score read before it can affect the Csound performance duration,
whereas one launched after can’t (besides sending an “e 0” command). If you start Csound without a score, it will be
kept going forever (or whatever is the time limit, 7,000 years or something).

========================
Dr 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 6 Nov 2015, at 10:51, Rory Walsh  wrote:
> 
> Ah. Ok. So to clarify, there is no way to do this from the API if you are reading a score from disk, UNLESS you modify that score before compiling?
> 
> On 6 November 2015 at 10:41, Victor Lazzarini  wrote:
> yes, that is expected. f0 is only allowed in the first score loaded before first compilation.
> ========================
> Dr 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 6 Nov 2015, at 10:38, Rory Walsh  wrote:
> >
> > The following results in a Csound illegal RT scoreline
> >
> > csound->InputMessage("f0 1000")
> >
> > Is this expected? I've attached a test program.
> > 

and you need to use ReadScore() not InputMessage(), which is strictly RT events.
========================
Dr 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 6 Nov 2015, at 10:58, Victor Lazzarini  wrote:
> 
> Off the top of my head, the boundary is csoundStart(). A score read before it can affect the Csound performance duration,
> whereas one launched after can’t (besides sending an “e 0” command). If you start Csound without a score, it will be
> kept going forever (or whatever is the time limit, 7,000 years or something).
> 
> ========================
> Dr 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 6 Nov 2015, at 10:51, Rory Walsh  wrote:
>> 
>> Ah. Ok. So to clarify, there is no way to do this from the API if you are reading a score from disk, UNLESS you modify that score before compiling?
>> 
>> On 6 November 2015 at 10:41, Victor Lazzarini  wrote:
>> yes, that is expected. f0 is only allowed in the first score loaded before first compilation.
>> ========================
>> Dr 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 6 Nov 2015, at 10:38, Rory Walsh  wrote:
>>> 
>>> The following results in a Csound illegal RT scoreline
>>> 
>>> csound->InputMessage("f0 1000")
>>> 
>>> Is this expected? I've attached a test program.
>>>