Hey fellas!
Presenting my first complete patch, but a pretty useful one (at least for me!).

Quark is an aleatoric midi sequencer which at a given tempo plays notes, randomly taken from a selected musical scale. Additional randomization options are available, such as volume, note duration and even dynamic scale changes. All open instances of the sequencer can be synced to each other and can additionally trigger Hydrogen to play in sync.

Quark was created to be used in a modular audio environment of a GNU/Linux system. On other systems sync between sequencer instances and Hydrogen might have little meaning. Quark was tested on GNU/Linux only.
From Pd perspective, the patch uses basic objects, but visually is a little messy. It is one of my first patches and by the time I found out about subpatches and abstractions, it was easier to leave it as it is. At the same time it is not a big patch at all, fitting on a laptop screen, and important sections are commented.

For full description of how it works, venture here:
http://www.louigiverona.ru/?page=projects&s=software&t=puredata&a=puredata_quark

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

http://crca.ucsd.edu/~msp/techniques/latest/book-html/node111.html

cha-ching! i'm just saying spend a minute or two with puckette's book, it's some good shit

http://crca.ucsd.edu/~msp/techniques/latest/book-html/node124.html

Here's where to get The Puckette's Book Pineapple.

~:o)

http://crca.ucsd.edu/~msp/techniques.htm
http://crca.ucsd.edu/~msp/techniques/latest/book-html/

Keep well all ~ SSSSSSSSSSSS

Artificial Reverberation
http://crca.ucsd.edu/~msp/techniques/latest/book-html/node111.html

All-pass Filters
http://crca.ucsd.edu/~msp/techniques/latest/book-html/node150.html

i think one thing you should take into account when designing a GUI is something that will fit well ontop of the work you've already done. if your patch has a message handling structure already embedded in it (one that is sufficient to control all parameters of your patch), it would be very easy to employ either of the trends mentioned above.

if your patch has a set up where many sub-patches on a main canvas, perhaps the graph-on-parent method would work well.

another consideration is displaying information from your patch (not just controlling or changing it).

though i guess the main thing is usability. certain components and controls are going to fit your patch better than others. if your patch needs to be used in some type of performance, what features will make the patch easiest to use for the performer.

i do not know much about it other than it exists, but joseph sarlo at UCSD is working on GrlPd...sometype of layer for making GUI's for your patches. the link is [url=http://crca.ucsd.edu/~jsarlo/gripd/ ]http://crca.ucsd.edu/~jsarlo/gripd/

i hope this helped some and perhaps it will stimulate some forum discussion.

i haven't done very much in the area of adc~ analysis myself, but i have heard that miller puckette's fiddle~ and bonk~ externs seem to be fairly popular for this task. i guess fiddle detects pitch and bonk detects rhythms (more or less). here is paper on fiddle and bonk:
[url=http://www-crca.ucsd.edu/%7Etapel/icmc98.pdf ]http://www-crca.ucsd.edu/%7Etapel/icmc98.pdf

(the paper is pretty technical, you might find more practical information elsewhere).

another note--if you have the resources available, you'll probably find the best results if can use two computers, one for audio and one video, and send the information with netsend/netreceive (or better yet OSC, i find it much easier to use).

good luck.

--zac

. for the startup, the preferences is called "flags", you can specify audioi, midi, font , path for your abstractions etc ....
In OsX, I don't know where is the startup files. I remember edit a file pd.command somehwere
for an help with flags see: [url=http://crca.ucsd.edu/~msp/Pd_documentation/x3.htm#s4 ]http://crca.ucsd.edu/~msp/Pd_documentation/x3.htm#s4

. for preset , it's a real question. the object qlist, textfile would interest you. You can also use just array to store values. save it and open it like this :
[url=http://giair.music.free.fr/patchs/partage/array/enregistrer_array.gif ]http://giair.music.free.fr/patchs/partage/array/enregistrer_array.gif

there is another object in other libraries : pbank from pdjimmies, xeq from ?, and matrix.

Another way is built with the Rradical solution : [url=http://puredata.info/community/projects/convention04/lectures/tk-barknecht/ ]http://puredata.info/community/projects/convention04/lectures/tk-barkn echt/
It seems to be powerful.

. hide cables is impossible but a right click on a subpatch and select graph on parent works well. or use canvas.

. the best way to talk is here in anglish or in idecibel.com in french. the mailing list is very a specialist discussion, not focus on newbie.

. inlets and outlets of an object is showed with a right click on the object and selecting help. for better comprehension you can add a comments near your inlets or outlets to be more clear.