Csound Csound-dev Csound-tekno Search About

[Csnd] lpslot

Date2010-06-08 11:39
Frommenno
Subject[Csnd] lpslot
Hi, 
i'm investigating the use of LPC, in particular the use of lpslot.
So far i have discovered that lpinterp wants lpc files that are analyzed
with filter poles values (-a option)
then the way to be able to mix two lpc files is to put each lpc file in a
different lpslot. LPC files must have equal amount of poles - in this case
50 poles.
I get no errors but only a loud click, i guess DC.
What goes wrong?



; Select audio/midi flags here according to platform
; Audio out   Audio in    No messages
-odac           -iadc     -d     ;;;RT audio I/O



sr = 44100
kr = 4410
ksmps = 10
nchnls = 1

instr 1
asig	buzz	20000, 440, 10, 1
;fox50poles.lp = 2.8 seconds long
;flute50poles.lp = 2.6 seconds long
ktime  line 0, p3, p3
				lpslot	0
krmsr,krmso,kerr,kcps	lpread   
ktime,"/home/menno/manual/examples/fox50poles.lp"
				lpslot	1
krmsr,krmso,kerr,kcps	lpread   
ktime,"/home/menno/manual/examples/flute50poles.lp"

kmix	line	0, p3, 2
; lpinterp works only with poles files..
				lpinterp	 0, 1, kmix				
aout				lpreson	asig		                   ;buzz output
ares				balance	aout, asig
       out ares*.01
endin


f1 0 4096 10 1
i 1 0 2.8
e


is someone willing to try this out?
Menno

Date2010-06-08 12:12
FromDave Phillips
Subject[Csnd] re: preparing files for LPC analysis
Greetings,

At one time I was fascinated by the possibilities of LPC. I managed to 
write at least one decent piece based on its use, and I was totally 
off-base in my understanding of the LPC processes. The piece was good 
though. :)

IIRC I had to ensure that there were *no* periods of absolute silence in 
the analyzed soundfile. That meant trimming the beginning and end 
points, and again IIRC I added noise to any other moments of complete 
silence. Apparently any 0 amplitude value will cause the analysis to fail.

LPC is rather tricky to "get right". Plan on lots of trial & error. :)

Best,

dp



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date2010-06-08 12:22
FromVictor Lazzarini
Subject[Csnd] Re: lpslot
I think this is to do with the input sounds you are using. I have used  
the same CSD with other sounds and got no loud click (but not a good  
result, nevertheless).
As Dave said LPC is tricky.

Victor

On 8 Jun 2010, at 11:39, menno wrote:

>
> Hi,
> i'm investigating the use of LPC, in particular the use of lpslot.
> So far i have discovered that lpinterp wants lpc files that are  
> analyzed
> with filter poles values (-a option)
> then the way to be able to mix two lpc files is to put each lpc file  
> in a
> different lpslot. LPC files must have equal amount of poles - in  
> this case
> 50 poles.
> I get no errors but only a loud click, i guess DC.
> What goes wrong?
>
> 
> 
> ; Select audio/midi flags here according to platform
> ; Audio out   Audio in    No messages
> -odac           -iadc     -d     ;;;RT audio I/O
> 
> 
>
> sr = 44100
> kr = 4410
> ksmps = 10
> nchnls = 1
>
> instr 1
> asig	buzz	20000, 440, 10, 1
> ;fox50poles.lp = 2.8 seconds long
> ;flute50poles.lp = 2.6 seconds long
> ktime  line 0, p3, p3
> 				lpslot	0
> krmsr,krmso,kerr,kcps	lpread
> ktime,"/home/menno/manual/examples/fox50poles.lp"
> 				lpslot	1
> krmsr,krmso,kerr,kcps	lpread
> ktime,"/home/menno/manual/examples/flute50poles.lp"
>
> kmix	line	0, p3, 2
> ; lpinterp works only with poles files..
> 				lpinterp	 0, 1, kmix				
> aout				lpreson	asig		                   ;buzz output
> ares				balance	aout, asig
>       out ares*.01
> endin
> 
> 
> f1 0 4096 10 1
> i 1 0 2.8
> e
> 
> 
> is someone willing to try this out?
> Menno
> -- 
> View this message in context: http://old.nabble.com/lpslot-tp28816231p28816231.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date2010-06-08 12:25
FromPeiman Khosravi
Subject[Csnd] Re: Re: lpslot
Worth checking out this thread too. Andreas' suggestion helped me out  
at the time.

http://old.nabble.com/LPC-random-bursts--bug---to27931321.html#a27931876

P

On 8 Jun 2010, at 12:22, Victor Lazzarini wrote:

