[Csnd] expseg
Date | 2010-02-16 07:04 |
From | Enrico de Trizio |
Subject | [Csnd] expseg |
Hope is not too dumb: why expseg keeps rising (or falling) after the last value? Thanks, Enrico ^_^ ps. I would have asked to Dr. B. but you guys are faster :D :D :D late night humor : / Send bugs reports to this list. To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" |
Date | 2010-02-16 07:16 |
From | jpff@cs.bath.ac.uk |
Subject | [Csnd] Re: expseg |
> Hope is not too dumb: why expseg keeps rising (or falling) after the > last value? > > Thanks, Enrico ^_^ > > Because that is what it does! We have discussed this endlessly in the past, but the linseg/expseg/transeg will continue the last segment if the time exceeds the perscription. ==John ff Send bugs reports to this list. To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" |
Date | 2010-02-16 10:47 |
From | joachim heintz |
Subject | [Csnd] Re: Re: expseg |
I understood Enrico said that expseg does NOT continue the last segment (as it should). I think he's right and there is a bug in expseg. Please check: instr 1 klin linseg 1, 1, 2 ktran transeg 1, 1, 1, 2 kexp expseg 1, 1, 2 printks "klin = %f%nktrans = %f%nkexp = %f%n", .5, klin, ktran, kexp endin returns for 3 seconds: klin = 1.000000 ktrans = 1.000000 kexp = 1.000000 klin = 1.499726 ktrans = 1.377112 kexp = 1.414140 klin = 1.999763 ktrans = 1.999218 kexp = 2.000110 klin = 2.000000 ktrans = 2.000000 kexp = 2.828882 klin = 2.000000 ktrans = 2.000000 kexp = 4.001068 klin = 2.000000 ktrans = 2.000000 kexp = 5.658972 klin = 2.000000 ktrans = 2.000000 kexp = 8.003851 joachim Am 16.02.2010 um 08:16 schrieb jpff@cs.bath.ac.uk: >> Hope is not too dumb: why expseg keeps rising (or falling) after the >> last value? >> >> Thanks, Enrico ^_^ >> >> > > Because that is what it does! We have discussed this endlessly in the > past, but the linseg/expseg/transeg will continue the last segment > if the > time exceeds the perscription. > > ==John ff > > > > 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" |
Date | 2010-02-16 12:00 |
From | Aidan Collins |
Subject | [Csnd] Re: Re: Re: expseg |
I believe the line opcode is the one we have frequent discussions about, the 'seg' opcodes should stop shouldn't they? On Tue, Feb 16, 2010 at 5:47 AM, joachim heintz |
Date | 2010-02-19 23:34 |
From | moko@city-net.com |
Subject | [Csnd] Re: expseg |
Is the envelope as long as idur (p3)? If not, add another segment to hold the value. Eg, if p3 = 10 secs and you use expseg to change a value over the first second, try this: kenv expseg 0.001,1,1,9,1 You might also take a look at transeg, a much more flexible envelope that lets you change the slope of the exponential curve. --David > Hope is not too dumb: why expseg keeps rising (or falling) after the > last value? > > Thanks, Enrico ^_^ > > > ps. I would have asked to Dr. B. but you guys are faster :D :D :D > late night humor : / > > > > Send bugs reports to this list. > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe > csound" > |
Date | 2010-02-19 23:37 |
From | Michael Gogins |
Subject | [Csnd] Re: Re: expseg |
Yes, and in general, when you go to use an opcode, check the manual first to see if there's a better one for the job. MKG from cell phone On Feb 19, 2010 6:33 PM, <moko@city-net.com> wrote: |