I've an opcode that rearrange a schedule in my terms:

    opcode    eva_midi, 0, Siiiii
Sinstr, iwhen, idur, iamp, ienv, icps xin

if    idur > giminnote && iamp > 0 then

    if    (icps != 0) then
        ich        init 1
        until ich > ginchnls do
            schedule    Sinstr, iwhen, idur, iamp, ienv, icps, ich
            ich += 1
        od
    endif

endif
    endop

and when I make a csd with some code inside like this:

eva_midi "orphans4", 0, 2, 0.5, giiago, 440 

I get this message:

WARNING: eva_midi: perf-time code in global space, ignored

At the end in the wav I render it seems that everything is fine.
I do not understand where's the problem/error? Am i doing something in the wrong way? Is it always better to put all schedules inside an instrument?

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

User defined opcodes are not pure init time blocks, even if there is 
nothing left for them to do after the init pass. By putting an opcode at 
the instr0 level you are placing performance code where it is not 
allowed. You can place bare "schedule" calls within the global space but 
a user-defined opcode needs to be called from within an instrument.

On 08.06.23 12:35, C œurdelia wrote:
> I've an opcode that rearrange a schedule in my terms:
>
>      opcode    eva_midi, 0, Siiiii
> Sinstr, iwhen, idur, iamp, ienv, icps xin
>
> if    idur > giminnote && iamp > 0 then
>
>      if    (icps != 0) then
>          ich        init 1
>          until ich > ginchnls do
>              schedule    Sinstr, iwhen, idur, iamp, ienv, icps, ich
>              ich += 1
>          od
>      endif
>
> endif
>      endop
>
> and when I make a csd with some code inside like this:
>
> eva_midi "orphans4", 0, 2, 0.5, giiago, 440
>
> I get this message:
>
> WARNING: eva_midi: perf-time code in global space, ignored
>
> At the end in the wav I render it seems that everything is fine.
> I do not understand where's the problem/error? Am i doing something in the wrong way? Is it always better to put all schedules inside an instrument?
>
> 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

I think you can safely ignore those warnings. All they say is that if you expected the code to run at
perf time, that won’t happen. But if you did, then there’s an issue.
========================
Prof. Victor Lazzarini
Maynooth University
Ireland

> On 9 Jun 2023, at 08:01, Cordelia <00000c641a512f08-dmarc-request@LISTSERV.HEANET.IE> wrote:
> 
> WARNINGThis email originated from outside of Maynooth University's Mail System. Do not reply, click links or open attachments unless you recognise the sender and know the content is safe.
> Thank you for your answer.
> 
> What I don’t understand is if it’s a suggestion or a “good practice”. 
> How this message impact performance or sound? As I said, csound says “ignored”, but at the end it compile the schedules.
> Thank you.
> 
> 
> 
>> On 8 Jun 2023, at 12:41, Eduardo Moguillansky  wrote:
>> 
>> User defined opcodes are not pure init time blocks, even if there is nothing left for them to do after the init pass. By putting an opcode at the instr0 level you are placing performance code where it is not allowed. You can place bare "schedule" calls within the global space but a user-defined opcode needs to be called from within an instrument.
>> 
>> On 08.06.23 12:35, C œurdelia wrote:
>>> I've an opcode that rearrange a schedule in my terms:
>>> 
>>>     opcode    eva_midi, 0, Siiiii
>>> Sinstr, iwhen, idur, iamp, ienv, icps xin
>>> 
>>> if    idur > giminnote && iamp > 0 then
>>> 
>>>     if    (icps != 0) then
>>>         ich        init 1
>>>         until ich > ginchnls do
>>>             schedule    Sinstr, iwhen, idur, iamp, ienv, icps, ich
>>>             ich += 1
>>>         od
>>>     endif
>>> 
>>> endif
>>>     endop
>>> 
>>> and when I make a csd with some code inside like this:
>>> 
>>> eva_midi "orphans4", 0, 2, 0.5, giiago, 440
>>> 
>>> I get this message:
>>> 
>>> WARNING: eva_midi: perf-time code in global space, ignored
>>> 
>>> At the end in the wav I render it seems that everything is fine.
>>> I do not understand where's the problem/error? Am i doing something in the wrong way? Is it always better to put all schedules inside an instrument?
>>> 
>>> 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