[Csnd] alpass, valpass, comb, vcomb opcodes noisy

[Csnd] alpass, valpass, comb, vcomb opcodes noisy

Date	2009-11-30 05:44
From	Rene Djack
Subject	[Csnd] alpass, valpass, comb, vcomb opcodes noisy
	Hi list, I found that all these opcodes generate a discontinuity every lpt second. The same is for reverb opcode (internally using alpass and comb opcodes). Can test with see alpass.csd in manual. Linux Ubuntu Studio 9.10, csound5.11.1 float, double, csound cvs. Cheers, René

Date	2009-11-30 08:49
From	Victor Lazzarini
Subject	[Csnd] Re: alpass, valpass, comb, vcomb opcodes noisy
	Can you post your test CSD? Victor On 30 Nov 2009, at 05:44, Rene Djack wrote: > Hi list, > > I found that all these opcodes generate a discontinuity every lpt > second. > The same is for reverb opcode (internally using alpass and comb > opcodes). > Can test with see alpass.csd in manual. > > Linux Ubuntu Studio 9.10, csound5.11.1 float, double, csound cvs. > > Cheers, > René Send bugs reports to this list. To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2009-11-30 08:59
From	jpff@cs.bath.ac.uk
Subject	[Csnd] Re: alpass, valpass, comb, vcomb opcodes noisy
	> Hi list, > > I found that all these opcodes generate a discontinuity every lpt second. > The same is for reverb opcode (internally using alpass and comb opcodes). > Can test with see alpass.csd in manual. I do not think that reverb uses alpass opcode internally. It has a separate implementation of allpass filters. Sorry but I do not undersatbs "every lpt second". Can you explain? ==John ff Send bugs reports to this list. To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2009-11-30 09:00
From	Victor Lazzarini
Subject	[Csnd] Re: Re: alpass, valpass, comb, vcomb opcodes noisy
	No problems seen here, at least with comb. I expect the same with other opcodes. I put a sinewave through and did not see any 'discontinuity' at the output a multiples of loop time. -o combtest.wav -d 0dbfs = 1 ; MAX AMPLITUDE IS 1.0 !!!! instr 1 asig oscili 0.5, 440, 1 a1 comb asig, 0.9, 0.5 out a1 endin f1 0 16384 10 1 i1 0 20 The reason I am suspicious about this report is that these opcodes are old (in the case of comb, more than 20 years, it's been there since the first version of Csound). They have been used by many people and if such a so blatant problem was present, we would have known about it a long time ago. But I can be wrong. In any case, you'll need to supply a test CSD to demonstrate the problem. Victor On 30 Nov 2009, at 08:49, Victor Lazzarini wrote: > Can you post your test CSD? > > Victor > On 30 Nov 2009, at 05:44, Rene Djack wrote: > >> Hi list, >> >> I found that all these opcodes generate a discontinuity every lpt >> second. >> The same is for reverb opcode (internally using alpass and comb >> opcodes). >> Can test with see alpass.csd in manual. >> >> Linux Ubuntu Studio 9.10, csound5.11.1 float, double, csound cvs. >> >> Cheers, >> René > > > > 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	2009-11-30 09:35
From	Rene Djack
Subject	[Csnd] Re: Re: Re: alpass, valpass, comb, vcomb opcodes noisy
Attachments	alpass.csd alpass.wav
	Hi, Sorry i post too fast. Your test csd is fine also on my system, but if i use the alpass.csd ( or comb.csd...) included in manual i really have discontinuity, here is the test csd and the generated wav. Cheers, René 2009/11/30 Victor Lazzarini <Victor.Lazzarini@nuim.ie> No problems seen here, at least with comb. I expect the same with other opcodes. I put a sinewave through and did not see any 'discontinuity' at the output a multiples of loop time. <CsoundSynthesizer> <CsOptions> -o combtest.wav -d </CsOptions> <CsInstruments> 0dbfs = 1 ; MAX AMPLITUDE IS 1.0 !!!! instr 1 asig oscili 0.5, 440, 1 a1 comb asig, 0.9, 0.5 out a1 endin </CsInstruments> <CsScore> f1 0 16384 10 1 i1 0 20 </CsScore> </CsoundSynthesizer> The reason I am suspicious about this report is that these opcodes are old (in the case of comb, more than 20 years, it's been there since the first version of Csound). They have been used by many people and if such a so blatant problem was present, we would have known about it a long time ago. But I can be wrong. In any case, you'll need to supply a test CSD to demonstrate the problem. Victor On 30 Nov 2009, at 08:49, Victor Lazzarini wrote: Can you post your test CSD? Victor On 30 Nov 2009, at 05:44, Rene Djack wrote: Hi list, I found that all these opcodes generate a discontinuity every lpt second. The same is for reverb opcode (internally using alpass and comb opcodes). Can test with see alpass.csd in manual. Linux Ubuntu Studio 9.10, csound5.11.1 float, double, csound cvs. Cheers, René 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	2009-11-30 09:52
From	Rene Djack
Subject	[Csnd] Re: Re: Re: alpass, valpass, comb, vcomb opcodes noisy
	Oups... The discontinuity is coming from instr 1 with no declick envelope! Very sorry for the noise. Cheers, René 2009/11/30 Victor Lazzarini <Victor.Lazzarini@nuim.ie> No problems seen here, at least with comb. I expect the same with other opcodes. I put a sinewave through and did not see any 'discontinuity' at the output a multiples of loop time. <CsoundSynthesizer> <CsOptions> -o combtest.wav -d </CsOptions> <CsInstruments> 0dbfs = 1 ; MAX AMPLITUDE IS 1.0 !!!! instr 1 asig oscili 0.5, 440, 1 a1 comb asig, 0.9, 0.5 out a1 endin </CsInstruments> <CsScore> f1 0 16384 10 1 i1 0 20 </CsScore> </CsoundSynthesizer> The reason I am suspicious about this report is that these opcodes are old (in the case of comb, more than 20 years, it's been there since the first version of Csound). They have been used by many people and if such a so blatant problem was present, we would have known about it a long time ago. But I can be wrong. In any case, you'll need to supply a test CSD to demonstrate the problem. Victor On 30 Nov 2009, at 08:49, Victor Lazzarini wrote: Can you post your test CSD? Victor On 30 Nov 2009, at 05:44, Rene Djack wrote: Hi list, I found that all these opcodes generate a discontinuity every lpt second. The same is for reverb opcode (internally using alpass and comb opcodes). Can test with see alpass.csd in manual. Linux Ubuntu Studio 9.10, csound5.11.1 float, double, csound cvs. Cheers, René 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"