I've been building some simple things and learning my way around PD vanilla. All in all it's a very nice system especially for free.

One thing that isn't working is creating windows for granular and FFT processing. I follow the exact patching from the tutorials that are included in the documentation. These things usually rely on "loadbang" for writing a single cycle of cosine to a table, buffer, etc. When I set this up I always still have to have to draw the table by hand. The filtering that I'm doing is working just fine, but I'm curious what I'm doing wrong. I've added a manual "bang" to write the table, calculate the size, etc, as well, but no luck. Usually I end up with nothing in the table.

I've had the same issue with granular synthesis. Even if I use a cos~ table that's offset and driven by a phasor~ I get clicks out the wahoo. This has happened even when just opening full patches that were made by the guy who wrote the software.

Anyhow. I'm finding workarounds for everything anyway, so hopefully things won't stay weird. It just seems like my system is acting screwy. I'm happy to try anything at this point as I'm looking forward to setting up my spare rPi as a standalone host for pd. Right now I'm just diddling around on my old 3930k windows 7 system so I don't get too carried away when I start trying to move things over to the Pi.

Thanks for any help,

JJ

Maybe the tutorial is older and uses table instead of array?
Also, have you checked the example file I02.Hann.window.pd?
It would help if you precise which tutorial you are trying to follow.

Hope this helps ...

You can check out [window] from my github repo here and see how it works.

I was using the FFT tutorials (in the html help) for making a stereo FFT filter. It wants to have the sample rate divided by the block size and fed to an osc~ which is fed into a tabwrite~ with a phase offset. This is all in the main patch. Then the window should be readable in the FFT sub patch. The table just stays blank. I'm trying to keep things as vanilla as possible until I can do most of what I want. Then I'll start adding on.

https://puredata.info/docs/manuals/pd this is the documentation I was using. In the FFT section I built the "window maker" in the exact way that it was put together in the documentation. I've been having these types of issues with many things that involve arrays. Even simple stuff like making a scope for the output. Often time they simply won't draw in data and the data isn't there if you try to print it etc.

@ah_dziz The only thing that I can think of that would stop tables being drawn is if DSP is turned off, or the audio thread is not running because Pd has failed to communicate properly with the OS.
But you say audio is running fine.
Maybe upload a patch you have made that is not drawing to the table/array and we can see if it works for us...... use the "Up arrow" symbol above the post that you are writing.
David.

Will do. I have also tried using an offset cos~ table to make a window but it quickly turns clicky. On the bright side all my other experiments (that need no windowing) are working well. I'll upload what I made next time I'm on the machine.

Populating a window table depends on a couple of patching design patterns that come up everywhere, but which nobody talks about:

1. Initialize - process - finalize (where finalizing is sometimes optional).
2. Counting.

That is, the "fill operation" consists of counting an index from the beginning of the array to the end. Each index value gets mapped mathematically onto the window value at that moment, and [tabwrit(e)]-ten into the array.

Since you're saying that nothing is happening in your loop, I'd have to guess that some of this logic is not quite right in your patch.

Step by step:

"Initialize/process" is because, every time you bang the operation, you want to start at the beginning of the array. So the counter needs to be initialized. Use [t] at the top -- we need at least 2 bangs here.

The loop is done by [until]. The [array size] is to tell it how many times to run.

Then, for tabread4~, you need:

• i = 1, phase = 0
• i = size-3, phase = pi

phase = (i - 1) / (size-4) * pi (I might be off-by-one here?)

Then take sin^2 of this for a Hann window.

I added another "f" into the counter's [t], because one branch here needs to set the [tabwrite] index (and this must happen before doing the math). Also the (size-4) needs a [t] to split the array-size output message.

hjh

I'll give it a go that way when I get back on it. On the plus side, I've been having fun with my janky hand drawn windows for my little FFT filter. It turns out that having weird shaped windows makes for some silly sounding spectral noises. In all my other software one used to having to drive the "write position" when filling an array. I was surprised when the documentation didn't mention it. Is there a way to have the array spit out it's current write index? And can any of the tabread~ objects spit out their current location as a number? I'm guessing yes but the documentation seems a bit behind the times. Thanks for the info!

JJ

@ah_dziz There is no "current index" but you can get the value at an index.
Pd extended help was a bit more informative (and was correct)...... read.zip
David.