is there any way to control/change the FFT Size of a pfft~ using an Umenu or any other stored value instead of typing the new size as an argument?

umenu-fft-size-control

if you mean changing the fft size dynamically, I don't think you can

The only mean I know is by scripting. (delete pfft~, and reinstantiate a new

one with the new FFT size). You will interrupt the audio chain, thus get a

> is there any way to control/change the FFT Size of a pfft~ using an Umenu or

> any other stored value instead of typing the new size as an argument?

The only mean I know is by scripting. (delete pfft~, and reinstantiate a new
one with the new FFT size). You will interrupt the audio chain, thus get a
click or even further problems.
Jean-Francois. 

>
> is there any way to control/change the FFT Size of a pfft~ using an Umenu or
> any other stored value instead of typing the new size as an argument?
>

Scripting is not a problem for me, but I am a bit concerned if this will work within a plug-in ?

I want the user to be able to define the FFT Size when the plug-in is loaded.

I haven't done much plug-in work, but as long as you don't change the fft size while your audio is running it shouldn't be a problem.

Quote: maronid wrote on Wed, 24 December 2008 15:32

----------------------------------------------------

> is there any way to control/change the FFT Size of a pfft~ using an Umenu or any other stored value instead of typing the new size as an argument?

I used gate~ 8 with 8 different pfft~ objects and their different sizes hardwired in. With matrix~ you could avoid the clicks too (I was just experimenting so it didn't matter). I don't know if having multiple ones are a problem processor-wise since only one is active at a time, perhaps someone here knows? With the gate~ of course you can have the drop-down, which was nice.

It was definitely cool to try out the different fft~ sizes on different samples, with wacko values of sig~/speed and gizmo~/pitch shift, it was pretty insane what a basic sample could be mangled into... a snare hit sounded like a totally distorted space-violin, great stuff!

Quote: maronid wrote on Wed, 24 December 2008 15:32
----------------------------------------------------
> Hi,
>
> is there any way to control/change the FFT Size of a pfft~ using an Umenu or any other stored value instead of typing the new size as an argument?
>
----------------------------------------------------

all you need to avoid the processor issue is to use the begin~ object in order to shut off the unused signal networks.... i think!

To gain on CPU usage, you will need to put each of these pfft~ inside a

poly~, and mute all the unused ones (wihtout poly~, all pfft~ are "active"

whether you give them an audio signal or a null signal).

With this technique, you can indeed change the FFT size, overlap, and even

inside the pfft~ the window shape, all without clicks.

> I used gate~ 8 with 8 different pfft~ objects and their different sizes

> hardwired in. With matrix~ you could avoid the clicks too (I was just

> experimenting so it didn't matter). I don't know if having multiple ones are a

> problem processor-wise since only one is active at a time, perhaps someone

> here knows? With the gate~ of course you can have the drop-down, which was

Sounds like a good idea!
To gain on CPU usage, you will need to put each of these pfft~ inside a
poly~, and mute all the unused ones (wihtout poly~, all pfft~ are "active"
whether you give them an audio signal or a null signal).
With this technique, you can indeed change the FFT size, overlap, and even
inside the pfft~ the window shape, all without clicks.
Jean-Francois.

> I used gate~ 8 with 8 different pfft~ objects and their different sizes
> hardwired in. With matrix~ you could avoid the clicks too (I was just
> experimenting so it didn't matter). I don't know if having multiple ones are a
> problem processor-wise since only one is active at a time, perhaps someone
> here knows? With the gate~ of course you can have the drop-down, which was
> nice.

does putting the pfft into a patcher and using mute~ not work?

> does putting the pfft into a patcher and using mute~ not work?

Actually, toggle -> [mute~] -> [pfft~ .....] seems to work, too.

Yes, it seems to work great as well.
Actually, toggle -> [mute~] -> [pfft~ .....] seems to work, too.
J-F.

You can also put the pfft INS poly~ change the arguments of the poly~ 

dynamically and reload the patch by resending the patchername. That 

way it does not interrupt the main DSP chain.

On 26 déc. 08, at 23:45, Nick Inhofe wrote:

You can also put the pfft INS poly~ change the arguments of the poly~  
dynamically and reload the patch by resending the patchername. That  
way it does not interrupt the main DSP chain.

On 26 déc. 08, at 23:45, Nick Inhofe  wrote:

>
> does putting the pfft into a patcher and using mute~ not work?


yea, but wouldn't it be great if pfft just accepted a message to change the fft size. Anyone know why it doesn't? Ill take the click for the simplicity of a message going into pfft to change fft size/overlap, and write a patch using poly (as described above, thanks!) if I don't want the click. Maybe in next version?

"yea, but wouldn't it be great if pfft just accepted a message to change the fft size...Maybe in next version?"

That is for me one of the most annoying things in Max...why can't I simply change the fft size and overlap factor with a message? I want to make a Max for Live device, based on pfft, and i really don't want to have loads of pffts inside, with all the possible permutations of fft size and overlapping factors...

8 years later, but hell. You can scale the FFT size Inside your pfft~ if you set the pfft to a fixed size, like1024, and use a [/~ "your desired value"] with the third inlet of the [fftin~1], which is the bin index. A little less elegant, but it should work in theory.

8 years later, but hell.  You can scale the FFT size Inside your pfft~ if you set the pfft to a fixed size, like1024, and use a [/~ "your desired value"] with the third inlet of the [fftin~1], which is the bin index. A little less elegant, but it should work in theory. 

Umenu FFT Size Control