A collection of 14 objects that can be used to create static shapes in a graph-on-parent patch or abstraction using a single object with creation arguments for each shape, all the arguments are required except for the destination(last), which can be replaced by the single outlet using send and a bang to it's inlet, useful only for creation order changes and the destination should be cleared first.

IMPORTANT the destination patch or graph-on-parent patch should be cleared before saving changes. This is because the objects are created at load time by an internal loadbang and any previously saved objects scalar may be stranded and accumulate in the .pd file causing Pd to crash on the next load. The file also grows from a few KB to 20KB or 30 KB. Use the object "clear-first" as the very first object.

These objects require a graph-on-parent to have ranges set from 0 to size to match the GOP window size otherwise the object will be distorted

Once the desired graphics are completed and saved, create another GOP patch of the same size and new name, place above the graphics patch and add controls etc.

Pd-vanilla uses rounded end caps for its drawn lines, this gives soft or rounded corners to weightier lines. This also gives us the ability to make nicer circles by creating a single pixel dot and changing the weight (line-width) to change the size, "circle-filled" and "circle-filled-xl" use this feature.

“rectangle”, “rectangle-filled”, “singleline”, "circle-unfilled", "ellipse" and "ellipse-filled" are drawn geometrically and "ellipse" / "ellipse-filled" can also draw circles when the width and height are the same.

"polygon" has a maximum of 8 nodes, any unused nodes need to repeat the last node.
"polygon-filled" has a maximum of 7 nodes, any unused nodes need to repeat the last node and the last node will join to the first node and enclose the shape.

"curve" and "curve-filled" both have a start position followed by 12 nodes as offsets from there. It is easier to decide the number of nodes to use first then create the curve from the right side and leave the remaining nodes as 0 offsets.

"seriesoflines-h" and "seriesoflines-v" useful for drawing grids of horizontal and vertical lines that could also be skewed.

Vanilla-Shapes.zip

I was teaching Pd synthesis class & was surprised how hard it was to find vanilla waveguide models for Pd. I stumbled upon the ACRE Waveguide Library, but lots of externals needed. Anyone know of vanilla waveguide models ppl have shared online?

FYI, an algorithm I was taught in school uses a heap-based priority queue for that B array.

Oh nice, I overlooked that one... the limitations of having zero formal training in CS. I actually have a pure vanilla float-heap abstraction already (https://github.com/jamshark70/hjh-abs)... lower values to the top. For descending order, I'd just negate on the way in and out.

hjh

Could you explain how to use this?

Maybe someone can make this more elegant than me.bit_Crusher.pd

this example from my live electronics tutorial explains how to do this in a more elegant way with expr~

i just read the starting post again - and as it seems i did not do that before asking that question.

it would have been my next question why you do not use coefficients which somebody else made already.

no i havent tested those yet, but i might come back one day with proposals.

mvu-2.pd
Edit: Oh yeah, I forgot the multichannel stuff, had a plan for that but don't recall what it was.

While [goto] does make it easier and quicker to navigate large patches and helps avoiding having to open loads of subpatches just to get to that one buried subpatch you want to work on it results in having an excess of [goto]s which are often only needed once or twice. So now we have [g2], works the same but no clicking needed and it deletes itself after running. Requires iemguts.
g2.pd

But some libraries are compiled as a single binary. The Gem library for example only contains Gem.exe. So when you create a [gemwin] it cannot be found in the search. Those are the libraries that have to be loaded as Pd starts, using the -lib flag..... so Pd then has all of the objects that the library contains already loaded in memory when you create an object.... and it doesn't need to search for them.

[declare] loads the single binary as the patch is opened....... -lib as Pd starts.
[declare] is more useful if the library is stored on your computer in a path outside the Pd standard paths (perhaps you bundled it up into a subfolder when you uploaded your patch) .... as you can set the path to the library..... although for your own use you can also add search paths to Pd using "file" "preferences" "path" from the Pd menu.
David.

1 at the beginning and 2 at the end.

Could be done cheaper, but is cleanly layed out ...
array-guard.pd
array-guard-help.pd

late edit / some additional notes:
. Syntax is: 51234512
. Audio example uses a very short array, the bigger it gets the less audible artifacts become
. [tabread4~] helpfile (pd 0.55.0) is wrong about right inlet had to be a signal, control input works too.

I find myself creating loops with [until] [f] [+ 1] etc... over and over again. Today I finally made a [for] loop abstraction, with start, stop and step arguments, it can also increment or decrement. I tried to document it thoroughly. Hope to help.

for.pd
for-help.pd

Toggle in the signal domain... here are a couple of ways.

toggleff~.pd -- probably faster, but it may overflow after a long time (hours).

toggleff-forever~.pd -- will not overflow, but uses fexpr~ so it might be slower.

Both define a signal trigger as a crossing from <= 0 to > 0.

Was first looking into this in Max (which doesn't have a native one), then wondered what it would take in Pd. Not that much but it's enough that you don't want to build it out by hand every time.

hjh