I know you get the "r" envelope opcodes (like linsegr and transegr)
that include a release section, but if I want to make a sound that
plays for a fixed duration, no matter how long the score statement
says the note duration is, how do I do that? My experiments with the
release opcodes haven't worked, as the note stays on until the
release.

Is there an envelope opcode that extends the note duration if the
envelope overlaps, rather than just adding a release section?

I'll make what I mean clearer with a hideous example. I want instr 1
to always play for 0.5 seconds:



-odac -dm3 --expression-opt --sample-accurate



sr = 48000
ksmps = 100
nchnls = 1
0dbfs = 1.0

gif1 ftgen 0, 0, 64, 9, 1, 0.6, 4, 0.5, 5, 0.3

instr 1
aenv1 linseg 1, 0.5, 0
aosc1 oscili aenv1, p4, gif1
out aosc1
endin




r 128
t 0 180
i1 0 0.2 200
i1 + 0.2 300
i1 + 1.0 400
i1 + 0.5 500
i1 + 0.3 600




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

Well... boy do I feel silly! :D Lol, that's pretty darn simple, nice
work csound dev team!

On Sun, Jan 3, 2016 at 3:48 PM, Rory Walsh  wrote:
> You can override the duration by setting p3 in your instrument, ala
>
> p3=.5
>
>
> On 3 January 2016 at 15:43, Peter Burgess 
> wrote:
>>
>> I know you get the "r" envelope opcodes (like linsegr and transegr)
>> that include a release section, but if I want to make a sound that
>> plays for a fixed duration, no matter how long the score statement
>> says the note duration is, how do I do that? My experiments with the
>> release opcodes haven't worked, as the note stays on until the
>> release.
>>
>> Is there an envelope opcode that extends the note duration if the
>> envelope overlaps, rather than just adding a release section?
>>
>> I'll make what I mean clearer with a hideous example. I want instr 1
>> to always play for 0.5 seconds:
>>
>> 
>> 
>> -odac -dm3 --expression-opt --sample-accurate
>> 
>> 
>>
>> sr = 48000
>> ksmps = 100
>> nchnls = 1
>> 0dbfs = 1.0
>>
>> gif1 ftgen 0, 0, 64, 9, 1, 0.6, 4, 0.5, 5, 0.3
>>
>> instr 1
>> aenv1 linseg 1, 0.5, 0
>> aosc1 oscili aenv1, p4, gif1
>> out aosc1
>> endin
>>
>> 
>> 
>>
>> r 128
>> t 0 180
>> i1 0 0.2 200
>> i1 + 0.2 300
>> i1 + 1.0 400
>> i1 + 0.5 500
>> i1 + 0.3 600
>>
>> 
>> 
>>
>> 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

Lol! I didn't follow that thread to the end, it's a year of smooth
manoeuvres ahead

On Sun, Jan 3, 2016 at 3:55 PM, Rory Walsh  wrote:
> Oh I wouldn't worry about feeling silly. Have you not been following the
> thread on array outputs to opcodes?! I just sent the dev team on a wild
> goose chase over nothing but an oversight on my part!! Yikes. Beers owed
> count is increasing exponentially these days!
>
> On 3 January 2016 at 15:50, Peter Burgess 
> wrote:
>>
>> Well... boy do I feel silly! :D Lol, that's pretty darn simple, nice
>> work csound dev team!
>>
>> On Sun, Jan 3, 2016 at 3:48 PM, Rory Walsh  wrote:
>> > You can override the duration by setting p3 in your instrument, ala
>> >
>> > p3=.5
>> >
>> >
>> > On 3 January 2016 at 15:43, Peter Burgess
>> > 
>> > wrote:
>> >>
>> >> I know you get the "r" envelope opcodes (like linsegr and transegr)
>> >> that include a release section, but if I want to make a sound that
>> >> plays for a fixed duration, no matter how long the score statement
>> >> says the note duration is, how do I do that? My experiments with the
>> >> release opcodes haven't worked, as the note stays on until the
>> >> release.
>> >>
>> >> Is there an envelope opcode that extends the note duration if the
>> >> envelope overlaps, rather than just adding a release section?
>> >>
>> >> I'll make what I mean clearer with a hideous example. I want instr 1
>> >> to always play for 0.5 seconds:
>> >>
>> >> 
>> >> 
>> >> -odac -dm3 --expression-opt --sample-accurate
>> >> 
>> >> 
>> >>
>> >> sr = 48000
>> >> ksmps = 100
>> >> nchnls = 1
>> >> 0dbfs = 1.0
>> >>
>> >> gif1 ftgen 0, 0, 64, 9, 1, 0.6, 4, 0.5, 5, 0.3
>> >>
>> >> instr 1
>> >> aenv1 linseg 1, 0.5, 0
>> >> aosc1 oscili aenv1, p4, gif1
>> >> out aosc1
>> >> endin
>> >>
>> >> 
>> >> 
>> >>
>> >> r 128
>> >> t 0 180
>> >> i1 0 0.2 200
>> >> i1 + 0.2 300
>> >> i1 + 1.0 400
>> >> i1 + 0.5 500
>> >> i1 + 0.3 600
>> >>
>> >> 
>> >> 
>> >>
>> >> 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

