Why not have an instrument doing nothing else that every now and than turn on 
another instance of itself that turn off the previous instance to keep csound 
alive?


>----Messaggio originale----
>Da: stevenyi@gmail.com
>Data: 23/01/2010 17.40
>A: 
>Ogg: [Csnd] Re: Re: Re: R: Re: Infinite Duration Proposal
>
>Yes, large durations work, but in my mind it's a workaround to a
>problem and not a real solution.  The motivation behind all this is
>two-fold, one the idea of long-running installations (i.e. more than a
>year) and two, that from the perspective of a developer using an audio
>engine, I am thinking that there should be ways to make the engine run
>and have active instances of instruments without need for scheduling,
>just turn on an instrument.
>
>It seems that there is no direct solution currently and only the
>long-duration workaround.  I am going to do some investigation of the
>engine sometime in the next couple of weeks to see how exactly
>everything works.  I'll also write back here before I do any coding on
>this if I do end up spending the time on it.
>
>Thanks everyone for your replies!
>steven
>
>On Sat, Jan 23, 2010 at 11:13 AM, Victor Lazzarini
> wrote:
>> What about  f0  with a very large duration?
>>
>> On 23 Jan 2010, at 15:28, Steven Yi wrote:
>>
>>> Hi All,
>>>
>>> I already knew about both ihold and negative duration and neither
>>> works.  I looked at the source code of the alwayson opcode and all it
>>> does is use -1 for duration.  I have attached examples that use ihold
>>> and negative duration as well as a normal running project.
>>>
>>> As far as I understand, held notes are only held for the duration of a
>>> score.  If the only notes are held, the score duration is considered 0
>>> and csound immediately turns off the project (as far as I understand).
>>> This is why I implied changing the engine to change its exit
>>> criteria.
>>>
>>> So, unless there's some other way I'm unaware of, there is still no
>>> other way except to specify a very long duration for a project.
>>>
>>> steven
>>>
>>> On Sat, Jan 23, 2010 at 8:47 AM, vallste@libero.it 
>>> wrote:
>>>>
>>>> Why not creating a "f 0 -1"?
>>>>
>>>> Maybe it has been already discussed... in this case sorry for this
>>>> question...
>>>>
>>>>> ----Messaggio originale----
>>>>> Da: michael.gogins@gmail.com
>>>>> Data: 23/01/2010 12.55
>>>>> A: 
>>>>> Ogg: [Csnd] Re: Infinite Duration Proposal
>>>>>
>>>>> -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"
>>>>
>>>>
>>>>
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>
>Send bugs reports to this list.
>To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
csound"




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