On Jun 24, 2005, at 3:25 AM, Anton Woldhek wrote:
Its a good start, but much needs to be done. I like the format, a question and a set of objects. For beginning exercises, all of the necessary objects should be there. As the exercises get more advanced, then the objects can just be suggestions. While I think that using the PDDP templates is a good idea, I don't think we should use the exact templates, rather make workshop/exercise templates. Ben Bogart has a good start in that regard.
I cant seem to locate Ben's files at the moment
I just whipped out some sketches of some patches for the very first intro workshop for Pd. I attached them.
Ok this is a more documentation then exercise kind of patch. Seems
good to start at this level. (In regards to what I was on about with the max tutorial pdf).Btw: execution order isnt undefined (as I have no doubt you are well
aware of) but is depend on creation order. I think this is an important
aspect of pd coders to realize well though. It should be brought back in an
practical exercise where the student is given a problematic patch to debug.
Its officially "undefined", but currently, its based on the order that
things were connected. But its very bad to rely on that, so its much
better to teach people to use a [trigger] if they need a defined
execution order.
Also, I remember some talk in the past about making all the connections
to an inlet execute at the same logical time. That change would break
patches that rely on the connection order, but patches build around the
idea of "undefined" execution order would be fine.
Btw2: im not sure if putting a [o] on a [*~] connect to a [osc~ 500]
is a good idea for n00bs. They might ruine their speakers!
These are not finished patches, just the ideas. The finished patches
will use standard PDDP GUI elements for such things.
.hc
Cheers Anton
If you are not part of the solution, you are part of the problem.
- Eldridge Cleaver