@llorona said:

The new forum doesn't seem to like it when the word "table" is enclosed by square brackets (I.e. the ASCII representation of PD's table object). I guess it thinks it's BBCode? It chops off the rest of the post.

I think it would be a better practice to use code block for [objects]

[table]

[adc~]
|
[dac~]

@emacpher said:

Losing links to the old forum is a disaster ... That was a huge resource. Why not "freeze" it but keep it available for searching and access via whatever URL's folks might have saved for themselves. I know I have a lot.

The old one is still browsable here :
http://puredata_bak.hurleur.com

perfect_house_music.pd

Super great

Well, sorry for the randomness these last days, we made some server change, and had dns issue + forgot to transfert the puredata db, well long story.

Anyway, I think all is in order now.

Interesting project, for embedding audio patch directly in web page.

http://www.iua.upf.edu/~malonso/pdplugin/

A patch just for test the Attachement function

http://www.pdpatchrepo.info/hurleur/bofibof.pd

I did use time by time pdvst within energyXT 1, was pretty nice, but the way pdvst work is not ideal.

It would be as good than max4live if it let user store the patch state,structure,and data right inside your main host project.

What would mimic the max4live way (if i have well understood how it works), would be having only 1 pdvst vst plugin that would be able to store the patch as a preset, instead of creating an instance of pdvst for each patch you make, modify.

Not sure if the specification of vst let you store a big amount of data...

If only i had better coding abilities, i would give it a try, right now the pdvst project looks pretty dead (not new work on it since 2004).

thanks you hardoff
happy it suits some ears