The only thing like this I've attempted this far just used clone to generate voices . There are tutorials from better programmers than me out there that show proper ways of doing things. I did not have to wire every every voice though they all got their info from the outside.

I've had great luck with just using a couple of noise sources through some filters and then 4 osc~ that are setup to FM on another and have each tone's pitch controlled by a Frequency envelope (line~ with a curve function) as well as an amp envelope (line~ again with a curve control). For hats and cymbals I use almost the exact same setup except the osc~ objects are replaced with phasor~ objects and I use simple Bipolar AM ahead of the filtering. Because of the way that the vanilla filters work, you will probably also want to scale the amp as you adjust the q factor.

With this setup I can make pretty much any sound that I can make with microtonal (my favorite drum synth). For extra fun you can run each drum voice in a single sample block sub patch and do some nifty feedback and filtering as well.

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

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.

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.

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.

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