> I think this is to do with the input sounds you are using. I have  
> used the same CSD with other sounds and got no loud click (but not a  
> good result, nevertheless).
> As Dave said LPC is tricky.
>
> Victor
>
> On 8 Jun 2010, at 11:39, menno wrote:
>
>>
>> Hi,
>> i'm investigating the use of LPC, in particular the use of lpslot.
>> So far i have discovered that lpinterp wants lpc files that are  
>> analyzed
>> with filter poles values (-a option)
>> then the way to be able to mix two lpc files is to put each lpc  
>> file in a
>> different lpslot. LPC files must have equal amount of poles - in  
>> this case
>> 50 poles.
>> I get no errors but only a loud click, i guess DC.
>> What goes wrong?
>>
>> 
>> 
>> ; Select audio/midi flags here according to platform
>> ; Audio out   Audio in    No messages
>> -odac           -iadc     -d     ;;;RT audio I/O
>> 
>> 
>>
>> sr = 44100
>> kr = 4410
>> ksmps = 10
>> nchnls = 1
>>
>> instr 1
>> asig	buzz	20000, 440, 10, 1
>> ;fox50poles.lp = 2.8 seconds long
>> ;flute50poles.lp = 2.6 seconds long
>> ktime  line 0, p3, p3
>> 				lpslot	0
>> krmsr,krmso,kerr,kcps	lpread
>> ktime,"/home/menno/manual/examples/fox50poles.lp"
>> 				lpslot	1
>> krmsr,krmso,kerr,kcps	lpread
>> ktime,"/home/menno/manual/examples/flute50poles.lp"
>>
>> kmix	line	0, p3, 2
>> ; lpinterp works only with poles files..
>> 				lpinterp	 0, 1, kmix				
>> aout				lpreson	asig		                   ;buzz output
>> ares				balance	aout, asig
>>      out ares*.01
>> endin
>> 
>> 
>> f1 0 4096 10 1
>> i 1 0 2.8
>> e
>> 
>> 
>> is someone willing to try this out?
>> Menno
>> -- 
>> View this message in context: http://old.nabble.com/lpslot-tp28816231p28816231.html
>> Sent from the Csound - General mailing list archive at Nabble.com.
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>> "unsubscribe csound"
>>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date2010-06-08 15:03
Frommenno
Subject[Csnd] Re: Re: lpslot
thank you all for your answers.
This will need some ( = a lot) more experimentation. i do like the pops and
crackels LPC produces. They remind me of a simple transistor radio, opening
the case of it and touching the electronics by hand :)


Menno


peiman wrote:
> 
> Worth checking out this thread too. Andreas' suggestion helped me out  
> at the time.
> 
> http://old.nabble.com/LPC-random-bursts--bug---to27931321.html#a27931876
> 
> P
> 
> On 8 Jun 2010, at 12:22, Victor Lazzarini wrote:
> 
>> I think this is to do with the input sounds you are using. I have  
>> used the same CSD with other sounds and got no loud click (but not a  
>> good result, nevertheless).
>> As Dave said LPC is tricky.
>>
>> Victor
>>
>> On 8 Jun 2010, at 11:39, menno wrote:
>>
>>>
>>> Hi,
>>> i'm investigating the use of LPC, in particular the use of lpslot.
>>> So far i have discovered that lpinterp wants lpc files that are  
>>> analyzed
>>> with filter poles values (-a option)
>>> then the way to be able to mix two lpc files is to put each lpc  
>>> file in a
>>> different lpslot. LPC files must have equal amount of poles - in  
>>> this case
>>> 50 poles.
>>> I get no errors but only a loud click, i guess DC.
>>> What goes wrong?
>>>
>>> 
>>> 
>>> ; Select audio/midi flags here according to platform
>>> ; Audio out   Audio in    No messages
>>> -odac           -iadc     -d     ;;;RT audio I/O
>>> 
>>> 
>>>
>>> sr = 44100
>>> kr = 4410
>>> ksmps = 10
>>> nchnls = 1
>>>
>>> instr 1
>>> asig	buzz	20000, 440, 10, 1
>>> ;fox50poles.lp = 2.8 seconds long
>>> ;flute50poles.lp = 2.6 seconds long
>>> ktime  line 0, p3, p3
>>> 				lpslot	0
>>> krmsr,krmso,kerr,kcps	lpread
>>> ktime,"/home/menno/manual/examples/fox50poles.lp"
>>> 				lpslot	1
>>> krmsr,krmso,kerr,kcps	lpread
>>> ktime,"/home/menno/manual/examples/flute50poles.lp"
>>>
>>> kmix	line	0, p3, 2
>>> ; lpinterp works only with poles files..
>>> 				lpinterp	 0, 1, kmix				
>>> aout				lpreson	asig		                   ;buzz output
>>> ares				balance	aout, asig
>>>      out ares*.01
>>> endin
>>> 
>>> 
>>> f1 0 4096 10 1
>>> i 1 0 2.8
>>> e
>>> 
>>> 
>>> is someone willing to try this out?
>>> Menno
>>> -- 
>>> View this message in context:
>>> http://old.nabble.com/lpslot-tp28816231p28816231.html
>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>>> "unsubscribe csound"
>>>
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>> "unsubscribe csound"
>>
> 
> 
> 
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
> 
> 
>