fixed in CVS. The delay line was only being 1/2 zeroed, because
its size was assumed to be in int32 not MYFLT (ie double) items.
----- Original Message ----- 
From: "victor" 
To: 
Sent: Friday, November 07, 2008 10:57 PM
Subject: [Csnd] Re: Delay opcode broken?


> looking at this now. I can see the problem you report, but the code
> is correct in terms of delay buffersize etc. The read pointer seems to
> be going all the way to the end of the buffer, too. It is hard to find
> where the problem lies. It is as if the buffer is being written at the
> 1/2-way point.
> ----- Original Message ----- 
> From: "Djack" 
> To: 
> Sent: Friday, November 07, 2008 6:51 PM
> Subject: [Csnd] Delay opcode broken?
>
>
>>
>> Hello all,
>>
>> When i test the delay.csd included in html documentation/examples i note 
>> the
>> following:
>>
>> The first line i1 0.0 0.2 gives a correct time delay of 0.10 sec between
>> beep and delayed beep
>> The second line i1 0.5 0.2 gives a wrong time delay of 0.05 sec between 
>> beep
>> and delayed beep
>>
>> This behaviour is only with csound double, this do not append with csound
>> float.
>>
>> I use csound5.09 from cvs 01Nov08 on Ubuntu Hardy 8.04 kernel linux
>> 2.6.24-21-rt.
>>
>> http://www.nabble.com/file/p20386726/delay.csd delay.csd
>>
>> Best regards
>> Rene Poggi
>> -- 
>> View this message in context: 
>> http://www.nabble.com/Delay-opcode-broken--tp20386726p20386726.html
>> Sent from the Csound - General mailing list archive at Nabble.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" 

It is ok now.
Tanks
René



Victor Lazzarini wrote:
> 
> fixed in CVS. The delay line was only being 1/2 zeroed, because
> its size was assumed to be in int32 not MYFLT (ie double) items.
> ----- Original Message ----- 
> From: "victor" 
> To: 
> Sent: Friday, November 07, 2008 10:57 PM
> Subject: [Csnd] Re: Delay opcode broken?
> 
> 
>> looking at this now. I can see the problem you report, but the code
>> is correct in terms of delay buffersize etc. The read pointer seems to
>> be going all the way to the end of the buffer, too. It is hard to find
>> where the problem lies. It is as if the buffer is being written at the
>> 1/2-way point.
>> ----- Original Message ----- 
>> From: "Djack" 
>> To: 
>> Sent: Friday, November 07, 2008 6:51 PM
>> Subject: [Csnd] Delay opcode broken?
>>
>>
>>>
>>> Hello all,
>>>
>>> When i test the delay.csd included in html documentation/examples i note 
>>> the
>>> following:
>>>
>>> The first line i1 0.0 0.2 gives a correct time delay of 0.10 sec between
>>> beep and delayed beep
>>> The second line i1 0.5 0.2 gives a wrong time delay of 0.05 sec between 
>>> beep
>>> and delayed beep
>>>
>>> This behaviour is only with csound double, this do not append with
>>> csound
>>> float.
>>>
>>> I use csound5.09 from cvs 01Nov08 on Ubuntu Hardy 8.04 kernel linux
>>> 2.6.24-21-rt.
>>>
>>> http://www.nabble.com/file/p20386726/delay.csd delay.csd
>>>
>>> Best regards
>>> Rene Poggi
>>> -- 
>>> View this message in context: 
>>> http://www.nabble.com/Delay-opcode-broken--tp20386726p20386726.html
>>> Sent from the Csound - General mailing list archive at Nabble.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"
> 
> 

-- 
View this message in context: http://www.nabble.com/Delay-opcode-broken--tp20386726p20394907.html
Sent from the Csound - General mailing list archive at Nabble.com.