Hi All,

I'm thinking of a change to allow instruments of infinite duration.
The idea would be to have something like this:

i1 0 x 0 1 2 3 4 5
i2 0 x 0 1 2 3 4 5

where the x would denote that this instrument instance is meant to be
infinite in duration.  There would be a change to the engine then to
have a flag on the instrument instance and to keep running while
either there is no more score as well as no more instrument instances
with unending duration.  This seems like it would be useful for
projects that are going to be run more like an application (i.e. a
QuteCsound project) or any kind of long running installation.

As far as I'm aware, the only way to specify long running projects up
until now has been to use a really long duration.  This has worked but
has always seemed strange to me to look at "i1 0 336000000 1 2 3 4 5"
or something like that.

Any thoughts?  Suggestions for better syntax than 'x'?  Or perhaps is
this altogether unnecessary?

Thanks!
steven


Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi Mr. Steven,
just because i need to understand ...

Could You not use ihold opcode?

I'm not sure, but is it not same thing?

Thanks,
ciao,
fran.



Steven Yi wrote:
> 
> Hi All,
> 
> I'm thinking of a change to allow instruments of infinite duration.
> The idea would be to have something like this:
> 
> i1 0 x 0 1 2 3 4 5
> i2 0 x 0 1 2 3 4 5
> 
> where the x would denote that this instrument instance is meant to be
> infinite in duration.  There would be a change to the engine then to
> have a flag on the instrument instance and to keep running while
> either there is no more score as well as no more instrument instances
> with unending duration.  This seems like it would be useful for
> projects that are going to be run more like an application (i.e. a
> QuteCsound project) or any kind of long running installation.
> 
> As far as I'm aware, the only way to specify long running projects up
> until now has been to use a really long duration.  This has worked but
> has always seemed strange to me to look at "i1 0 336000000 1 2 3 4 5"
> or something like that.
> 
> Any thoughts?  Suggestions for better syntax than 'x'?  Or perhaps is
> this altogether unnecessary?
> 
> Thanks!
> steven
> 
> 
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
> 
> 

-1 duration in the score is indefinite.

alwayson opcode in the orchestra header is indefinite.

Regards,
Mike

On Fri, Jan 22, 2010 at 10:49 PM, Steven Yi  wrote:
> Hi All,
>
> I'm thinking of a change to allow instruments of infinite duration.
> The idea would be to have something like this:
>
> i1 0 x 0 1 2 3 4 5
> i2 0 x 0 1 2 3 4 5
>
> where the x would denote that this instrument instance is meant to be
> infinite in duration.  There would be a change to the engine then to
> have a flag on the instrument instance and to keep running while
> either there is no more score as well as no more instrument instances
> with unending duration.  This seems like it would be useful for
> projects that are going to be run more like an application (i.e. a
> QuteCsound project) or any kind of long running installation.
>
> As far as I'm aware, the only way to specify long running projects up
> until now has been to use a really long duration.  This has worked but
> has always seemed strange to me to look at "i1 0 336000000 1 2 3 4 5"
> or something like that.
>
> Any thoughts?  Suggestions for better syntax than 'x'?  Or perhaps is
> this altogether unnecessary?
>
> Thanks!
> steven
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com


Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"