Spectral Examples

[@machinate]

I'm just here to comment on how meta it is to use the Alvin Lucier piece for this, heh. Nice touch.

[@josselinvinay7738]

thank you for your tutorial. i've learned one more thing today! thank you for share patchs

[@dolphin_dog]

truly transformational

[@lauprellim]

Hi, this is really great. Thank you so much for posting this video and the patches.

[@elduc8520]

Thanks for the explanation and the patch, i was rusted with fft, this helps a lot. Will give you feedback, have a good day. M

[@runner0075]

2 little questions about the spectral delay pfft~ subpatch: A) why do you multiply by two the spectral frame size coming form fftinfo~? the FFT spectral frame size is 512, and the ramp coming from fftin~ is 0/511, so at first glance this multiplication is not needed. B) why do you add a 2nd delay (delay~)? it seems it adds another (one or two) full FFT frames in the total delay time .. The tapin/tapout delay time is already quantised because by trunc~..

[@ms-1106]

This is so helpful. Thanks for the excellent tutorial !!

[@runner0075]

many thanks Sir

[@nurse_plissken8433]

Awesome. Just what I needed!

[@runner0075]

Amazing tut

[@theBobSugarProject]

This is super helpful! Thanks a lot. Can you help me with a question considering the spectral delay. The FFT size is 1024 this correspondents with 512 bins right? How come the multi slider objects with the delay and feedback values contain only 256 sliders? Shouldn't there be one delay and feedback value per bin?

[@TwistedSignals]

Good catch - yes I think you'd want to update the multisliders to provide one value per bin. Or resize the FFT to match the sliders.

[@theBobSugarProject]

Also I still don't really get how pfft~ behaves compared to poly~. Why is '#0' needed in the names of the buffers?

[@TwistedSignals]

#0 turns into a unique number. This would let you have multiple copies of the patch running, all with unique buffers.