Hi,

I'm heavily using UDOs in my projects about human communication. I'm just extending the existing csd form stereo (with only two voices) to 8 channel. At the same time I increased the number of virtual speakers e.g. 16. 

All content i.e. the text to be spoken by the virtual speakers the 2-D panning and the time schedule is done at i-rate. The heart is an UDO called 

         CreateSentence. 

This calls all UDOs necessary to do the job and finally triggers an instrument via event_i which will then produce the output at a scheduled time. The UDOs do not contain any k-rate or a-rate variables/ statements. k-rate and a-rate statements appear only in the instruments triggered via the event_i statement.

Since yesterday I start to get PERF errors of the kind:
...
 instrument 13 finished  <<<< this is just signalling that the (last instance of the) calling instrument has been completed.

PERF ERROR in instr 13: CreateSentence: not initialised
istatus	istime	CreateSentence	imode	imodehs	iPan1	2.	5.	0	0	0.	iPitch1	istoptime	0	
   note aborted

Instrument 13 is the instrument calling CreateSentence. It also contains only i-rate variables/statements. From the debugging printout I know that the last instance of instrument 13 has been terminated before the PERF ERROR appears. Furthermore all printouts from CreateSentence 'inside' instr 13 are sensible and complete.

What does it mean when code executed in the initialisation phase only produces PERF ERRORS?

Is there a sensible way for debugging in Csound with setting breakpoints in the csd at k-rate?

I'm running out of ideas. I would grateful for any help

Cheers,

Karin

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

Not initialised means that somehow the init pass for an opcode was skipped. That can happen if you have control of flow in the instr that is skipping at i-time but not at perf-time. Then the init for an opcode might not happen, and when it comes to perform, it fails because of that.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 26 Jun 2016, at 09:11, Karin Daum  wrote:
> 
> Hi,
> 
> I'm heavily using UDOs in my projects about human communication. I'm just extending the existing csd form stereo (with only two voices) to 8 channel. At the same time I increased the number of virtual speakers e.g. 16. 
> 
> All content i.e. the text to be spoken by the virtual speakers the 2-D panning and the time schedule is done at i-rate. The heart is an UDO called 
> 
>         CreateSentence. 
> 
> This calls all UDOs necessary to do the job and finally triggers an instrument via event_i which will then produce the output at a scheduled time. The UDOs do not contain any k-rate or a-rate variables/ statements. k-rate and a-rate statements appear only in the instruments triggered via the event_i statement.
> 
> Since yesterday I start to get PERF errors of the kind:
> ...
> instrument 13 finished  <<<< this is just signalling that the (last instance of the) calling instrument has been completed.
> 
> PERF ERROR in instr 13: CreateSentence: not initialised
> istatus    istime    CreateSentence    imode    imodehs    iPan1    2.    5.    0    0    0.    iPitch1    istoptime    0    
>   note aborted
> 
> Instrument 13 is the instrument calling CreateSentence. It also contains only i-rate variables/statements. From the debugging printout I know that the last instance of instrument 13 has been terminated before the PERF ERROR appears. Furthermore all printouts from CreateSentence 'inside' instr 13 are sensible and complete.
> 
> What does it mean when code executed in the initialisation phase only produces PERF ERRORS?
> 
> Is there a sensible way for debugging in Csound with setting breakpoints in the csd at k-rate?
> 
> I'm running out of ideas. I would grateful for any help
> 
> Cheers,
> 
> Karin
> 
> 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

By the way, if you want only the init time to run on an instr you can try giving it 0 duration. That way it will run the i-time and
then stop.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 26 Jun 2016, at 09:25, Victor Lazzarini  wrote:
> 
> Not initialised means that somehow the init pass for an opcode was skipped. That can happen if you have control of flow in the instr that is skipping at i-time but not at perf-time. Then the init for an opcode might not happen, and when it comes to perform, it fails because of that.
> 
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
> 
>> On 26 Jun 2016, at 09:11, Karin Daum  wrote:
>> 
>> Hi,
>> 
>> I'm heavily using UDOs in my projects about human communication. I'm just extending the existing csd form stereo (with only two voices) to 8 channel. At the same time I increased the number of virtual speakers e.g. 16. 
>> 
>> All content i.e. the text to be spoken by the virtual speakers the 2-D panning and the time schedule is done at i-rate. The heart is an UDO called 
>> 
>>        CreateSentence. 
>> 
>> This calls all UDOs necessary to do the job and finally triggers an instrument via event_i which will then produce the output at a scheduled time. The UDOs do not contain any k-rate or a-rate variables/ statements. k-rate and a-rate statements appear only in the instruments triggered via the event_i statement.
>> 
>> Since yesterday I start to get PERF errors of the kind:
>> ...
>> instrument 13 finished  <<<< this is just signalling that the (last instance of the) calling instrument has been completed.
>> 
>> PERF ERROR in instr 13: CreateSentence: not initialised
>> istatus    istime    CreateSentence    imode    imodehs    iPan1    2.    5.    0    0    0.    iPitch1    istoptime    0    
>>  note aborted
>> 
>> Instrument 13 is the instrument calling CreateSentence. It also contains only i-rate variables/statements. From the debugging printout I know that the last instance of instrument 13 has been terminated before the PERF ERROR appears. Furthermore all printouts from CreateSentence 'inside' instr 13 are sensible and complete.
>> 
>> What does it mean when code executed in the initialisation phase only produces PERF ERRORS?
>> 
>> Is there a sensible way for debugging in Csound with setting breakpoints in the csd at k-rate?
>> 
>> I'm running out of ideas. I would grateful for any help
>> 
>> Cheers,
>> 
>> Karin
>> 
>> 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

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

