Re: [PD] peak amplitude in pd vanilla (was: [env~] vs [vsnapshot~]: which one is more cpu consuming?)

2010-02-16 Thread Matt Barber
If you need to send a 0 at the beginning of each block, here are some interesting ways of doing it that just occurred to me: __ [sig~ -1] [block ] | [rfft~] | [/~ ] | [+~ 1] | ___ and the best: ___ [sig~

Re: [PD] peak amplitude in pd vanilla (was: [env~] vs [vsnapshot~]: which one is more cpu consuming?)

2010-02-15 Thread Matt Barber
> hello > > im sorry i left the thread for some time now. > thank you all very much for your replies. > > Your results are confirmed here too: the two methods with vsnapshot~  and > writing-reading to a table are equally inefficient. > Matt's suggestion --whilst much more efficient-- has a serious

Re: [PD] peak amplitude in pd vanilla (was: [env~ ] vs [vsnapshot~ ]: which one is more cpu consuming?)

2010-02-14 Thread ypatios
hello im sorry i left the thread for some time now. thank you all very much for your replies. Your results are confirmed here too: the two methods with vsnapshot~ and writing-reading to a table are equally inefficient. Matt's suggestion --whilst much more efficient-- has a serious disadvantage:

Re: [PD] peak amplitude in pd vanilla (was: [env~ ] vs [vsnapshot~ ]: which one is more cpu consuming?)

2010-02-09 Thread William Brent
> Note that [metro] has a lower limit of 1 ms, so you need to make your own > metro-abstraction. Ah - I had no idea that this was true. I suggested using a metro with a rate of 1/44.1 ms as an alternative to [block~ 1], but I guess there's no way around it... It seems like the best thing to hav

Re: [PD] peak amplitude in pd vanilla (was: [env~ ] vs [vsnapshot~ ]: which one is more cpu consuming?)

2010-02-09 Thread Matt Barber
> > As I understand it (and hopefully i am not completely wrong..) you don't > have to 'store' a list and 'then' read again it to find the max magnitude. > It's as simple as the following: > > (some signal) > *I* > *I* [pd me...@samplerate] > *I*/ > [vsnapshot~ ] > | > [abs ] > | > [moses ]X[t f ]

Re: [PD] peak amplitude in pd vanilla (was: [env~ ] vs [vsnapshot~ ]: which one is more cpu consuming?)

2010-02-09 Thread Frank Barknecht
Hallo, ypatios hat gesagt: // ypatios wrote: > As I understand it (and hopefully i am not completely wrong..) you don't > have to 'store' a list and 'then' read again it to find the max magnitude. > It's as simple as the following: > > (some signal) > *I* > *I* [pd me...@samplerate] Note that [m

Re: [PD] peak amplitude in pd vanilla (was: [env~ ] vs [vsnapshot~ ]: which one is more cpu consuming?)

2010-02-09 Thread IOhannes m zmoelnig
On 2010-02-09 11:21, ypatios wrote: > Hallo Frank :-), thanks for your reply > > (i updated the subject since the discussion moved on..) > > While you could bang vsnapshot~ at samplerate and keep track of samples in a >> list or so, this is a waste of resources. Something like tabsend~ or >> tabw

[PD] peak amplitude in pd vanilla (was: [env~ ] vs [vsnapshot~ ]: which one is more cpu consuming?)

2010-02-09 Thread ypatios
Hallo Frank :-), thanks for your reply (i updated the subject since the discussion moved on..) While you could bang vsnapshot~ at samplerate and keep track of samples in a > list or so, this is a waste of resources. Something like tabsend~ or > tabwrite~ > probably is much better: Just write a nu