Explore FFT windowing and apply this new knowledge to the noise reduction and Forbidden Planet patches we built in Part 1. Get the patches: cycling74.com/...
When you change from 511 to 512 the hanning curve in the [scope~] after [index~ fft_window] disappears, and also the hanning curve that should be inverted of phase after the [delay~] is not, is exactly as the other one, so that may be the issue.
"hanning curve that should be inverted of phase after the [delay~] is not" Actually, it's shouldn't be inverted and should be left as Tim set it; the Hanning window isn't doing anything to phase; it's only controlling amplitude/windowing the audio signal
Thank you for this informative and succinct tutorial series. Unfortunately, when following the tutorial precisely but, using plugin~ input from ableton in max4live as a source (instead of the simulated noise patch), it results in very noticeable unwanted harmonic content, even when removing the noise reduction component (straight from fft to ifft). I also tried it with the provided patch just to clarify that I hadn't done something wrong whilst following the tutorial, but this yielded the same result. If anyone could tell me why this may be I would love to know.
As long as I understand there are is an issue about windowing: double windowing at input an outputs causes unwanted amplitude modultaion. Windowing is needed only at input stage.
To the contrary, actually. If you remove the output windowing after [ifft~], you'll notice artifacts in the signal, especially at lower frequencies. This is because the signal of the fft bin has been altered since it's input; you can actually remove the windowing on the input (if you like) with no effect ;)
hello, following strictly the suggested settings and passages i get this messages: " ifft~: ifft~: phase must be multiple of 1024, setting to 0 ". This message is coming from all the fft~ and ifft~ istances set with 512 512 256, so it seems 256 phase shift is not accepted. Any clue on cause and solution? working on 44.1 kHz.
How do I unlock a patcher that has been locked by a feed back loop? I have lost 10 days of work because of one bad connection? WTF is up with that. I can't even delete patch-cords. Any ideas guys? Everyone be careful out there, this is the second time this happened to me. MAX needs a sequential loading option to recover this kinds of shit.
