Happily, I'm a *voluntary* affliction (for c74 listeners,
anyway). Everyone whines about how mellow I am
now and occasionally berates me for forcing *them*
to tell people to STFW/RTFM, etc. So far, no satisfactory
Jitter patches to accompany the RTQE webcast that
don't look suspiciously like kin to the tiresome throbbing
technotorus that follows you around the room, or I'd
probably be more visible. :-)
Besides occasionally going outside and performing with some of my
openGL patches I've used some jitter in video post production to do
effect work that would otherwise be very tiresome with after effects,
etc, mostly music videos - Hip Hop ( for The Roots).
1. Nearly any problem in Max/MSP/Jitter benefits
from being understood in terms of seeing it as
data being output from something that needs to
be transformed before being sent as data to
something else [where it works as input]. NOT
understanding that is a big reason why some
new users don't bother to learn anything about
messages and data formats, and also why those
same people spend so much of their lives doing
"cargo cult patching" [i.e. randomly connecting
things together with no particular understanding
of the data moving down the wires/pipes].
2. Don't assume that there is either a single external
object that performs any given function you may
want or require, or that there is a single solution or
"proper" solution to something you want to do. The
search for idiosyncratic solutions is a habit that
will serve your art well in general - and, once
you have your own solutions, the process of working
to optimize things is the second great school of
3. In the long run, the perceived efficiency of the patch
grovel is illusory with respect to the insight gained
from an attempt to solve the problem that confronts you.
Once found, shared solutions can be a formidable
source of insight - having mastered the habits of
thought the solution requires, the work of others
can be appreciated as embodying the results of a
similar search by others in a way that may generate
other insights for you.
I'm going though the Andrew GL tutorials and they are amazing.
They are really helping me to understand what is going on. I don't quite understand trigger yet but I'm sure I will get there.
I think you guys are forgetting about the creative part of max. Sometimes the ideas are more important the fancy coding.
A couple of things I've learned:
Break everything down into small pieces. If you try to skip steps then you will never get to the end. If you first have an idea so you think. Ok, this is what I want to do. How do I get there? This is the object I think will do it. How does it work? Print it up and see how the data is moving.
One of the most complicated things to do is move a lot of data. Lists are very hard to deal with. I recently discovered the spray object. Cool stuff, I used it to trigger a bunch of line objects, and then send them out a random outlet. It was very difficult to deal with that much data. It was worth it though. I based it off of Andrew’s animation tutorial and really made that thing dance. Any ideas on how I might edit that tutorial more to make it really cool? I've got it set up so that my drum machine is making the animation dance. You know, #31 animator.
Also is there anyway to edit the backdrop of GL stuff without adding more GL objects. I know I can do colors but that seems kind of dull.
Actually, Andrew's recipes are about as good an example
of a "programming style" in Max as I can readily summon,
unless you want to look at Tim Place's alpha version of
the Tap.Tools [which are abstractions rather than externals].
Joshua's right, and I wouln't sweat it. I should program as
well as he does.
On May 9, 2006, at 5:12 PM, jonathan marcus wrote:
> On May 9, 2006, at 3:41 PM, Tristan Hansen wrote:
>> Break everything down into small pieces. If you try to skip steps
>> then you will never get to the end.
> the oblique strategies needs some new cards for coders.
ah, maybe it's time to put another page next to the FAQ - the FGA
(frequently given answers) ;-)
in that case, my personal favourites shouldn't be forgotten:
'please post an example patch'
'I am away from the office for two weeks and will respond to your
I apoligise for any inconvience this may cause. '
by putting all these together & stirring really well, it might be
possible to find THE UNIVERSAL ANSWER TO MAX QUESTIONS, which could
be given to any question appearing on the forum, which probably could
be automated, and everybody had more time to do fun things with max/
Are you proposing to write the patch that does this? I think this
could best be done by creating an abstraction that interprets the
keypresses from someone smashing their forehead against their keyboard
and passing the output to an mxj that posts to a PHP script via ssh
key authentication. I searched the manual, but I'm not sure if it'll
Although I might quibble with the tone somewhat, quite a
few of us play round-robin when it comes to posting this
helpful guide to asking questions in a way that will almost
surely guarantee a focused and helpful answer.