i am working on a new set on pd, but there are a few buds and problems which are driving me crazy.... here are a few:

• a graph with "graph on parent" enabled put in a subpatch will also show on the parent and the main patch, creating terrible overlaps. solutions i've tried include puting the arrays in subpatches (but then i loose visual relation to the rest of the patch. in my example numberboxes linked to faders and graphs), and using one display unit to replace the data with coords messages (but then i loose general view of various units, which is very usefull especially with automations and remote controls).

• the "hide name and argument" option does not seem to work with arrays. they will always display their names when GOP is on...

• initialising. when the mainpatch is opened, a preset is loaded in every unit of "mud", but a few steps have to be done before any audio gets computed, and the patch starts to work normally. what i usually do is: load a sound, move the display slider (over where it says parameters), toggle to FUNC, click the display slider, move the view slider (over where it says playback) until it says "min". then the audio begins..... well is there a simple way to initiate? unpon opening a preset is loaded into each unit, so i'm basically looking for a way to run through all the hiden arrays so they send their data...

well that's it for now. as you can see my knowledge in pd is quite basic and i use only simple objects. so with this post i am looking for:

• answers to the above questions
• other problems and bugs i haven't noticed yet
• advice on how to make it better
• advice on great areas of pd i do not use (state saving systems, datastructures, creating guis) and would really make the job easier....

i really hope some of you will take the time, i learned all i know from this forum. i'm quite proud of that patch, and will happily post it and a tutorial upon completion.
thanks guys,

gab

http://www.pdpatchrepo.info/hurleur/newmud10.zip

• a graph with "graph on parent" enabled put in a subpatch will also show on the parent and the main patch, creating terrible overlaps. ...

I posted a possible solution for this to you on another thread just now.

• the "hide name and argument" option does not seem to work with arrays. they will always display their names when GOP is on...

This irritates me a bit, too. If you're willing to dig into data structures, you can make graphical arrays with them that are not only nicer looking (colors! shapes!) but are easy to manipulate with the mouse. You don't actually need to learn a whole lot, either. They're just a little more awkward to use at first.

• initialising. when the mainpatch is opened, a preset is loaded in every unit of "mud", but a few steps have to be done before any audio gets computed, and the patch starts to work normally. what i usually do is: load a sound, move the display slider (over where it says parameters), toggle to FUNC, click the display slider, move the view slider (over where it says playback) until it says "min". then the audio begins..... well is there a simple way to initiate? unpon opening a preset is loaded into each unit, so i'm basically looking for a way to run through all the hiden arrays so they send their data...

I'd have to dig into the patch a little more to see why you have to do this, but wouldn't the simple workaround be to load the preset, then [trigger] those steps afterwards?

I have to ask, though, do you really need all those hidden gui elements? Pd is notoriously inefficient when it comes to its gui, and those eat up a lot of cpu, even when they are hidden away in a subpatch. Arrays are the worst. Don't get me wrong, I'm all for nice guis and do plenty of "hacks" to make them cooler, but I've found it best to limit them to what I need. I mean, your patch freaks my laptop the fuck out without it even running.

if i remember well, you already saved me once a year ago with an earlier version of the same . thanks man .

about the gop leaking i'll check your other post right now.

about hiding the names of arrays, ok so the only solution would be datastructures .... i'll get to that soon then.

about all this gui, i guess you are right. i thought of using loads of arrays to store values, and one other to display them, because:
-it's easy to save as presets (just stick the arrays in a main one) and to modify later (it's one same system for all comunications and interface etc)
-it gives access to lots of parameters in little space
-i can't think of anything else (how else can i get to set individual parameters for master controls?)

i know the patch is not operational. the problem comes from the mud abstraction, i haven't finished it yet. maybe the solution is to just forget about displaying so much. i thought the gui only used up cpu if it showed, but i guess graphs are not the solution ...
there might also be trouble with having so many fiddle~ objects working together ...

the trouble is when i get stuck it's usually because of a detail i hadn't thought about, and having to re-invent everything gets me down. this patch is exactly what i want.

thanks alot, i'll go see if i find solutions in datastructures .
i'll think about all this.

gab

haven't been able to work for a while, but i'm back to that same patch ...
i've used all your tips with donecanvasdialog and a switch on the main patch, and it all seems to work fine (until now) . i just have a little problem with it: every time i close the master patch pd asks me if i want to save each unit of that "mud" patch where i use donecanvasdialog. i guess it's understandable as this is a building function, but is there any way around this? it's a hastle having to save every time ...

[donecanvasdialog <arguments>, dirty 0(
|

thank you so much, i finally got a first rough version of a complete production patch working. i have to update the envelope generators ("toing") and the sequencer, but it all seems to work ...
i had trouble using the ldirty 0( message, so i installed version 0.42.5-extended and now it works .
still have to find a way to initialise each unit of the "mud" patch properly (for now the master patch is slow until you move the "select" slider (where it says parameters) across for each unit of "mud"), and as i said update and review the envelopes and sequencer, but everything works fine, even controled by my BCF2000 .

so thanks, as you got me through all those problems. here is the temporary version of the patch. i'll make sure i post it with a tutorial ounce it's clean, and i'll let you know ... just out of curiousity: what do you use pd for? are you a musician? i mean if you know so much about pd you must be making great patches ...

cheers

gab

http://www.pdpatchrepo.info/hurleur/newmud11.zip

what do you use pd for? are you a musician? i mean if you know so much about pd you must be making great patches ...

I spend most of my time not finishing patches.

Okay, well, really I've just been in college (or university, depending on where you're from apparently) for the past four years and am just now in a program where I can use Pd for the majority of my projects. Before it was all on the side. I've mostly used it for synthesis and a little composition (which is why I got into it in the first place). Lately I've been using it mostly for dsp and audio analysis.

I almost finished something last year. Was really close.

if you do have a working patch somewhere as example i'd love it ....

my next chalenge (a few hours away, i'll go buy the beast today) is to use the kinect for xbox with pd for contemporary dance projects .... if it's too big for me alone i might have to find asociates ...
well thanks for all the help and the tips,
you can check some sounds of mine, entirely made with an earlier version of my patch, here : www.myspace.com/gabriellecup

cheers