 |
RodsAndConesMain.RodsAndCones HistoryHide minor edits - Show changes to markup April 25, 2012, at 10:46 PM
by -
Changed lines 193-194 from:
to:
This week roughly will cover Jitter tutorials 41,42,43 and Appendix C Additional resources:
April 19, 2012, at 10:28 PM
by -
Changed lines 149-150 from:
<pre><code> to:
[@ Changed lines 182-185 from:
</code></pre> to:
@] April 19, 2012, at 10:27 PM
by -
Changed lines 144-184 from:
to:
Patches from class Here's a patch with the correct way to fade between 2 videoplanes : <pre><code> begin_max5_patcher---------- 1278.3oc4YssbpaCE8Y3qP0SejiGc218I5i8anSmLBr.bJXQrkykdly+d2Rf IPgDrMACSOSx.Xgrzxq8dsuH99vAASLupKCP+F5OQCF78gCF3GxMvfsWOHXk 50oKUk9oEL0rZkN2FLZy2Y0uZ2L9xro+MZgtPirFzLUpFMQaeQqyQqLOmAax 16XYVtdpoJ2eazsCNyjaKy9GsaLBMDuc30J6zEY4yenPO0tAkLIMjvivR9HD S.yDQDb2aL3Uzes25kqV4WufeuHSsrd6yR8iYl732Hw0ClWsJKeo15eDIuOn oxVOJ1M3OFNz8xnKjqrKznrxxJ30bje5nWTkH6BkE49tT8Z6hGz4pIK0Hk0V jMoxp8yoTac7Kwcmto9XlMb9xvmyR0l0KU45xPzeLC8loBo.SwbCvdGYPfab 0H+RMF1g7z5shfFevViOoMKp01LRDIjKYQbwHDkEFySXzHvvIkd6Gl0ZKm7J a4VoKKUy0GY4vg.dCQTLdG27AzvF.XeasdCGDDr6QbcgtDbKT1LS99d1wzP4 VO6HwNVB63H7dLzYDEQxc2pLxyuwsld4mjdomjdIcfdy0u.6yQr6u7MfbaKu NaoQYC9L1gCrIMAywBmOWbXBPTBfdXzPmCItszSxsgcbhPvQn09ciNv26DzC msyuifkgrHIkCel6UmsmdNs1jcR5g9EpMIgNcx0QatOGEwBY3XLMoYZyCt0K WaRuxNeeD6N0rzTf9Uxt+u.N9DjjLILJlwDRPV5zkDQDOZatgtPSrqLMAQcf Eoawp.A4DU97OkPjrjvXLSPiOLlk.2MQIemlXsp.lrUWrMKuOEYyylRuCIq8 CvSSfkjvvRZ2IKVxMjrtMBPIlFFIkXAPajjjPAiAdeWh.TdaxRdTAwPMvyMn w1BUd4LSwpGbQ3sHJZrpxZVAQ5mhvmqPXzXO8ux.UQW81yu0klYNxf.P8AX+ Kxd8r4nEIhcgCnBXMY7DA7YQLoa89vXAWW23epLOTvL3DLTP8vhngwIQTW5q Nadnjai4whlbve5BUotsAZ7wqG0922rYeJOSC4P8TtBUA.TWnJgD0s37TbKX 43ubQPA3RqK1J.7O7OrIHOTE6l+ae2P0bYCoQFTlgHBpXNx0YNsazHII31jR rPqRGgfxDRgrzesoC2q7KHzqjGCryHTrniMTSucICexF5O.Nz3p7rmp7QOUo p0V2GNcXyqQBrX760yBjqiQofCHcCk1AmtaXBrWxxSMurU35HJjjiQLIjGxW zp6L2pyQMoZ1LPj6tzTAIqpu9JKr4TnmANzPEzkJmjzMNN9+c5ZFTla8IQRR jgTLVjbAB6ne100zn2OzR2mcmLB+Rz0hqrOm0Le9xctbG8nmk+4mkHkTqv16 froG2m49sd+E0L4Wn+yS.LJLHZmBB0r.P6cTWh3NFhuihK+t3q8++7Ka4Ara 7CYrRSUwz5Gw55BQQ6.aptDBo6ORv8ljqpGz6OQKxRS046aRSyJcV4zO92fn U3AemgGwYviqCydBOtyZ3r7SOhGB6NCOzl3+v5W+G4cFdXmAOtVx6K+4FXt5 Q3Htufi2ZwOCdD8FbhZ.6zenw8S2dV3H6M3jz.zvw8FbZRdhj6Jzv5wr52Ud N7lTyCqGwSSRg1eYHZhvpGKvnIYH5pLeS47p0qeVWTtcM8HAZ04QSg6R4H+k Y4atzuhAE5mypmOena09wv+EQPoRT end_max5_patcher----------- </code></pre> April 19, 2012, at 12:09 PM
by -
Added lines 136-137:
This week includes items from Jitter tutorials 31, 32, 33, 34, 37, 40. April 19, 2012, at 08:58 AM
by -
Changed lines 7-8 from:
to:
Also by popular demand Wed afternoons from 430-530 April 19, 2012, at 08:56 AM
by -
Changed line 145 from:
to:
Added line 148:
April 19, 2012, at 08:53 AM
by -
Added lines 128-129:
Patches from class Added line 132:
Added lines 135-141:
Supplemental reading
April 12, 2012, at 06:30 PM
by -
Changed lines 119-122 from:
This week includes items from Jitter tutorials 27, 28, 45, 46, 47, 48, 51. There's also the above named objects. Additionally, there's a .pdf that explains (somewhat) what's going on with mxj. to:
This week includes items from Jitter tutorials 27, 28, 45, 46, 47, 48, 51. There's also the above named objects. Changed lines 126-127 from:
to:
April 12, 2012, at 12:36 PM
by - April 12, 2012, at 12:35 PM
by -
Changed lines 126-127 from:
to:
April 12, 2012, at 12:16 AM
by -
Changed lines 115-122 from:
This week includes items from Jitter tutorials 27, 28, 45, 46, 47, 48, 51 to:
This week includes items from Jitter tutorials 27, 28, 45, 46, 47, 48, 51. There's also the above named objects. Additionally, there's a .pdf that explains (somewhat) what's going on with mxj. Supplements
April 11, 2012, at 11:33 PM
by -
Changed lines 112-113 from:
Patches from class to:
Patches from class Added lines 121-122:
This week includes items from Jitter tutorials 27, 28, 45, 46, 47, 48, 51 Changed line 137 from:
to:
April 06, 2012, at 01:23 AM
by -
Added lines 112-113:
Patches from class April 05, 2012, at 03:52 PM
by -
Added lines 44-46:
<<<<<<<
======= Changed lines 48-49 from:
to:
>>>>>>> Changed line 133 from:
to:
April 05, 2012, at 01:24 PM
by -
Changed lines 44-45 from:
to:
April 05, 2012, at 11:45 AM
by -
Changed lines 102-103 from:
to:
April 05, 2012, at 11:29 AM
by -
Changed line 66 from:
Patches from class\\ to:
Patches from class\\ Changed lines 79-80 from:
Patches from class : Patches from class to:
Patches from class Changed lines 123-125 from:
to:
April 05, 2012, at 11:28 AM
by -
Added lines 45-68:
Week 1:
differences between Max6 and PD. If you want to use an alternative (like softVNS for max5 or gridflow in PD or Quartz Composer, knock yourself out, but I will be of significantly less help)
Assignment : create a video player that moves to random points in a timeline. In class, we looked at building a scrubber with a mouse, expand on that idea and combine the player it with different types of input (ideas include Arduino, keypress, audio detection, etc etc etc). Look at the framebyframe.maxpat example for a starter. Patches from class April 05, 2012, at 11:26 AM
by -
Deleted line 44:
http://itp.nyu.edu/~dis244/blog/?cat=21 April 05, 2012, at 11:26 AM
by -
Changed lines 87-89 from:
to:
April 05, 2012, at 11:23 AM
by -
Changed lines 73-74 from:
This week covers the cv.jit help patches, and Jitter tutorial 25. Also the max patcher storage Tutorials. to:
This week covers the cv.jit help patches, and Jitter tutorial 25. Also the max patcher storage Tutorials. Added lines 80-82:
Assignment April 04, 2012, at 10:49 PM
by -
Added line 42:
April 04, 2012, at 02:07 PM
by -
Changed lines 42-43 from:
to:
April 04, 2012, at 02:06 PM
by -
Changed lines 42-72 from:
Some nice pages for insiration and reference Course ScheduleWeek 1:
Assignment : create a video player that moves to random points in a timeline. In class, we looked at building a scrubber with a mouse, expand on that idea and combine the player it with different types of input (ideas include Arduino, keypress, audio detection, etc etc etc). Look at the framebyframe.maxpat example for a starter. Patches from class Jitter Tutorials 1,2,3, 5, 14 & 16 are analogous to what we covered in class to:
http://itp.nyu.edu/~dis244/blog/?cat=21 April 02, 2012, at 01:37 PM
by -
Changed lines 43-45 from:
Some nice pages for insiration and reference Andrew benson's Jitter recipes Book 1, Book 2, Book 3, Book 4. to:
Some nice pages for insiration and reference April 02, 2012, at 01:37 PM
by -
Changed lines 43-45 from:
to:
Some nice pages for insiration and reference Andrew benson's Jitter recipes Book 1, Book 2, Book 3, Book 4. April 02, 2012, at 11:36 AM
by -
Added lines 98-104:
This week covers the cv.jit help patches, and Jitter tutorial 25. Also the max patcher storage Tutorials. Supplemental readings
April 02, 2012, at 11:31 AM
by -
Added line 86:
April 01, 2012, at 10:48 PM
by -
Changed lines 89-90 from:
to:
April 01, 2012, at 10:33 PM
by -
Changed lines 94-95 from:
to:
Changed lines 110-111 from:
to:
April 01, 2012, at 10:29 PM
by -
Changed line 86 from:
to:
April 01, 2012, at 10:29 PM
by -
Added lines 69-70:
Jitter Tutorials 1,2,3, 5, 14 & 16 are analogous to what we covered in class Added lines 83-84:
We covered things that are in Jitter tutorial 8, 10, 11, 15, 16, & 17 March 30, 2012, at 08:53 PM
by -
Changed lines 79-80 from:
Patches from class : Patches from class to:
Patches from class : Patches from class March 30, 2012, at 05:23 PM
by -
Changed lines 79-85 from:
to:
Patches from class : Patches from class Links and things mentioned :
March 29, 2012, at 01:42 PM
by -
Changed lines 41-43 from:
to:
March 29, 2012, at 01:42 PM
by -
Changed lines 41-43 from:
to:
March 29, 2012, at 01:01 PM
by -
Added line 40:
March 29, 2012, at 12:37 PM
by -
Added line 39:
Added line 42:
March 29, 2012, at 12:32 PM
by -
Added line 38:
Changed lines 40-41 from:
to:
March 29, 2012, at 11:32 AM
by -
Added line 37:
March 29, 2012, at 11:13 AM
by -
Added line 36:
March 29, 2012, at 11:02 AM
by -
Changed line 68 from:
to:
Added lines 72-74:
Assignment : Use at least one of the built in effects in Jitter, plus feedback, to make something interesting! If the built in tools aren't your cup of tea, try using a third party library like Auv-i. March 29, 2012, at 10:24 AM
by -
Added line 35:
March 29, 2012, at 08:31 AM
by - March 29, 2012, at 02:43 AM
by -
Added line 34:
Changed lines 37-38 from:
to:
March 29, 2012, at 12:18 AM
by -
Added line 33:
Changed lines 37-38 from:
to:
March 28, 2012, at 09:26 PM
by -
Changed line 31 from:
to:
March 26, 2012, at 08:49 PM
by -
Changed line 32 from:
to:
March 26, 2012, at 08:48 PM
by -
Added line 32:
Changed lines 37-38 from:
to:
March 26, 2012, at 05:47 PM
by -
Added line 31:
Changed lines 37-38 from:
to:
March 23, 2012, at 04:10 PM
by -
Added lines 30-37:
Student pages
March 22, 2012, at 04:55 PM
by -
Changed lines 51-52 from:
Assignment : create a video player that moves to random points in a timeline. In class, we looked at building a scrubber with a mouse, expand on that idea and combine the player it with different types of input (ideas include Arduino, keypress, audio detection, etc etc etc) to:
Assignment : create a video player that moves to random points in a timeline. In class, we looked at building a scrubber with a mouse, expand on that idea and combine the player it with different types of input (ideas include Arduino, keypress, audio detection, etc etc etc). Look at the framebyframe.maxpat example for a starter. Patches from class March 22, 2012, at 10:30 AM
by -
Changed lines 22-23 from:
There is an activity for nearly every class. They are very short, simple activities. These are the basic steps you need to go through to understand the principles discussed in class each week. They're designed to help you not only to understand the technical details, but also to get a feel for what the technology can do, so that you can incorporate it into actual projects. You should at least complete the steps outlined each week, so that you understand practically what it is we're talking about. Document on your blog any discoveries you make, pitfalls you hit, and details not covered in the class that you think will be useful for your fellow students and future students in this class. to:
There is a homework assignment for nearly every class. They are very short, simple activities. These are the basic steps you need to go through to understand the principles discussed in class each week. They're designed to help you not only to understand the technical details, but also to get a feel for what the technology can do, so that you can incorporate it into actual projects. You should at least complete the steps outlined each week, so that you understand practically what it is we're talking about. Document on your blog any discoveries you make, pitfalls you hit, and details not covered in the class that you think will be useful for your fellow students and future students in this class. Added lines 26-29:
Final ProjectAt the end of the semester, you will be expected to present a final project that uses dataflow language for video in some compelling fashion. This can take the form of an installation, performance, software, what have you. You are free to combine this final with that of another class, but make sure you let the other instructor know what you're doing. We will start to discuss these in week 4. March 22, 2012, at 08:50 AM
by -
Changed lines 14-15 from:
It;s probably best to BYO laptop to class. It is very helpful to use while we go over particular topics, and learn by doing in class. However, they can also be a super distraction. Whenever classmates are presenting or we're in the midst of a class discussion, however, please keep your laptop closed. The quality of the class depends in large part on the quality of your attention and active participation, so please respect that and close your lid. to:
It's probably best to BYO laptop to class. It is very helpful to use while we go over particular topics, and learn by doing in class. However, they can also be a super distraction. Whenever classmates are presenting or we're in the midst of a class discussion, however, please keep your laptop closed. The quality of the class depends in large part on the quality of your attention and active participation, so please respect that and close your lid. Changed line 33 from:
to:
Changed lines 38-39 from:
to:
Changed lines 45-46 from:
to:
March 21, 2012, at 04:20 PM
by -
Deleted lines 7-12:
GradingParticipation & Attendance: 40% Changed lines 14-15 from:
Laptop use is fine if you are using your laptop to present in class, or if we're in the middle of an exercise that makes use of it. Whenever classmates are presenting or we're in the midst of a class discussion, however, please keep your laptop closed. The quality of the class depends in large part on the quality of your attention and active participation, so please respect that and close your lid. to:
It;s probably best to BYO laptop to class. It is very helpful to use while we go over particular topics, and learn by doing in class. However, they can also be a super distraction. Whenever classmates are presenting or we're in the midst of a class discussion, however, please keep your laptop closed. The quality of the class depends in large part on the quality of your attention and active participation, so please respect that and close your lid. Changed lines 22-29 from:
There is an activity for nearly every class. They are very short, simple activities. These are the basic steps you need to go through to understand the principle discussed in class each week. They're designed to help you not only to understand the technical details, but also to get a feel for what the technologies we're discussing can do, so that you can incorporate them into actual applications. You should at least complete the steps outlined each week, so that you understand practically what it is we're talking about. Document on your blog any discoveries you make, pitfalls you hit, and details not covered in the class or the lab that you think will be useful for your fellow students and future students in this class. Production AssignmentsFor production assignments, you'll be expected to present your project in class on the day that it's due. If you're working in a group, all group members should be present, and should participate equally in the presentation. Journal & DocumentationYou are expected to keep an online journal of your progress. The purpose of the journal is twofold. First, it is a valuable way for you to communicate to your instructor that you are keeping up with the work in the class. We read the journals to see how students are doing, so you should update your journal regularly throughout the semester. At a minimum, reference to each week's work is expected, and thorough documentation of the production projects and technical research. Second, the journal is a way to document your work for your own use and that of others. Many ITP students have found themselves using their journals as a place to store notes, code samples, and more. to:
There is an activity for nearly every class. They are very short, simple activities. These are the basic steps you need to go through to understand the principles discussed in class each week. They're designed to help you not only to understand the technical details, but also to get a feel for what the technology can do, so that you can incorporate it into actual projects. You should at least complete the steps outlined each week, so that you understand practically what it is we're talking about. Document on your blog any discoveries you make, pitfalls you hit, and details not covered in the class that you think will be useful for your fellow students and future students in this class. I expect you to have a blog/journal/publicly available website where you will be posting the weekly work. Changed lines 28-32 from:
Week 1:
to:
Week 1:
Added line 36:
Changed lines 45-57 from:
Week 2: using the video grabber, some built in effects, automating things. jit.rota 3 computer vision, jit.gen 4 LFOs, audio to video, video to audio 5 openGL for optimization. drawing with jit.gl.sketch 6 More GL, slabs, it.gl.gridshapes Using with other applications : syphon. 7 show your work, final questions to:
Assignment : create a video player that moves to random points in a timeline. In class, we looked at building a scrubber with a mouse, expand on that idea and combine the player it with different types of input (ideas include Arduino, keypress, audio detection, etc etc etc) Week 2:
Week 3
Week 4
Week 5
Week 6
Week 7
March 20, 2012, at 03:31 PM
by -
Changed lines 39-64 from:
1)basics : you already know how to patch things together (thanks Hans!). Now we’re going to apply that knowledge to the world of video and matricies. differences between max6 and PD. Will be teaching n Max, if you want to use an alternative (like softVNS for max5 or gridflow in PD, knock yourself out) Quick tour of the interface : browser, sidebar, attributes window. help patches and reference. keyboard shortcuts for object creation. Play a movie! bang makes us do it jit.qt.movie (file types, codecs read, autostart, loop, unique, gettime, frame, randomly jump around in timeline. adapt, dim) show how movie continues to play even when metro is off. looppoints. qmetro vs metro. @colormode uyvy use mouse to control playback, scrubbing. Use keyboard to ump to different points in a film jit.pwindow vs jit.window jit.fpsgui : matrix name The jitter matrix! Screen coordinates planes, dims, types, named matricies, setcell, getcell (pack vs pak) sends and receives in matricies. 2 using the video grabber, some built in effects, automating things. jit.rota to:
Week 1:
Week 2: using the video grabber, some built in effects, automating things. jit.rota March 20, 2012, at 03:28 PM
by -
Changed lines 2-25 from:
to:
Boxes and Lines for Rods and ConesSpring 2012
GradingParticipation & Attendance: 40% Participation & AttendanceShowing up on time, engaging in the class discussion, and offering advice and critique on other projects in the class is a major part of your grade. Please be present and prompt. Lateness will hurt your grade. If you're going to be late or absent, please email me in advance. If you have an emergency, please let me know as soon as you can. Please turn in assignments on time as well. LaptopsLaptop use is fine if you are using your laptop to present in class, or if we're in the middle of an exercise that makes use of it. Whenever classmates are presenting or we're in the midst of a class discussion, however, please keep your laptop closed. The quality of the class depends in large part on the quality of your attention and active participation, so please respect that and close your lid. Mobile PhonesPlease put them on vibrate or turn them off before you come to class unless they are part of your project. Changed lines 28-44 from:
Final ProjectThe central goal of this class is to start developing fluency in the Pd programming language so that you are able to express ideas in the form of functioning projects. The class focuses on the programming language itself, and works best when you bring in project ideas to work on. Then you can focus on building real projects while developing fluency in Pd. Therefore, this class ends with a final project. It should be a substantial chunk of work, but it need not be something entirely new. Working on a project for a good chunk of the class is the best for learning, but it is also acceptable to present some smaller chunks as long as you can demonstrate basic understanding of what it takes to complete a larger project. Breakdown of Example ProjectsOne approach to becoming good at a programming language is to learn a set of building blocks very well, then think in terms of those building blocks. This is the approach that this class aims to teach. To that goal, we will see a demo of a related project every week, talk about how it was done, and break it down. The central idea is to focus on what is happening rather than whether we liked it or not. The discussion can cover any topic, the only thing that is not allowed are judgments, like "I liked it", or "that sucked", or "that's a nice guitar sound". Instead we should talk about how to implement it using the tools we know, whether the idea was well implemented, whether a different approach would have been more effective, etc. LaptopsDuring much of the classtime, you will be following along and programming on your own laptop. Therefore it is essential that you bring your laptop to every class. That said, laptops are also very effective instruments of distraction. Everyone benefits if we all pay attention. I'll do my best to keep the class interesting, I hope you'll join me in this pursuit. You are welcome to use your laptop in class when I am speaking, or when it is relevant to the classwork being presented. However, during discussions and when your fellow students are talking, please be respectful of everyone's time and close the lid. If necessary, I'll remind you of this, but even better would be if everyone does so on their own. to:
There is an activity for nearly every class. They are very short, simple activities. These are the basic steps you need to go through to understand the principle discussed in class each week. They're designed to help you not only to understand the technical details, but also to get a feel for what the technologies we're discussing can do, so that you can incorporate them into actual applications. You should at least complete the steps outlined each week, so that you understand practically what it is we're talking about. Document on your blog any discoveries you make, pitfalls you hit, and details not covered in the class or the lab that you think will be useful for your fellow students and future students in this class. Production AssignmentsFor production assignments, you'll be expected to present your project in class on the day that it's due. If you're working in a group, all group members should be present, and should participate equally in the presentation. Journal & DocumentationYou are expected to keep an online journal of your progress. The purpose of the journal is twofold. First, it is a valuable way for you to communicate to your instructor that you are keeping up with the work in the class. We read the journals to see how students are doing, so you should update your journal regularly throughout the semester. At a minimum, reference to each week's work is expected, and thorough documentation of the production projects and technical research. Second, the journal is a way to document your work for your own use and that of others. Many ITP students have found themselves using their journals as a place to store notes, code samples, and more. March 20, 2012, at 03:23 PM
by -
Changed lines 24-128 from:
(1/28) Week 1: Pd Overview
(2/4) Week 2: What is Dataflow?
(2/11) Week 3: processing generic messages
(2/18) Week 4: lines and signals
(2/25) Week 5: storing data
(3/4) Week 6: encapsulationThe key to building large projects is encapsulating ideas into reusable chunks. The difference between a code block and a function: subpatches are code blocks and abstractions are functions, kind of. The real power of abstractions is not, that they are in their own files so they can be used for code reuse. The real power is, that they can accept arguments.
(3/11) Week 7: Final Project Presentations
to:
1)basics : you already know how to patch things together (thanks Hans!). Now we’re going to apply that knowledge to the world of video and matricies. differences between max6 and PD. Will be teaching n Max, if you want to use an alternative (like softVNS for max5 or gridflow in PD, knock yourself out) Quick tour of the interface : browser, sidebar, attributes window. help patches and reference. keyboard shortcuts for object creation. Play a movie! bang makes us do it jit.qt.movie (file types, codecs read, autostart, loop, unique, gettime, frame, randomly jump around in timeline. adapt, dim) show how movie continues to play even when metro is off. looppoints. qmetro vs metro. @colormode uyvy use mouse to control playback, scrubbing. Use keyboard to ump to different points in a film jit.pwindow vs jit.window jit.fpsgui : matrix name The jitter matrix! Screen coordinates planes, dims, types, named matricies, setcell, getcell (pack vs pak) sends and receives in matricies. 2 using the video grabber, some built in effects, automating things. jit.rota 3 computer vision, jit.gen 4 LFOs, audio to video, video to audio 5 openGL for optimization. drawing with jit.gl.sketch 6 More GL, slabs, it.gl.gridshapes Using with other applications : syphon. 7 show your work, final questions March 20, 2012, at 11:40 AM
by -
Added lines 1-128:
This syllabus is liable to change Assignments
Final ProjectThe central goal of this class is to start developing fluency in the Pd programming language so that you are able to express ideas in the form of functioning projects. The class focuses on the programming language itself, and works best when you bring in project ideas to work on. Then you can focus on building real projects while developing fluency in Pd. Therefore, this class ends with a final project. It should be a substantial chunk of work, but it need not be something entirely new. Working on a project for a good chunk of the class is the best for learning, but it is also acceptable to present some smaller chunks as long as you can demonstrate basic understanding of what it takes to complete a larger project. Breakdown of Example ProjectsOne approach to becoming good at a programming language is to learn a set of building blocks very well, then think in terms of those building blocks. This is the approach that this class aims to teach. To that goal, we will see a demo of a related project every week, talk about how it was done, and break it down. The central idea is to focus on what is happening rather than whether we liked it or not. The discussion can cover any topic, the only thing that is not allowed are judgments, like "I liked it", or "that sucked", or "that's a nice guitar sound". Instead we should talk about how to implement it using the tools we know, whether the idea was well implemented, whether a different approach would have been more effective, etc. LaptopsDuring much of the classtime, you will be following along and programming on your own laptop. Therefore it is essential that you bring your laptop to every class. That said, laptops are also very effective instruments of distraction. Everyone benefits if we all pay attention. I'll do my best to keep the class interesting, I hope you'll join me in this pursuit. You are welcome to use your laptop in class when I am speaking, or when it is relevant to the classwork being presented. However, during discussions and when your fellow students are talking, please be respectful of everyone's time and close the lid. If necessary, I'll remind you of this, but even better would be if everyone does so on their own. Course Schedule(1/28) Week 1: Pd Overview
(2/4) Week 2: What is Dataflow?
(2/11) Week 3: processing generic messages
(2/18) Week 4: lines and signals
(2/25) Week 5: storing data
(3/4) Week 6: encapsulationThe key to building large projects is encapsulating ideas into reusable chunks. The difference between a code block and a function: subpatches are code blocks and abstractions are functions, kind of. The real power of abstractions is not, that they are in their own files so they can be used for code reuse. The real power is, that they can accept arguments.
(3/11) Week 7: Final Project Presentations
|