Ken Murphy

I'm trying to use frameaverage~ to create a running average of FFT frames (see my related post: 

https://cycling74.com/forums/generating-averaged-audio/).

 In a nutshell, I'm trying to average the harmonic content of an audio signal over time. I've had a degree of success, but I'm still a bit stymied. Here's the pfft~ subpatch:

And here's the (very basic) parent patch:

As I increase the @framecount for the frameaverage~ object, I initially get the results I expect: the harmonic content is "smeared" over time. E.g., If I set @framecount to 10, I get about a second of averaging, if I set it to 20, I get a bit under 2 seconds. This is particularly apparent if I cut the audio input signal: it takes what seems like the expected amount of time to "fade out" as the zero-amplitude frames are averaged in.

By this token I should be able to average the audio over a period much longer than a second or two, but I'm not getting the results I'm expecting when I increase the @framecount. For example, if I set the @framecount to 100, I should expect 4096 (frame size) * 100 = 409600 samples = ~9.3 seconds of averaging. Therefore when I cut the audio input, the output should fade out over something close to that length of time. However, it cuts out in just a second or 2. This is frustrating as my goal is to process longer segments of audio (in the 20-second range or more).

So perhaps I'm making some incorrect assumptions about what frameaverage~ does under the hood, or what its limitations are. But I'm also a bit stumped by the frameaverage~ reference page regarding the @framecount attribute, which states that it is "Limited to between 1 and the 'maxframecount' argument given at object instantiation." What's this maxframecount argument? What is meant by "given at object instantiation?" It is not a documented argument or attribute of frameaverage~ (I tried setting it as an attribute and got an error. Using argument syntax, it had no effect), and I can't find a mention of it anywhere. But if I am hitting on a max value for framecount, that would explain the behavior I'm seeing.

Any insights would be greatly appreciated!

Here's he reference page for frameaverage~: 

https://docs.cycling74.com/max7/maxobject/frameaverage~

I'm trying to use frameaverage~ to create a running average of FFT frames (see my related post: https://cycling74.com/forums/generating-averaged-audio/). In a nutshell, I'm trying to average the harmonic content of an audio signal over time. I've had a degree of success, but I'm still a bit stymied. Here's the pfft~ subpatch:

So perhaps I'm making some incorrect assumptions about what frameaverage~ does under the hood, or what its limitations are. But I'm also a bit stumped by the frameaverage~ reference page regarding the @framecount attribute, which states that it is "Limited to between 1 and the 'maxframecount' argument given at object instantiation."  What's this maxframecount argument? What is meant by "given at object instantiation?" It is not a documented argument or attribute of frameaverage~ (I tried setting it as an attribute and got an error. Using argument syntax, it had no effect), and I can't find a mention of it anywhere. But if I am hitting on a max value for framecount, that would explain the behavior I'm seeing.

Here's he reference page for frameaverage~: https://docs.cycling74.com/max7/maxobject/frameaverage~


frameaverage-and-maxframecount

[frameaverage~ 100 @framesize 4096 @framecount 1]

I think the argument needs to be first:
[frameaverage~ 100 @framesize 4096 @framecount 1]

frameaverage~ and maxframecount