Csound Csound-dev Csound-tekno Search About

[Csnd] Question about delay opcodes

Date2012-08-21 03:26
FromTakahiko Tsuchiya
Subject[Csnd] Question about delay opcodes
Hello all,

I have a question about the delayr / deltap / delayw opcodes. If I’m not misunderstanding too much, the delayr allocates a buffer to store some signal, the deltap delays and outputs the stored signal, and the delayw writes some signal into the buffer. Question is - what is the delayr actually “reading”? And from where? To me, the deltap seems to be the one reading from the delay buffer...

Takahiko

Date2012-08-21 03:34
FromDeepak
SubjectRe: [Csnd] Question about delay opcodes
I had thought that delayr reads from the end of the buffer....
when we use delayr and delayw in conjunction, we define the buffer using delayr, for eg:
aOut delayr 0.3; defines a 0.3 sec long buffer
 and then we can have :

delayw aSig

and if we have
 aOutFinal = aSig + aOut*feedback, the delay time would be 0.3....

with deltap we can tap at any point in the buffer..., there by having more control as to where you want to read it from...

This is what I have understood..I remember reading the FLOSS manuals being helpful on this topic...had read it a while ago though...

Thanks
Deepak...


On Mon, Aug 20, 2012 at 10:26 PM, Takahiko Tsuchiya <turbo@f.email.ne.jp> wrote:
Hello all,

I have a question about the delayr / deltap / delayw opcodes. If I’m not misunderstanding too much, the delayr allocates a buffer to store some signal, the deltap delays and outputs the stored signal, and the delayw writes some signal into the buffer. Question is - what is the delayr actually “reading”? And from where? To me, the deltap seems to be the one reading from the delay buffer...

Takahiko



--
www.myspace.com/dcompanymusic
www.myspace.com/thewoodshedmusicians

Date2012-08-21 03:45
FromJustin Smith
SubjectRe: [Csnd] Question about delay opcodes
Yeah: once upon a time there was no such thing as deltap, so you just
had delayr followed by delayw, and the delayr read silence first then
eventually the output of the delayw. Deltap changes this by being able
to have any additional delay between ksmps/sr seconds as the minimum
and the position of the fixed delayr as the maximum.

On Mon, Aug 20, 2012 at 7:34 PM, Deepak  wrote:
> I had thought that delayr reads from the end of the buffer....
> when we use delayr and delayw in conjunction, we define the buffer using
> delayr, for eg:
> aOut delayr 0.3; defines a 0.3 sec long buffer
>  and then we can have :
>
> delayw aSig
>
> and if we have
>  aOutFinal = aSig + aOut*feedback, the delay time would be 0.3....
>
> with deltap we can tap at any point in the buffer..., there by having more
> control as to where you want to read it from...
>
> This is what I have understood..I remember reading the FLOSS manuals being
> helpful on this topic...had read it a while ago though...
>
> Thanks
> Deepak...
>
>
>
> On Mon, Aug 20, 2012 at 10:26 PM, Takahiko Tsuchiya 
> wrote:
>>
>> Hello all,
>>
>> I have a question about the delayr / deltap / delayw opcodes. If I’m not
>> misunderstanding too much, the delayr allocates a buffer to store some
>> signal, the deltap delays and outputs the stored signal, and the delayw
>> writes some signal into the buffer. Question is - what is the delayr
>> actually “reading”? And from where? To me, the deltap seems to be the one
>> reading from the delay buffer...
>>
>> Takahiko
>
>
>
>
> --
> www.myspace.com/dcompanymusic
> www.myspace.com/thewoodshedmusicians


