hi everyone,

i've written a few abstractions and i've decided to upload some of them (most of my useful ones are here). i use pd-extended and i haven't tested whether they'll work on vanilla pd.

there are a lot of small but handy abstractions in this package as well as some more complex sequencers.

i've also included introduction patches which give a quick explanation of almost all the abstractions included.

out of the "small but handy" abstractions i find [map] the most useful.

some of these are really messy, some aren't well-documented, some may have bugs, and some were pretty much ripped off from other people (i've tried to give credit though).

also, there may be a few abstractions you'll want to edit because i have some of my path-names in them. i think [snd~] and the sequencers have them. your best bet is to open them in a text-editor and search for "/home/modula" (without quotes) and replace the directory with whereever you store your sound files or data, respectively.

anyway, hope you enjoy these, and if you have any questions, feel free to reply and i'll elaborate as much as possible.

Edit: i'm now maintaining these on github. the latest versions of them will always be here.

here are a few tips for all of you:

when you make a complex patch with lots of sends and receives or other objects that might need a $0 in the name, instead of typing something like , type . that way, you can still use pd's find to search for "s foo-" (just make sure the "whole word" box is unchecked).

also, to have multiple things coming from one object, i like to do something along these lines:

[map 60'1000 58'500 55'500 53'1000]
|
[s2l ']
|
[unpack f f]

that way, you can get two numbers from the same [map] just by splitting them by an apostrophe. maybe you'd prefer to use multiple maps but i find it's easier to sync them this way.

[map] is sometimes good as a replacement for [select] especially if each outlet of the [select] is connected to a message box anyway. another thing i use [select] for is to select only certain things. however, sometimes i want all instances of something to go to the same place. a good replacement for [select] in this case is [unmap].

[unmap]'s arguments are a list that its input (on the left inlet) is matched against. it will output the input's index in the list if it's matched, but it won't output if it isn't matched. since [unmap] only has one outlet, you can use it as a replacement for [select] just by connecting [unmap]'s outlet to a [bang]. that way, you don't have to connect each of [select]'s outlets to the same object; you only have to connect it to one! pretty handy in my humble opinion!

anyway i really hope these abstractions do their job and abstract away some common patterns. like i said, i'm most proud of [map] - it's very versatile and i've tried to make it as open-ended as possible so it comes in very much handy!

feel free to share some tips if you discover any clever ideas!