Yeah, I'm quite comfortable with taking one for the team like that :D

On Sun, Jan 3, 2016 at 4:04 PM, Rory Walsh  wrote:
> It's good that some of us are here to remind the rest of the members that
> it's Ok to make complete tools of ourselves from time to time!
>
> On 3 January 2016 at 15:59, Peter Burgess 
> wrote:
>>
>> Lol! I didn't follow that thread to the end, it's a year of smooth
>> manoeuvres ahead
>>
>> On Sun, Jan 3, 2016 at 3:55 PM, Rory Walsh  wrote:
>> > Oh I wouldn't worry about feeling silly. Have you not been following the
>> > thread on array outputs to opcodes?! I just sent the dev team on a wild
>> > goose chase over nothing but an oversight on my part!! Yikes. Beers owed
>> > count is increasing exponentially these days!
>> >
>> > On 3 January 2016 at 15:50, Peter Burgess
>> > 
>> > wrote:
>> >>
>> >> Well... boy do I feel silly! :D Lol, that's pretty darn simple, nice
>> >> work csound dev team!
>> >>
>> >> On Sun, Jan 3, 2016 at 3:48 PM, Rory Walsh  wrote:
>> >> > You can override the duration by setting p3 in your instrument, ala
>> >> >
>> >> > p3=.5
>> >> >
>> >> >
>> >> > On 3 January 2016 at 15:43, Peter Burgess
>> >> > 
>> >> > wrote:
>> >> >>
>> >> >> I know you get the "r" envelope opcodes (like linsegr and transegr)
>> >> >> that include a release section, but if I want to make a sound that
>> >> >> plays for a fixed duration, no matter how long the score statement
>> >> >> says the note duration is, how do I do that? My experiments with the
>> >> >> release opcodes haven't worked, as the note stays on until the
>> >> >> release.
>> >> >>
>> >> >> Is there an envelope opcode that extends the note duration if the
>> >> >> envelope overlaps, rather than just adding a release section?
>> >> >>
>> >> >> I'll make what I mean clearer with a hideous example. I want instr 1
>> >> >> to always play for 0.5 seconds:
>> >> >>
>> >> >> 
>> >> >> 
>> >> >> -odac -dm3 --expression-opt --sample-accurate
>> >> >> 
>> >> >> 
>> >> >>
>> >> >> sr = 48000
>> >> >> ksmps = 100
>> >> >> nchnls = 1
>> >> >> 0dbfs = 1.0
>> >> >>
>> >> >> gif1 ftgen 0, 0, 64, 9, 1, 0.6, 4, 0.5, 5, 0.3
>> >> >>
>> >> >> instr 1
>> >> >> aenv1 linseg 1, 0.5, 0
>> >> >> aosc1 oscili aenv1, p4, gif1
>> >> >> out aosc1
>> >> >> endin
>> >> >>
>> >> >> 
>> >> >> 
>> >> >>
>> >> >> r 128
>> >> >> t 0 180
>> >> >> i1 0 0.2 200
>> >> >> i1 + 0.2 300
>> >> >> i1 + 1.0 400
>> >> >> i1 + 0.5 500
>> >> >> i1 + 0.3 600
>> >> >>
>> >> >> 
>> >> >> 
>> >> >>
>> >> >> 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
>
>
> 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

In your instrument definition assign the duration you want to p3.

Regards,
Mike

Yeah rory already put me straight on that, i should of thought to try
that already really :D cheers all the same though mike. The score and
the orchestra feel very separate in my head, so it didn't occur to me
that I could actually alter the p fields from the orchestra.

This simple fact has opened up a whole world of possibilities that I
thought originally would be awkward to implement

On Sun, Jan 3, 2016 at 5:12 PM, Michael Gogins  wrote:
> In your instrument definition assign the duration you want to p3.
>
> Regards,
> Mike
>
> On Jan 3, 2016 10:43 AM, "Peter Burgess" 
> wrote:
>>
>> I know you get the "r" envelope opcodes (like linsegr and transegr)
>> that include a release section, but if I want to make a sound that
>> plays for a fixed duration, no matter how long the score statement
>> says the note duration is, how do I do that? My experiments with the
>> release opcodes haven't worked, as the note stays on until the
>> release.
>>
>> Is there an envelope opcode that extends the note duration if the
>> envelope overlaps, rather than just adding a release section?
>>
>> I'll make what I mean clearer with a hideous example. I want instr 1
>> to always play for 0.5 seconds:
>>
>> 
>> 
>> -odac -dm3 --expression-opt --sample-accurate
>> 
>> 
>>
>> sr = 48000
>> ksmps = 100
>> nchnls = 1
>> 0dbfs = 1.0
>>
>> gif1 ftgen 0, 0, 64, 9, 1, 0.6, 4, 0.5, 5, 0.3
>>
>> instr 1
>> aenv1 linseg 1, 0.5, 0
>> aosc1 oscili aenv1, p4, gif1
>> out aosc1
>> endin
>>
>> 
>> 
>>
>> r 128
>> t 0 180
>> i1 0 0.2 200
>> i1 + 0.2 300
>> i1 + 1.0 400
>> i1 + 0.5 500
>> i1 + 0.3 600
>>
>> 
>> 
>>
>> 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