Hi all,

there was a post on PD list that pointed out this link:

http://www.martin-brinkmann.de/pd-patches.html

4 pd patches, Reaktor-style, not exactly "clean" patching in some cases but great
ideas..

Alberto

nice thanks

Finally got around to trying these - great stuff!

I definitely like fmfb!
Pure Reaktorish-patch, great use of fm and tons of feedback delay.
Space sounds, science fiction effects. Nice!!
I definitely have to attach a scope~ to the output to see how it looks like...

Best,

Alberto

Yummy, more synths! all nicely wrapped up and ready to make sounds with. The FM drum box is Inspiratinal to play with. I think we are going to start hearing lots more music made with Pd soon.

Here's my two latest musical offerings (as pd code)
http://www.obiwannabe.co.uk/html/compositions/compositions.html

i know these a quite old,but does anyone else get alot of errors when opening these*?

If you haven't already, do check out the mnb instruments package as well. There are a lot building blocks in there. My favourites are the dualdelay1s, pcf1s, and rockaloops. Grainstates and groovebox are good fun as well.

I've had no trouble opening these using the last two versions of Pd-extended.

they open fine now,but i get no sound at all??

I love grainstates.
Can't stop playng

Thanks

@S-N-S said:

i know these a quite old,but does anyone else get alot of errors when opening these*?

I had few errors in opening some of the patches, in particular
regarding vcf_lp2~ and vcf_hp2~, (in fbfm, for example, in "phaser1" and "rezchord1"
an error related to the iem_cot~, which handles the frequency cutoff of the filters).
Moreover, on some recent extended Pd I know that there where issues
with the zexy objects >~,==~, due to the hexloader that were fixed on the very last versions.
I asked this to Martin which was very kind in answering:

>i know this problem. iem_cot~ is just a symbolic link to iem_cot4~,
>and it is missing in pd extended on windows (and maybe in some linux
>releases too). i do not use extended, but 'pd vanilla' with a few libs
>and externals manually added.

Outstanding music out of these patches!!!

Alberto

beautiful collection...
i don't understand how do brinkmann's patches save values when closing
can anybody explain?
thanks

After taking a quick look at his groovebox1 patch, it looks like he's storing preset values into [graph] objects, which are just arrays with the "graph on parent" option turned off. By clicking "save contents" in the properties dialog, the contents of all the [graph] objects are retained when the patch is closed.

Edit: if you're looking for a state-saving system, you might want to take a look at [sssad]. It's a little weird to wrap your head around at first, but once you get it you realize it's the simplest option, especially for complicated presets. The above method is a bit archaic. It's fine for small patches, but for large ones it gets convoluted and doesn't save symbols.

hi Maelstorm, thank you for the explanation, it's a nice solution indeed and i'll study it.
yes, i'm looking for a state-saving system and i know about sssad but maybe there's something missed in my pd extended because i have this error message:
_sssad/singleton $1.SSAD sssad-persistence $1 $0
... couldn't create
if you know something about this error...
thanks

He is a great patch designer in Reaktor and puredata.