Thanks a lot, Victor. 

setting the duration to 0 really helps. The perf error is gone and the output (printout and wav) looks reasonable. 

cheers,

Karin
> On 26 Jun 2016, at 10:33, Victor Lazzarini  wrote:
> 
> By the way, if you want only the init time to run on an instr you can try giving it 0 duration. That way it will run the i-time and
> then stop.
> 
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
> 
>> On 26 Jun 2016, at 09:25, Victor Lazzarini  wrote:
>> 
>> Not initialised means that somehow the init pass for an opcode was skipped. That can happen if you have control of flow in the instr that is skipping at i-time but not at perf-time. Then the init for an opcode might not happen, and when it comes to perform, it fails because of that.
>> 
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>> 
>>> On 26 Jun 2016, at 09:11, Karin Daum  wrote:
>>> 
>>> Hi,
>>> 
>>> I'm heavily using UDOs in my projects about human communication. I'm just extending the existing csd form stereo (with only two voices) to 8 channel. At the same time I increased the number of virtual speakers e.g. 16. 
>>> 
>>> All content i.e. the text to be spoken by the virtual speakers the 2-D panning and the time schedule is done at i-rate. The heart is an UDO called 
>>> 
>>>       CreateSentence. 
>>> 
>>> This calls all UDOs necessary to do the job and finally triggers an instrument via event_i which will then produce the output at a scheduled time. The UDOs do not contain any k-rate or a-rate variables/ statements. k-rate and a-rate statements appear only in the instruments triggered via the event_i statement.
>>> 
>>> Since yesterday I start to get PERF errors of the kind:
>>> ...
>>> instrument 13 finished  <<<< this is just signalling that the (last instance of the) calling instrument has been completed.
>>> 
>>> PERF ERROR in instr 13: CreateSentence: not initialised
>>> istatus    istime    CreateSentence    imode    imodehs    iPan1    2.    5.    0    0    0.    iPitch1    istoptime    0    
>>> note aborted
>>> 
>>> Instrument 13 is the instrument calling CreateSentence. It also contains only i-rate variables/statements. From the debugging printout I know that the last instance of instrument 13 has been terminated before the PERF ERROR appears. Furthermore all printouts from CreateSentence 'inside' instr 13 are sensible and complete.
>>> 
>>> What does it mean when code executed in the initialisation phase only produces PERF ERRORS?
>>> 
>>> Is there a sensible way for debugging in Csound with setting breakpoints in the csd at k-rate?
>>> 
>>> I'm running out of ideas. I would grateful for any help
>>> 
>>> Cheers,
>>> 
>>> Karin
>>> 
>>> 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
> 
> 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

Great!
========================
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 26 Jun 2016, at 09:45, Karin Daum  wrote:
> 
> Thanks a lot, Victor. 
> 
> setting the duration to 0 really helps. The perf error is gone and the output (printout and wav) looks reasonable. 
> 
> cheers,
> 
> Karin
>> On 26 Jun 2016, at 10:33, Victor Lazzarini  wrote:
>> 
>> By the way, if you want only the init time to run on an instr you can try giving it 0 duration. That way it will run the i-time and
>> then stop.
>> 
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>> 
>>> On 26 Jun 2016, at 09:25, Victor Lazzarini  wrote:
>>> 
>>> Not initialised means that somehow the init pass for an opcode was skipped. That can happen if you have control of flow in the instr that is skipping at i-time but not at perf-time. Then the init for an opcode might not happen, and when it comes to perform, it fails because of that.
>>> 
>>> Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy
>>> Maynooth University
>>> Ireland
>>> 
>>>> On 26 Jun 2016, at 09:11, Karin Daum  wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> I'm heavily using UDOs in my projects about human communication. I'm just extending the existing csd form stereo (with only two voices) to 8 channel. At the same time I increased the number of virtual speakers e.g. 16. 
>>>> 
>>>> All content i.e. the text to be spoken by the virtual speakers the 2-D panning and the time schedule is done at i-rate. The heart is an UDO called 
>>>> 
>>>>      CreateSentence. 
>>>> 
>>>> This calls all UDOs necessary to do the job and finally triggers an instrument via event_i which will then produce the output at a scheduled time. The UDOs do not contain any k-rate or a-rate variables/ statements. k-rate and a-rate statements appear only in the instruments triggered via the event_i statement.
>>>> 
>>>> Since yesterday I start to get PERF errors of the kind:
>>>> ...
>>>> instrument 13 finished  <<<< this is just signalling that the (last instance of the) calling instrument has been completed.
>>>> 
>>>> PERF ERROR in instr 13: CreateSentence: not initialised
>>>> istatus    istime    CreateSentence    imode    imodehs    iPan1    2.    5.    0    0    0.    iPitch1    istoptime    0    
>>>> note aborted
>>>> 
>>>> Instrument 13 is the instrument calling CreateSentence. It also contains only i-rate variables/statements. From the debugging printout I know that the last instance of instrument 13 has been terminated before the PERF ERROR appears. Furthermore all printouts from CreateSentence 'inside' instr 13 are sensible and complete.
>>>> 
>>>> What does it mean when code executed in the initialisation phase only produces PERF ERRORS?
>>>> 
>>>> Is there a sensible way for debugging in Csound with setting breakpoints in the csd at k-rate?
>>>> 
>>>> I'm running out of ideas. I would grateful for any help
>>>> 
>>>> Cheers,
>>>> 
>>>> Karin
>>>> 
>>>> 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
>> 
>> 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

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