Pure Data [bang~] equivalent

italic-disco!

yo, i'm wondering if something could be done with the fftin~ nofft to replicate tabreceive~ ; and if maybe vectral~ could be of help here

Also when i downloaded the pd patch from Martin's website, there is no samphold~ anymore in the abs_small_paul abstraction. Where did you get your version, Fora ?

@vichug

I found a few useful conversions in this post linked below

https://cycling74.com/forums/conversion-in-maxmsp

> samphold~

does pd:wrap~ work for negative numbers, and if yes, what does it it do? i might have a replacement.

I believe it works for negative numbers. wrap~ can be replaced with [%~ 1.]

I came across wrap~ in the post I linked just above.

from PD, wrap~ is explained as follows; Remainder modulo 1

'[wrap~] gives the difference between the input and the largest integer not exceeding it (for positive numbers this is the fractional part)'

I believe it works for negative numbers. wrap~ can be replaced with [%~ 1.]

that is somehow contradictory, because % does not not work for negative numbers. :)

i was always using this

expr ((($f1-int($f1/$f2)*$f2) + ($f2)*(($f1-int($f1/$f2)*$f2)==0))*($f1>=0)) + ((((($f1-int($f1/$f2)*$f2)+$f2) + (-$f2)*((($f1-int($f1/$f2)*$f2)+$f2)==0))*($f1<0)))

but somehow i am afraid there is a simpler way (like some "wrap" external?)

negative numbers on modulo result in negaitive results, which is the correct result, but not what you would exspect from wrapping a range.

(the fonts of Raja's patch appear normal on my machine)
(@Fora i meant, where did you get your PD patch version ? ;) )
re:vectral~, after looking into it slightly further, there is the problem that in pd the pitch change is done in time domain - via reading more or less of the original sound during one frame, so changing playback speed - not spectral domain, so one frame of signal will be repitched *before* there is an fft on it. BUT it is also windowed when it is pitched in this time domain, and not yet fft'ed. So vectral~ couldn't have an use for this problem, only something like "manual" windowing and fft'ing could help, as Raja already suggested... vectral~ could maybe potentially have a use though, if there is a way to change the pitch in fft domain, by "switching" bin's amplitudes - or there is the gizmo~ external, maybe that's how it works, i don't know ; but that wouldn't sound the same surely ?
Then, there is that PD can change windowing block size very conveniently, which you can't do in Max (one needs to recreate the object and give a new arg to change fft/windowing size whereas in PD, you can pass a message to block~). Soooo, er, as Raja said, that's, complicated :p and borderline impossible to obtain exactly the same result as in PureData in as much elegant way (copying abstraction with fft~ and manual windowing for each possible vector size to choose from, or script recreating the fft objects with new frame size each time it's changed are possible options....)