[PD] PDDP Homework & Meeting Notes Dec 19th 2005
Hans-Christoph Steiner
hans at eds.org
Tue Dec 20 23:59:42 CET 2005
I totally agree that teaching is the best way to really learn a topic.
Please contribute anything that you might come p with whille you are
learning Pd. I wrote a lot of help patches while trying to figure out a
given object, for example.
Also, I find that after I teach a workshop, I always make a few new
tutorial patches for questions that were asked during the workshop.
.hc
On Mon, 19 Dec 2005, Kyle Klipowicz wrote:
> This is really awesome Ben! I have been reading along with the web
> posts, and unfortunately have missed the meetings so far, but I think
> that this is a very important initiative with Pd. I have just started
> to try and explain Pd to some friends, and realize that it is somewhat
> of a miracle to have gotten as far as I have on the scattered
> (although inspiring) documentation that exists.
>
> Especially brilliant is your implication that _EVERY_ Pd
> user/developer is a student, with more and more difficult
> tasks/assignments. I think that by teaching Pd to people, and sharing
> my patches/abstractions with them, it will serve only to increase and
> refine my own personal Pd knowledge. But that can be applied to
> anything ;-)
>
> Kudos!
>
> ~Kyle
>
> On 12/19/05, B. Bogart <ben at ekran.org> wrote:
>> PDDP Meeting Dec 19th 2005
>>
>> _Issues:_
>>
>> * Encourage code sharing
>> * patching style
>> * implimentation vs creation (abstraction design)
>>
>> _Content Ideas:_
>>
>> An assignment for students in the higher levels is to create a
>> high-level abstraction. This abstraction is means to solve the problem
>> of either A: A fellow students creative problem or B: provide more
>> high-level abstractions for lower-level students. This would benifit the
>> students by:
>>
>> * Students learn to describe the problem they are solving.
>> * Students learn to communicate that problem to one and other.
>> * Students are encouraged to make use of the efforts of others.
>> * Enourages students to look at problems from other points of view.
>>
>> _What is the Purpose of these workshops?_
>>
>> * Learn Pure-Data?
>> * Create media outside the context of commercial markets?
>> * To get back some freedom and genuine experience?
>> * Is the purpose of the workshops not the same as the purpose of PD
>> itself?
>>
>> Workshop Draft (partical)
>>
>> _Level 1 (Intro)_
>> * Image
>> * Loading a still image (high-level, window&file hidden)
>> * Using a numberbox to control the size of the image
>> * Loading a video clip (same abstraction as above)
>> * Using number box to scrub video frames
>> * Using metro to control clip playback
>> * Sound
>> * Load a sound file (high-level, table&soundfiler hidden)
>> * Play sound file back with phasor~
>> * Srub sound file with numberbox
>> * Create sound (high-level FM abstraction?)
>> * Change sound quality with numberbox
>> * Network
>> * Read MIDI values (simple MIDI abstraction)
>> * Add midi control to control frame of video & tone of FM synth
>> * Physical Media
>> * HW interface (serial&processing hidden)
>> * push-button advances frame and triggers sound-file.
>>
>> _Level 2 (less Intro)_
>> * Image
>> * High level PDP patch that has three abstractions:
>> * load an image file
>> * blur effect
>> * output to window
>>
>> *HOMEWORK Assignment For Developers*
>>
>> Today we talked about extending the concept of the project based
>> workshop into the workshop materials themselves. That is each level of a
>> workshop (above we have level 1 layed out and level 2 is particially
>> done) is brought home by using a different project example. That is each
>> level would have a creative project already developed that would serve
>> to inspire the students individual projects, as well as give meaning and
>> context to the technical details (implimentation)
>>
>> So for your assignment you need to create a project idea that:
>>
>> * Fits in with a particular level of the workshop (level 1 is
>> introduction and
>> level n is advanced. Just choose a number from 1-10 to describe the
>> level of
>> the project.
>>
>> * The project should be pretty simple in terms of concept and as
>> technical as
>> your chosen level allows.
>>
>> * Require as few externals as possible
>>
>> * The project has to be feasible
>>
>> * The project has to be inspiring!
>>
>> * Ideally it will encompass all four threads, image/sound/network/physical
>>
>> For the next meeting on January 9th 2006 all PDDP contributers should
>> have developed a project concept and implimentation that could work as
>> teaching material.
>>
>> An example project from my Metaphorical Networks lecture is:
>>
>> Concept:
>>
>> * As the sun rises an eye opens
>>
>> Implimentation:
>>
>> * An LDR connects to a multiIO which reads the voltage
>> * We read this value and scale it to 0-100
>> * The 0-100 value controls which frame a video of an eye opening is
>> playing.
>>
>> Yes this example only has visual and physical media.
>>
>> This page is available on the PDDP wiki @:
>>
>> https://www.puredata.info/dev/pddp/BBogartsMeetingNotes20051219
>>
>>
>> _______________________________________________
>> PD-list at iem.at mailing list
>> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
>>
>>
>>
>>
>
>
> --
> http://perhapsidid.blogspot.com
> (((())))(()()((((((((()())))()(((((((())()()())())))
> (())))))(()))))))))))))(((((((((((()()))))))))((())))
> ))(((((((((((())))())))))))))))))))__________
> _____())))))(((((((((((((()))))))))))_______
> ((((((())))))))))))((((((((000)))oOOOOOO
>
> _______________________________________________
> PD-list at iem.at mailing list
> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
>
zen
\
\
\[D[D[D[D
More information about the Pd-list
mailing list