Date2012-08-21 04:09
FromTakahiko Tsuchiya
SubjectRe: [Csnd] Question about delay opcodes
Thanks Deepak for the quick answer. I misunderstood like the delayr was solely for creating a temp buffer. Reading the floss manual page now! (http://en.flossmanuals.net/csound/d-delay-and-feedback/)

Takahiko


On Mon, Aug 20, 2012 at 10:34 PM, Deepak <musicmagic@gmail.com> wrote:
I had thought that delayr reads from the end of the buffer....
when we use delayr and delayw in conjunction, we define the buffer using delayr, for eg:
aOut delayr 0.3; defines a 0.3 sec long buffer
 and then we can have :

delayw aSig

and if we have
 aOutFinal = aSig + aOut*feedback, the delay time would be 0.3....

with deltap we can tap at any point in the buffer..., there by having more control as to where you want to read it from...

This is what I have understood..I remember reading the FLOSS manuals being helpful on this topic...had read it a while ago though...

Thanks
Deepak...



On Mon, Aug 20, 2012 at 10:26 PM, Takahiko Tsuchiya <turbo@f.email.ne.jp> wrote:
Hello all,

I have a question about the delayr / deltap / delayw opcodes. If I’m not misunderstanding too much, the delayr allocates a buffer to store some signal, the deltap delays and outputs the stored signal, and the delayw writes some signal into the buffer. Question is - what is the delayr actually “reading”? And from where? To me, the deltap seems to be the one reading from the delay buffer...

Takahiko



--
www.myspace.com/dcompanymusic
www.myspace.com/thewoodshedmusicians


Date2012-08-21 04:10
From"Dr. Richard Boulanger"
SubjectRe: [Csnd] Question about delay opcodes
also - remember to read the Pinkston chapter in The Csound Book.

-dB
___________________________________

Dr. Richard Boulanger, Ph.D.

Professor of Electronic Production and Design
Professional Writing and Music Technology Division
Berklee College of Music
1140 Boylston Street
Boston, MA 02215-3693

617-747-2485 (office)
774-488-9166 (cell)


____________________________________



____________________________________

____________________________________

On Aug 20, 2012, at 11:09 PM, Takahiko Tsuchiya <turbo@f.email.ne.jp> wrote:

Thanks Deepak for the quick answer. I misunderstood like the delayr was solely for creating a temp buffer. Reading the floss manual page now! (http://en.flossmanuals.net/csound/d-delay-and-feedback/)

Takahiko


On Mon, Aug 20, 2012 at 10:34 PM, Deepak <musicmagic@gmail.com> wrote:
I had thought that delayr reads from the end of the buffer....
when we use delayr and delayw in conjunction, we define the buffer using delayr, for eg:
aOut delayr 0.3; defines a 0.3 sec long buffer
 and then we can have :

delayw aSig

and if we have
 aOutFinal = aSig + aOut*feedback, the delay time would be 0.3....

with deltap we can tap at any point in the buffer..., there by having more control as to where you want to read it from...

This is what I have understood..I remember reading the FLOSS manuals being helpful on this topic...had read it a while ago though...

Thanks
Deepak...



On Mon, Aug 20, 2012 at 10:26 PM, Takahiko Tsuchiya <turbo@f.email.ne.jp> wrote:
Hello all,

I have a question about the delayr / deltap / delayw opcodes. If I’m not misunderstanding too much, the delayr allocates a buffer to store some signal, the deltap delays and outputs the stored signal, and the delayw writes some signal into the buffer. Question is - what is the delayr actually “reading”? And from where? To me, the deltap seems to be the one reading from the delay buffer...

Takahiko



--
www.myspace.com/dcompanymusic
www.myspace.com/thewoodshedmusicians



Date2012-08-21 04:45
FromTakahiko Tsuchiya
SubjectRe: [Csnd] Question about delay opcodes
Thanks Justin, it's getting clearer.

Dr. B, I read the chapter roughly before asking this question, but I will go back to it. Thanks.

Takahiko


On Mon, Aug 20, 2012 at 11:10 PM, Dr. Richard Boulanger <rboulanger@berklee.edu> wrote:
also - remember to read the Pinkston chapter in The Csound Book.

-dB
___________________________________

Dr. Richard Boulanger, Ph.D.

Professor of Electronic Production and Design
Professional Writing and Music Technology Division
Berklee College of Music
1140 Boylston Street
Boston, MA 02215-3693

617-747-2485 (office)
774-488-9166 (cell)


____________________________________



____________________________________

____________________________________

On Aug 20, 2012, at 11:09 PM, Takahiko Tsuchiya <turbo@f.email.ne.jp> wrote:

Thanks Deepak for the quick answer. I misunderstood like the delayr was solely for creating a temp buffer. Reading the floss manual page now! (http://en.flossmanuals.net/csound/d-delay-and-feedback/)

Takahiko


On Mon, Aug 20, 2012 at 10:34 PM, Deepak <musicmagic@gmail.com> wrote:
I had thought that delayr reads from the end of the buffer....
when we use delayr and delayw in conjunction, we define the buffer using delayr, for eg:
aOut delayr 0.3; defines a 0.3 sec long buffer
 and then we can have :

delayw aSig

and if we have
 aOutFinal = aSig + aOut*feedback, the delay time would be 0.3....

with deltap we can tap at any point in the buffer..., there by having more control as to where you want to read it from...

This is what I have understood..I remember reading the FLOSS manuals being helpful on this topic...had read it a while ago though...

Thanks
Deepak...



On Mon, Aug 20, 2012 at 10:26 PM, Takahiko Tsuchiya <turbo@f.email.ne.jp> wrote:
Hello all,

I have a question about the delayr / deltap / delayw opcodes. If I’m not misunderstanding too much, the delayr allocates a buffer to store some signal, the deltap delays and outputs the stored signal, and the delayw writes some signal into the buffer. Question is - what is the delayr actually “reading”? And from where? To me, the deltap seems to be the one reading from the delay buffer...

Takahiko



--
www.myspace.com/dcompanymusic
www.myspace.com/thewoodshedmusicians